Bugzilla – Full Text Bug Listing
| Summary: | CNFE: org.xml.sax.SAXException on org.eclipse.jetty.osgi.boot start with jsp fragment | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] Jetty | Reporter: | Dmytro Pishchukhin <dmytro.pishchukhin> | ||||
| Component: | osgi | Assignee: | Hugues Malphettes <hmalphettes> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | gregw, hmalphettes, jetty-inbox, mgorovoy | ||||
| Version: | 7.1.4 | ||||||
| Target Milestone: | 7.1.x | ||||||
| Hardware: | PC | ||||||
| OS: | Windows Vista | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Dmytro Pishchukhin
Created attachment 171934 [details]
Issue details
Hi Dmytro, Thanks for filing the bug. This sounds exactly like bug 315004 However it should be fixed :/ I just verified that the manifest of the osgi.boot bundle does import org.xml.sax Could you let me know how you start the application and which jdk you are using? Thanks! (In reply to comment #2) Hi Hugues, 1. I use JDK 1.6.x 2. To reproduce it you can use the list of bundles from the attachment. I use bundles from JettySDK4EclipseRT-7.1.4.v20100610-win32.win32.x86.zip. Regards. > Hi Dmytro, > Thanks for filing the bug. > This sounds exactly like bug 315004 > > However it should be fixed :/ > I just verified that the manifest of the osgi.boot bundle does import > org.xml.sax > > Could you let me know how you start the application and which jdk you are > using? > > Thanks! (In reply to comment #3) > (In reply to comment #2) > > Hi Hugues, > > 1. I use JDK 1.6.x > 2. To reproduce it you can use the list of bundles from the attachment. I use > bundles from JettySDK4EclipseRT-7.1.4.v20100610-win32.win32.x86.zip. > Ok. I just double-checked that I can download and start the app on windows 32. I started it on the command line through start.bat. How do you start it? I you use a launch configuration, could you attach it to this bug please? Could you type in the OSGi console >osgi packages.org.xml.sax I am struggling to reproduce this issue. Hugues, FYI: I've made some tests with similar host-fragment bundles configuration. It does not work even with import-package org.xml.sax in fragment bundle :( (tested on 3.5.2 and 3.6.R4). I'm just trying to find any workaround for this issues. Regards (In reply to comment #5) > Hugues, > > FYI: I've made some tests with similar host-fragment bundles configuration. It > does not work even with import-package org.xml.sax in fragment bundle :( > (tested on 3.5.2 and 3.6.R4). > > I'm just trying to find any workaround for this issues. > > Regards OK so if we add to the jsp fragment "org.xml.sax" to the imported packages then we are fine? I'll do that and send you a new experimental distrib to verify if that is ok with you. (In reply to comment #6) > (In reply to comment #5) > > Hugues, > > > > FYI: I've made some tests with similar host-fragment bundles configuration. It > > does not work even with import-package org.xml.sax in fragment bundle :( > > (tested on 3.5.2 and 3.6.R4). > > > > I'm just trying to find any workaround for this issues. > > > > Regards > > OK so if we add to the jsp fragment "org.xml.sax" to the imported packages then > we are fine? > I'll do that and send you a new experimental distrib to verify if that is ok > with you. No, it won't help me. I've already tried. :( I have not any idea why it works fine in SDK and does not work in my configuration. Maybe some system properties are missed in my configuration. I have to check. It takes some time.... Thank you for support. (In reply to comment #7) > > No, it won't help me. I've already tried. :( > > I have not any idea why it works fine in SDK and does not work in my > configuration. Maybe some system properties are missed in my configuration. I > have to check. It takes some time.... > > Thank you for support. Oh Dymtro: I had not realized you were the reporter of bug 315004 Ok, well there is something different in the way OSGi is setup there. I asked around my co-workers if they knew more about execution profiles and why org.xml.sax is not available. If you can share a testcase to reproduce this I can try some more. (In reply to comment #8) > (In reply to comment #7) > > > > No, it won't help me. I've already tried. :( > > > > I have not any idea why it works fine in SDK and does not work in my > > configuration. Maybe some system properties are missed in my configuration. I > > have to check. It takes some time.... > > > > Thank you for support. > Oh Dymtro: I had not realized you were the reporter of bug 315004 > Ok, well there is something different in the way OSGi is setup there. I asked > around my co-workers if they knew more about execution profiles and why > org.xml.sax is not available. > > If you can share a testcase to reproduce this I can try some more. I'll ask also in Equinox tree Dymtro identified the core issue and filed a bug about it: bug 317007 This specific issue is fixed. It will require org.apache.jasper.glassfish v201006231034 or later from eclipse orbit. I'll add a second packaging to the jetty-test-webapp to also make it a web-bundle: currently the project jetty-test-webapp produces a war and a sources.jar. I'll add another artifact that will be the same web-app as a web-bundle. It will be attached to the same maven project as the artifact jetty-test-webapp-webbundle.jar I'll mark this bug fixed once I can run this test webapp with felix via pax-exam. I'll need to add the unzipping of the web-bundles to support the jsp pages inside the web-bundle. Fixed for 7.1.5.v20100705 I was able to run the jetty-test webapp packaged as a webbundle and automated the testing of a simple jsp page. |