Re: deserialization error: no deserializer is registered

2004-01-16 Thread Jim Stafford
thanks, jim FONTDEVILA Diego wrote: RE: deserialization error: no deserializer is registered You probably have not registered correctly the bean serialization classes to handle your bean (the SOAP serialization issue is independent from the information you give the JVM when you say

Re: deserialization error: no deserializer is registered

2004-01-15 Thread Jim Stafford
similar to the wsdd files for deployment. I am still stuck at java2wsdl. thanks, jim FONTDEVILA Diego wrote: RE: deserialization error: no deserializer is registered You probably have not registered correctly the bean serialization classes to handle your bean (the SOAP serializatio

Re: deserialization error: no deserializer is registered

2004-01-15 Thread Sesha Nandyal
Thank you for the response. I will try the solution you have suggested. Sorry all - for posting this question that uses JWSDP. Sesha FONTDEVILA Diego wrote: You probably have not registered correctly the bean serialization classes to handle your bean (the SOAP serialization issue is independe

Re: deserialization error: no deserializer is registered

2004-01-15 Thread Anne Thomas Manes
You should send this question to Sun's JAX-RPC discussion list. At 11:14 AM 1/15/2004, you wrote: Hello All, I am getting the following error : deserialization error: no deserializer is registered for (null, {http://com.test/types/HelloWebservice}HelloBean

RE: deserialization error: no deserializer is registered

2004-01-15 Thread FONTDEVILA Diego
Title: RE: deserialization error: no deserializer is registered You probably have not registered correctly the bean serialization classes to handle your bean (the SOAP serialization issue is independent from the information you give the JVM when you say Serializable). Here is a code example

Re: Deserialization error: org.xml.sax.SAXException: Invalidelement in...

2003-06-26 Thread Steve Weiss
I think I fixed my problem. Apparently I needed to create a separate QName object for each of my bean classes in the client, and use it for the type mapping. -Steve

re: deserialization error

2002-06-18 Thread James Black
Hello, I used a nightly build from 11 June, and have a - Mapping Exception to Axis Fault message. I get a java.lang.reflect.InvocationTargetException error at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:135) at org.apache.axis.encoding.DeserializationContextImp

RE: Deserialization error upgrading from Beta 1 => Beta 2

2002-05-01 Thread Blumenkrantz, Jason
Upon looking into it further, it looks like Axis Beta 2 is unable to handle HREFs where SOAP-ENC:root is not supplied. From the Axis client, SOAP-ENC:root is set to "0" on the attached bean. However, .NET is not including SOAP-ENC:root attributes. So the method call in the first body element is su