You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by mike jones <mi...@gmail.com> on 2005/06/11 13:46:39 UTC

Using non generated classes in soap call

All,
I a situation where I am passing an object (a simple bean) from axis over a 
soap call to a .net app and back. This object is defined in java and the 
.net end auto generates the class.
However at some point I want pass my object into a .net service, so the .net 
end has written a service using the generated object as a parameter.
I ran the wsdl to java and refactored the created services classes to use my 
class and threw away the auto generated ones.
This all works find I call the service with the object and the object is 
serialized. But at the .net end it cannot convert the soap message back into 
its object. However if I use the generated classes it works.
The only difference in the messages in the namespace in the parameters.. 

generated

<schemeDTO xmlns="http://impl.service.webservice.borris.anite.com"
<http://impl.service.webservice.borris.anite.com/>>
  <ns1:regulatoryReference
xmlns:ns1="http://schemereturn.thepensionregulator.com/xsd"
<http://schemereturn.thepensionregulator.com/xsd>>
    test
  </ns1:regulatoryReference> 
</schemeDTO>

My class
<schemeDTO xmlns="http://impl.service.webservice.borris.anite.com"
<http://impl.service.webservice.borris.anite.com/>>
  <regulatoryReference>
    a test
  </regulatoryReference> 
</schemeDTO>


I would like to know is I am trying the impossible ( but I had this
workig a week ago until a few tweaks) and if so am I missing
something? Are the typeDesc in the generated classes essential?

Thanks any help
Mike :)


-- 
"If we can hit that bull's-eye, the rest of the dominos will fall like a 
house of cards - Checkmate."