In Sun's Java 5 JDK, they learned from bundling Xalan-J in 1.4 as part
of rt.jar, and put the bundled version of Xerces into a different
namespace. I think you still have a dependency on Xerces when using Java
5 since Castor directly tries to create an instance of
org.apache.xml.serialize.XMLSerializer, rather than the Sun Java 5 class
com.sun.org.apache.xml.serialize.XMLSerializer.
Cheers,
James
Werner Guttmann wrote:
Yes and no. In other words, it depends.
If you want to use 'pretty printing', there's currently a dependency on
Xerces as Castor internally uses Xerces to achieve e.g. indentation. But
good news is that there's an interface involved which you can provide a
custom serializer for.
What surprises me, though, is that you are facing problems with JDK 5.0,
as I am sure this has been tested before. What's the problem you are
facing ?
Werner
stoil valchkov wrote:
Hi,
I have a problem to detach from xerces 1.4 jar. class
org.exolab.castor.xml.XercesSerializer has in its constructor
Class.forName("org.apache.xml.serialize.XMLSerializer").newInstance();
This results in class not found if I try using xerces comming with JDK
1.5. Is it possible to remove this dependency?
Best regards,
Stoil
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
