Bugzilla – Full Text Bug Listing
| Summary: | Deployed applications don't work starting from the shell | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] Virgo | Reporter: | Carlos Salinas <devel> | ||||
| Component: | jetty | Assignee: | Project Inbox <virgo-inbox> | ||||
| Status: | CLOSED INVALID | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | eclipse, glyn.normington | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | Macintosh | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Carlos Salinas
Please could you provide a small example application that exhibits the problem? Created attachment 191396 [details]
An app example that shows the error descripbed in the bug item
U should enable an httpservice in the OSGi framework, because the app only consume the service to register a servlet with the web-contextpath '/test' and shows a message ' Hello, world!'.
So that we can reproduce your exact environment, please could you detail how you set up a HTTP Service? Sorry for being picky, but we want to reproduce the bug you are seeing. I describe how i configured the httpservice in the following forum thread: http://www.eclipse.org/forums/index.php?t=msg&th=206189&start=0&S=8120c905b0992dbc1ed0b8cd8eb9e278 (In reply to comment #3) > So that we can reproduce your exact environment, please could you detail how > you set up a HTTP Service? Sorry for being picky, but we want to reproduce the > bug you are seeing. Perfect. Thanks! There is a known issue with the version of Pax-Web you are using, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=331370 As such could you re-test with Pax-Web 1.0.0 where this issue has been fixed. (In reply to comment #6) > There is a known issue with the version of Pax-Web you are using, see > https://bugs.eclipse.org/bugs/show_bug.cgi?id=331370 > > As such could you re-test with Pax-Web 1.0.0 where this issue has been fixed. I have just tested, replacing the Pax-Web bundles version 0.8.0 for ones in the version 1.0.1, and the bug doesnt be fixed. By the i also try using the equinox httpService implemented for jetty 7, as you told in the forum thread http://www.eclipse.org/forums/index.php?t=rview&goto=660064#msg_660064 Bu i couldnt retrieve the httpservice using the same test bundle i attached. Can you point the exact list of bundles i have to deploy besides the org.eclipse.equinox.http.jetty? Hi, Apologies for the slow reply, I've been away on vacation. I can't advise on the Jetty 7 HttpService as I've never had it running myself but I do know it requires most of the Jetty bundles to be present as it's built on top on the WAB support. This is quite different from the way the Jetty 6 HttpService worked. I've only used the Equinox implementation. What extra features do you require from the HttpService as the Equinox one may well meet them. For example there is a Jasper bundle that can provide JSP support for the Equinox HttpService. I think it's worth taking a step back to look at your requirements as you are tying out some quite untested code/combinations and there may well be something much more stable and proven that provides what your after. Thanks, Chris. Dear Raiser Please can you say where you are at with this bug? The Jetty guys are not shipping the Http Service in Jetty 7 as part of Indigo and the use of Pax Web further complicates diagnosis due to some complex repackaging of multiple bundles into a single bundle. Unless we can get to a specific stable configuration, we are not going to be able to diagnose this bug, Regards, Glyn Since we have nothing specific to go on, closing. |