adding an element (a field in a bean) in a webservice without changing the stubs

Hello, I have a webservices in a version. In the next version, I want to add a field in bean which add an element in the soap. If I don't generate again the stubs with the ant task, i get an exception : [junit] org.xml.sax.SAXException: Invalid element in com.accor.services.ws.cli

Re: adding an element (a field in a bean) in a webservice without changing the stubs

Is it possible to pass javabeans as arguments from soap client to the soap service without having to code for custom serializers and de-serializers? Thanks, Olivier Lamy [EMAIL PROTECTED] on 28 Oct 2003 12:14 Please respond to [EMAIL PROTECTED] To:Axis-User [EMAIL PROTECTED] Subject:

RE: adding an element (a field in a bean) in a webservice without changing the stubs

Title: Message Yes you dont have to write any code in order for Axis to pass objects conforming to the Java beans convention. You do have to provide the serialization framework configuration information; Specifically, the Java class, corresponding XML QName, and appropriate

Re: adding an element (a field in a bean) in a webservice without changing the stubs

This is done for you when you use java2wsdl...notice the typeMapping entry (really an exploded beanMapping). chris wrote: Yes you dont have to write any code in order for Axis to pass objects conforming to the Java beans convention. You do have to provide the serialization framework

Re: adding an element (a field in a bean) in a webservice without changing the stubs

Actually it's wsdl2java that generates the correct wsdd files (with mappings), etc. The only code you should have to handroll in web services deployment (at least for me so far...) is the underlying intf/impl that my soap service is calling. You shouldn't need to handcode wsdl, wsdd, xsd, or