Problems with JBoss client accessing a .NET Web Service
Tony Cruickshank
Greenhorn
Joined: Jun 14, 2004
Posts: 3
posted
0
Hi all,
I hope someone here help me with a problem I have accessing a .NET web service from a JBossJ2EE application. Everything seems to be okay up to the point where I try to access the first method when I get the following exception...
java.rmi.RemoteExce�ption: Call invocation failed: Target endpoint address not set; nested exception is: org.jboss.ws.WSExce�ption: Target endpoint address not set at org.jboss.ws.jaxrpc�.CallImpl.invokeInte�rnal(CallImpl.java:7�19) at org.jboss.ws.jaxrpc�.CallImpl.invoke(Cal�lImpl.java:398) at org.jboss.ws.jaxrpc�.CallProxy.invoke(Ca�llProxy.java:164)
Any advice on where I need to look to correct this problem gratefully received.
Thanks,
TonyC
Tony Cruickshank
Greenhorn
Joined: Jun 14, 2004
Posts: 3
posted
0
Hi All,
Resolved. The WSDL file I was generating from contained soap12 artefacts. Though the JBoss wstools generated the mapping and java successfully, at run time the server log contained the warning
WARN [org.jboss.ws.metadata.wsdl.WSDLDefinitions] Multiple WSDL bindings referrence the same interface:
Removing all the soap12 information from the WSDL and starting again with wstools fixed the problem.
TonyC
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.
subject: Problems with JBoss client accessing a .NET Web Service
0
