Right now I'd say if it's working we maybe just raise a low priority
JIRA issue with specifics in it. From past experience, adding more
JARs/options into the bundle could well mask something we should
actually look at in more detail. Also, I'm hoping to look at Jetty 5 or
6 soon and we may well either not get these errors or get a whole
different set.
So feel free to raise a JIRA issue - and feel free to delve further if
you have time - but be aware we may try and move Http onto a more recent
Jetty quite soon
Regards
-- Rob
Thor Heinrichs-Wolpert wrote:
Sorry, I'm on this list at home and working on felix at the office,
but those are the errors I saw, even though I could connect to the
servlet port.
I just didn't want to start trying to resolve something that was a
starting work in progress if someone else was already on it.
Do you want these package dependencies to be worked out? Possibly by
adding in a jetty options bundle?
Cheers,
Thor HW
On 3-May-06, at 1:40 AM, Rob Walker wrote:
As Richard points out, the Http bundle can be quite noisy at present
when it starts up. Key thing is does it actually work - there's Http
test or admin bundles in OBR you could try to see if it's working
(don't forget default port may be 8080 depending on your properties).
I'll probably be taking a look at a couple of JIRA issues on the
Http bundle in the next week or so - so if it is a bug, gather some
analysis/info so we can file a report and I'll try and look into it.
Regards
-- Rob
Richard S. Hall wrote:
Thor,
It might make it easier to diagnose if you could include some of
the errors in your email message. :-)
Are you sure you are seeing missing packages? When you start the
HTTP bundle it does print out some errors trying to load
localization classes, however those are normal. There is some
probing going on for localization classes which cannot be found and
these result in class loading diagnostic errors, but that is normal
since they really are not found.
The resulting message is to help the developer if they need to
debug it, but in this case the error is expected, so no debugging
is necessary. In the future, these messages will be directed to the
logger.
Is that what you are seeing, stuff like this:
ERROR: ****
****
Class 'org.mortbay.http.mime_en' was not found. Bundle 4 does not
import package 'org.mortbay.http', nor is the package exported by
any other bundle or available from the system class loader.
****
****
If so, then everything is fine.
-> richard
Thor Heinrichs-Wolpert wrote:
Is the Jetty bundle working? When I load it I get errors listing
some missing packages.
If it's broken I'll look at it more, if it's working then it's
either my local config or I'm missing some dependencies.
Thanks,
Thor HW
--
Ascert - Taking systems to the Edge
[EMAIL PROTECTED]
+44 (0)20 7488 3470
www.ascert.com
--
Ascert - Taking systems to the Edge
[EMAIL PROTECTED]
+44 (0)20 7488 3470
www.ascert.com
