| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Implementing JAX-WS gateway with JMS support for WAS |
« View previous topic :: View next topic » |
| Author |
Message
|
| billybong |
 Posted: Tue Sep 28, 2010 4:55 am Post subject: Implementing JAX-WS gateway with JMS support for WAS |
 |
|
Disciple
Joined: 22 Jul 2005
Posts: 150
Location: Stockholm, Sweden
|
Hi guys,
My question is more on the WAS/JMS/JAX-WS side, but since I know a lot of you have extensive experience with those setups I'll post it here as well.
I have a requirement to enable JMS support for an existing Webservice that acts as a gateway for backend "non-webservified" apps. The existing service is implemented as a javax.xml.ws.WebServiceProvider (@WebServiceProvider) ejb session bean, meaning that it is not tied to a specific wsdl and leaves the xml-binding/parsing up to the developer(me:-)
This works for the http scenarios, but I want to extend this WAS service to be able to consume JMS requests as well. Having a session bean annotated as webservice requires routing through the usage of generic IBM-supported routing projects. Http-router (basically a servlet) and JMS-router (MDB).
Now, the JMS-router is created automatically and is an MDB of the type "com.ibm.ws.webservices.engine.transport.jms.JMSListenerMDB" with the responsibility to route requests based on the jms property targetService.
I have got this routing to work based on a top-down developed service with a dedicated wsdl, but for all my experiments I simply cannot route messages to a @WebServiceProvider based service. The exceptions I receive says:
| Quote: |
| faultString: WSWS3163E: Error: The Web services engine could not find a target service to invoke! targetService is DUMMY2 |
AFAIK my understanding is that the serviceName is not routable if I choose to implement a JAX-WS service as a @WebServiceProvider
Has anyone else succeeded where I've failed?
The reason why I want to build this mediation as a jax-ws service is to reuse policys, handlers etc that are standardized at my client.
_________________
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Integration Developer V6.0
IBM Certified System Administrator - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere DataPower |
|
| Back to top |
|
 |
| billybong |
| Posted: Tue Sep 28, 2010 6:02 am Post subject: |
|
|
Disciple
Joined: 22 Jul 2005
Posts: 150
Location: Stockholm, Sweden
|
I actually managed to find the solution myself (as often when you take the time to ask a question 
Just fyi the targetService should include the targetNamespace for the service. I.e.
com.mycorp.services.DummyService2
_________________
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Integration Developer V6.0
IBM Certified System Administrator - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere DataPower |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 28, 2010 6:06 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| billybong wrote: |
| I actually managed to find the solution myself (as often when you take the time to ask a question |
| billybong wrote: |
Just fyi the targetService should include the targetNamespace for the service. I.e.
com.mycorp.services.DummyService2 |
That does seem fairly obvious. And thanks for posting it. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
