Scott M Stark wrote:
>This hell is due to the packaging of the xml components by
>the various parsers, and xml based derivatives. Everyone tends
>to bundle the core xml classes in one jar and incompatabilities
>arise. No one bundles the core java.* packages in their code.
>The fact that the xml based products bundle the core xml classes
>is due to a lack of a standard api for obtaining parsers and transformers.
>Now that JAXP 1.1 is out there is no reason for this. Start complaining
>to the product bundlers about this.
>
I was under the impression that, Xalan and Xerces acted as plugins to
the JAXP API
provided you set the following properitis correctly either on the
commandline or in a
jre/lib/jaxp.properties file.
javax.xml.transform.TransformerFactory
javax.xml.parsers.SAXParserFactory
javax.xml.parsers.DocumentBuilderFactory
Even if you do you get problems with jboss 2.2.2 as you will get
complaints about a Cp1252
encoding that is not supported by Xercses.
Other xml applications works fine with theese settings.
Regards
Uno Engborg
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user