Hi
Thanks for your quick answer. Now I've got the missing pieces - deploying a
J2EE client to JBoss for getting the client configuration - and I will try it
again.
Regards,
Walter
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884081#3884081
Reply to the
Hi Thomas
For me the part of setting up a J2EE client for calling a web service is not
clear.
When I want to call a .NET web service from a JBoss web service client, I do
not have anything deployed in a JBoss instance. But in order to use the
service-ref tag, I have to do a lookup on JNDI for
Sorry, but I still can't figure out how a java client which uses the JBossWS
runtime libs and a service-ref tag specifing a handler can call a web service
not deployed on JBoss (e.g. a .NET web service).
Are there any example around of a JBossWS client which calls a non-JBoss web
service?
Tha
Thanks for your quick answer.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883405#3883405
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883405
---
SF.Net email is
Thanks for your hint. It works now.
Just another question regarding client side handlers: If I want to install a
client side handler programmaticly with service.getHandlerRegistry() I get an
java.lang.UnsupportedOperationException exception.
How can I install a handler in a JBoss web service cl