META-INF/services/javax.xml.parsers.SAXParserFactory not routed correctly




14 years ago
13 years ago


(Reporter: Kaj Kandler, Assigned: Blake Ross)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/0.10.1 StumbleUpon/1.998
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/0.10.1 StumbleUpon/1.998

This bug does require the Java 1.4.0 or greater plug-in to be installed and an
applet that uses the JAXP lib to parse an xml file.

The JAXP classes request META-INF/services/javax.xml.parsers.SAXParserFactory as
one possible way to determine the appropriate parser factory. This request woudl
be be satisfied within the classpath of the Applet. On of the jars does contain
the services description.

However, in my application it is routed to the server as
/plan-b/META-INF/services/javax.xml.parsers.SAXParserFactory (it is treated as a
URL realtive to the codebase), where it does not exist.

This behavior is not the same with the same JDK and Internet Explorer.

for the JAXP behavior and configuration.

Reproducible: Always
Steps to Reproduce:
1. Install a proxy server, so you can log the requests to the server
2. Call
a page with the appropriate applet. Download plan-b/bin/player22.jar containing
the META-INF/services/... file
3. See your proxy logs for all requests

Actual Results:  
a request to plan-b/META-INF/services/javax.xml.parsers.SAXParserFactory to the

Expected Results:  
A request to META-INF/services/javax.xml.parsers.SAXParserFactory that is
satisfied from the code jar, that contains the service definition. 

I assume this has somethign to do with the integration of the Java Plug-In.
However, I could only classify it as a general bug. Please recategorieze at will.

This bug indicates to me a breach of the classpath for java applications, which
could be a security risk.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.