• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Devaka Cooray
  • Ron McLeod
  • Jeanne Boyarsky
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
  • Tim Holloway
Bartenders:
  • Martijn Verburg
  • Frits Walraven
  • Himai Minh

Problems with JBoss client accessing a .NET Web Service

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,

I hope someone here help me with a problem I have accessing a
.NET web service from a JBoss J2EE 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
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
Don't count your weasels before they've popped. And now for a mulberry bush related tiny ad:
the value of filler advertising in 2021
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic