简体   繁体   中英

Alternatives to generate the java code from the WSDL and xsd from the local files

We have a SOAP axis2 server that we cannot control that exposes some webservices. We created a webservice client using the wsdl from that webservice. It generated the java code from the wsdl using Eclipse

This will be deployed in production but if the server adds a outputfield for example, our code will break and we will need to generate the java code again, make a jar and deploy on the server.

This does not make any sense. It should be 100% or extremely close of update. Does it make sense to generate the java code from the WSDL and xsd from the local files?

All the examples I saw were like this

you can configure your JAXB2-Deserializer to ignore unkown (optional) elements, that preserves a bit of compatibility. Or modify the generated xsd to allow additional elements (xs:any) on the desired level.

But yes, that's a problem mostly solved by management

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM