thanks for the prompt reply .. i did go through the other thread which talked about websphere 7 but for them the change in castor property worked , but it does not seem to help me
i am running the app from RAD 7 . and not on a standalone websphere , so its all running in a default mode .. i even tried to add castor to class path , it did not work then added Xerses that did not work either altho i read in the forum and castor docs for jdk 5 we dont need xerses , but since nothing was working i was trying options Note : when i started this project i did this entire implementation on tomcat 6 as i knew websphere will make me feel its presence. and it worked perfect there when i started on websephere(from scratch) i just got struck with this issue. Werner Guttmann wrote: > > Not 100% sure, but Websphere's classloader does behave a bit in a non > standard way sometimes. Can you please investigate whether there's any > JARs on the classpath that might interfer ? > > Werner > > aminjava wrote: >> I am using castor 1.3 and websphere 6.1 >> >> i am on jdk 1.5.0.16 and have my castor.properties >> set to >> >> org.exolab.castor.xml.serializer.factory=org.exolab.castor.xml.XercesJDK5XMLSerializerFactory >> >> >> the code seems to fail and raise the exception as mentioned in subject >> here >> ... >> >> StringWriter writer = new StringWriter(); >> marshaller.setWriter(writer); >> >> i am writing obj to xml string >> >> ANY ideas what is wrong .. >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > -- View this message in context: http://www.nabble.com/Could-not-instantiate-serializer-com.sun.org.apache.xml.internal.serialize.XMLSerializer-tp25402979p25432897.html Sent from the Castor - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
