Hi Max,
After reading your article I made sure that the message parts had different
names in their definitions and used them for overloading the same WSDL method:
getModel(). The WSDL bindings for the method uses the different message parts
as appropriate.
Here is the binding generated by
J2EE webservices must adhere to WS-I Basic Profile 1.0, which JBossWS does.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3882865#3882865
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3882865
We all want to do advanced stuff in wsdl files, based on our business
requirements. But the eventual goal should be to make your webservices
portable(across containers) and interoperable(with .Net).
J2EE 1.4 web services (which JBossWS supports) has support for WSDL 1.1 (which
allows method
Thanks for the feedback. I shall simply rename WS operations (for use within
the same portType at least).
Claire.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3882873#3882873
Reply to the post :
Have a look at my article over here:
http://www.devsource.com/article2/0,1759,1828651,00.asp It is mostly related to
.NET, but everything about WSDL, messages, and methods would still apply to
Axis / JBoss.
Hope this helps
[EMAIL PROTECTED]
http://www.jbossfaq.com
is
Thanks Max. I'll take a look at the article and see how it works out.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3882620#3882620
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3882620
