The problem appears to be due to the fact
that no OSGi HTTP service is being registered. I
changed the config.ini to start up a telnet console (added osgi.console=1025
to the existing BIRT config.ini) and then checked to see if an HTTP service was
registered. No joy – and without HTTP Muse won’t start. And without Muse, no COSMOS.
I’ll poke around and try to figure
out why Jetty’s unhappy. More later…
Joel
-----Original Message-----
From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Hawkins, Joel
Sent: Tuesday, November 13, 2007
1:01 PM
To: Cosmos Dev
Subject: RE: [cosmos-dev] COSMOS
i7 DC Blocking Bug 209548.
Hmmmm. I’m assuming
this is something that used to work and now doesn’t? So what’s
changed? I know that I haven’t checked in anything since the last
iteration, so I’m pretty sure I didn’t break anything!
I’ll download it
and try to reproduce the issue. I’d invite Hubert to look into it as well.
Cheers,
Joel
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose it
to anyone else. If you received it in error please notify us immediately and
then destroy it.
From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Sheldon Lee-Loy
Sent: Tuesday, November 13, 2007
12:41 PM
To: cosmos-dev@xxxxxxxxxxx
Subject: [cosmos-dev] COSMOS i7 DC
Blocking Bug 209548.
I opened a blocking bug 209548 on the DC component. This is a
blocking bug because the reports can not be generated with the latest driver.
The bug report contains the steps to reproduce the problem:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=209548
Joel,
I assigned this bug to you since the reports work off the old DC runtime code
base and not Hubert's code changes.
Thanks,
Sheldon
______________________________________
Sheldon Lee-Loy
Tivoli Autonomic Computing, IBM Toronto Lab