Hello!
Sorry to say, but this may be a hard working lesson to never go for the "code first" approach when creating web services which contracts shall be persistent over time and over different application servers. So a tip for future development, write your wsdl and included schemas by hand and then generate code from that (that's what we call "contract first").
Ok, now the good thing. You can always save your old published wsdl file and generate code from that. It will work for you.
Kind regards
/Oskar
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144123#4144123
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144123
We are using the default jbossws version that comes with AS 4.2.2. The exceptions differ depending on the client consuming the services and the method being called. Most of the exceptions are related to NullPointerExceptions due to the differences in the published WSDLs. Some Web methods may not produce errors, but don't produce results due to the schema changes as well.
Most of the WSDL changes have to do with differences in Namespaces produced by JBOSS. I've tried included package-info that explicitly defines the XmlSchema to closely match the published WSDL, but so far it seems that the only thing I can do for the client apps that consume the services is to re-create the proxies so they have the new definitions.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143902#4143902
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4143902
