Great to see you got things working. As I have already said a few time over the last 2 years or so, with products like Websphere it turns out to be an environmental problem most of the times.
Cheers Werner aminjava wrote: > Worked now ... > let me explain what fixed it ... > > As i mentioned i am using jdk 1.5.0.16 , what i did was on my RAD workspace > i changed the jre to this 1.5.0.16 and not of webspehere 6.1 > > i now changed the jre to websphere 6.1 and then this in castor.properties > org.exolab.castor.xml.serializer.factory=org.exolab.castor.xml.XercesXMLSerializerFactory > it worked ... > > -Amin > > > > > 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 >> >> >> >> > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
