Could not instantiate serializer com.sun.org.apache.xml.internal.serialize.XMLSerializer

[aminjava]

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 ..

[Werner Guttmann]

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

[Werner Guttmann-6]

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

[Werner Guttmann]

Btw, if you had a look in the archives of the user mailing list, you
could have found the answer to your problem yourself.

Have a look at

http://www.junlu.com/list/70/377066.html

and I am sure you will find a similar solution, as both WebLogic as well
as WebShere tend to misbehave now and then .... ;-).

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

[aminjava]

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

[try zigc]

Werner,

I think this is related to this. Recently I used castor 1.3 in a NetBeans module. I try to marshal an object to a StringWriter. No error and no exception but it simply does not work. The StringWriter is empty. If I run the unit test outside the NetBeans platform runtime, everything works. I had to revert back to castor 1.0 which I have been using for some time.

thanks

Bill

On Mon, Sep 14, 2009 at 2:36 AM, aminjava <amin.mohammed@...> wrote:

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

[aminjava]

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

[Werner Guttmann-6]

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

[Werner Guttmann-6]

Sorry, Bill, bt I don't see how this could be to the problem at hand. If
you have issues with Castor 1.3, please let us know through a separate
thread.

Regards
Werner

try zigc wrote:

> Werner,
>
> I think this is related to this. Recently I used castor 1.3 in a NetBeans
> module. I try to marshal an object to a StringWriter. No error and no
> exception but it simply does not work. The StringWriter is empty. If I run
> the unit test outside the NetBeans platform runtime, everything works. I had
> to revert back to castor 1.0 which I have been using for some time.
>
> thanks
>
> Bill
>
>
> On Mon, Sep 14, 2009 at 2:36 AM, aminjava <amin.mohammed@...> wrote:
>
>> 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
>>
>>
>>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email