Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347704 - org.apache.taglibs.standard.glassfish is missing package imports for XML parser
Summary: org.apache.taglibs.standard.glassfish is missing package imports for XML parser
Status: RESOLVED FIXED
Alias: None
Product: Orbit
Classification: Tools
Component: bundles (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Hugues Malphettes CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-30 17:30 EDT by Jochen Hiller CLA
Modified: 2011-07-14 04:15 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jochen Hiller CLA 2011-05-30 17:30:08 EDT 
I've used the bundle org.apache.taglibs.standard.glassfish from Orbit as part of the javax.servlet.jsp.glassfish feature (2.1.0.201105282013).

Using this feature will raise a

    java.lang.NoClassDefFoundError: javax/xml/parsers/ParserConfigurationException

error. We've included the bundles javax.xml, javax.xml.stream as part of our target platform.
See also http://dev.eclipse.org/mhonarc/lists/skalli-dev/msg00068.html. 

The apache tagibs implementation has references to XML parser classes, e.g. org.xml.sax and others, but are not added in MANIFEST.MF to import packages.


I've added the package imports for

 javax.xml.parsers;version="1.3.0",
 org.xml.sax;version="2.0.2",
 org.xml.sax.helpers;version="2.0.2"

and jsp and taglib compilation did work then. I am not sure which version (min, max) has to be defined, the versions above worked well for me.
Comment 1 Hugues Malphettes CLA 2011-05-31 03:53:13 EDT 
Thanks for filing the issue.
I would like to be able to use the packages provided by the JDK eventually.
Jetty uses the version "0" for those 3 packages and it has been working fine.

Do you think:
 javax.xml.parsers,
 org.xml.sax;version,
 org.xml.sax.helpers
would also work for you?

Cheers.
Timewise we will have to wait for Indigo to be released before we can have a new build at orbit.
Comment 2 Jochen Hiller CLA 2011-05-31 04:45:08 EDT 
I've tested it in my environment with imports without versions, did work well.

A build after Indigo is fine for me: I have a workaround to get my product built for the moment.

It would probably more relevant for Skalli CI build, but we are yet lacking other 3rdParty bundles.

Cheers, Jochen
Comment 3 Hugues Malphettes CLA 2011-05-31 06:05:07 EDT 
Thanks for testing it. I'll commit and make a new build after Indigo.
Ping us for volunteers at Orbit and we will find people to help package the dependencies you guys need.
Comment 4 Hugues Malphettes CLA 2011-07-14 04:15:29 EDT 
Fixed with tag v201107141553