| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMQI (2.1.6) EJB Client |
« View previous topic :: View next topic » |
| Author |
Message
|
| james_render |
 Posted: Mon Feb 21, 2005 7:00 am Post subject: WMQI (2.1.6) EJB Client |
 |
|
Newbie
Joined: 21 Feb 2005
Posts: 6
|
Has anyone managed to successfully enable WMQI to use a third party's
EJB service?
I'm particularly interested in any solutions that don't require the
installation of WAS or use of its jar files..
I guess that the only way to do this is to use a proxy that can access
the JNDI facilities itself, e.g. use MQ to talk to a WAS box that in
turn undertakes the necessary ejb call?
Should it be possible to use an alternative JNDI naming service on the
WMQI box and still access the third party EJB?
Thanks
James |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Feb 21, 2005 7:03 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You should be able to write a Java plug-in that will call the EJB.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| james_render |
| Posted: Mon Feb 21, 2005 7:40 am Post subject: |
|
|
Newbie
Joined: 21 Feb 2005
Posts: 6
|
Yeah, have successfully managed to write a Java plugin node that calls the EJB,
However, can only get this to work when WAS is installed and extensive usage is made of its jar files, in order to use its corba based JNDI service. This is not an option that is possible outside of a development environment..
Is it possible to access an ejb just using the jdk that comes with WMQI??
What InitialContext should be used? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Feb 21, 2005 8:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You would need support jars for EJBs (j2ee, basically), and for the inital context that is appropriate for the EJB container you are using.
Otherwise you could use regular RMI to talk to another JVM that would then invoke the EJB. But you might run into transactional and class issues with that.
Or you could do as you mentioned, and invoke the EJB using an MDB and a queue. This then turns into a request/reply pattern - and might lead you into aggregation design or use of the MQGet node.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| james_render |
| Posted: Mon Feb 21, 2005 9:25 am Post subject: |
|
|
Newbie
Joined: 21 Feb 2005
Posts: 6
|
yeah, the problem is that the EJB container is WAS and I can't use its support jars (don't ask!!)
Am looking into using another context provider to obtain the reference, which should be interesting as it'll need to work with IBM's JDK. If anyone has any references to looking up WAS deployed EJB's using sun's COS naming service...
| jefflowrey wrote: |
You would need support jars for EJBs (j2ee, basically), and for the inital context that is appropriate for the EJB container you are using.
Otherwise you could use regular RMI to talk to another JVM that would then invoke the EJB. But you might run into transactional and class issues with that.
Or you could do as you mentioned, and invoke the EJB using an MDB and a queue. This then turns into a request/reply pattern - and might lead you into aggregation design or use of the MQGet node. |
|
|
| 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
|
|
|
|
