I thought I'd post my solution to this here as I've spent a day looking for a solution to the same problem, and only finding posts such as this without answers.
I have a JBossWS service that I am connecting a legacy Borland C++ app to, and ran into this same problem: the missing namespace.
In the WSDL Importer generated code, change the line with RegisterInvokeOptions to:
InvRegistry()->RegisterInvokeOptions(__interfaceTypeinfo(MyWebService), (ioDocument, ioLiteral, ioHasNamespace));
|
I can't see how to get WSDL Importer to generate this though.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195997#4195997
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4195997
Hi,
We would like to implements several webservices, but each ( for description simplicity) of them is deployed in separate EAR files.
Furthermore we want to have them all under the same context, lets call it OurContext.
So to achieve that functionality to our WS we have added :
@WebContext(contextRoot = "OurContext")
All applications deploy without any problem BUT only one (from recently deployed ear) WSDL is accessible!
it looks like only one ear can store WSDLs to specific contextRoot. Is it right? or maybe we are doing something wrong?
I would appreciate any help!
Michal Margiel
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195940#4195940
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4195940
