Client side JAX-RPC handler

[anil.saldhana]

Show us your <service-ref> element in your web.xml

Are there any errors in the server log when you start JBoss?

[walter.eich]

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 client without specifing a service-ref, e.g. calling a .NET web service?

Thanks for any help.

we

[jason.greene]

J2EE Webserivces explictly forbids modifying the handler chain programatically (you have to do it in the service-ref tag), we have a feature request to add a jboss propreitary method to programmatically modify the handler chain here:

http://jira.jboss.org/jira/browse/JBWS-142

-Jason

[walter.eich]

Thanks for your quick answer.

[walter.eich]

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?

Thanks for any help.

Kind regards,
Walter

[thomas.diesler]

What part of the step by step wiki is unclear?

http://wiki.jboss.org/wiki/Wiki.jsp?page=WSRPCClientStepByStep

[walter.eich]

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 getting the client configuration. It causes a naming exception if I do it as described in the step by step example. So my question is: How can I install a client side handler in a JBoss web service client which calls a .NET service?

Thanks for any help.

Regards,
Walter

[jason.greene]

Using a J2EE webservices client to talk to .NET would work like this:

1. You create a J2EE application client deployment ( this is deployed on the server).

2. You create a standalone client. This is a normal java program which is the true client.

3. On startup, the standalon client app then does a jndi lookup to retreive the meta information from the jboss instance. (This meta information is contained in the J2EE application client deployment)

4. The standalone client will then install handlers that are specified in the meta information.

5. The standalone client issues a webservice request to the .NET service.

Currently the standalone client and the jboss instance containing the J2EE application client must be on the same system, but we are planning on removing this restriction.

-Jason

[walter.eich]

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