-
1. Re: Regarding Message Inflow of JCA 1.5
starksm64 Jan 5, 2005 12:49 PM (in response to yogs)No, inflow is for one-way communication. JCA is about making EIS resouces available to J2EE components, not the other way around. For that the EIS integration would use the standard J2EE client apis.
-
2. Re: Regarding Message Inflow of JCA 1.5
adrian.brock Jan 5, 2005 1:59 PM (in response to yogs)If you read the spec, you will see that the message interface can be anything you like
including having a return value
e.g.
public interface MyMessageListener
{
ReturnType onRequest(MyRequest request);
}
Also with jca 1.5 it is possible for a resource adapter to invoke either directly
or using the workmanager (if you want transaction inflow) on an EJB (e.g. an SLSB)
NOTE: Being a newbie does not excuse you from reading the specs before posting
frivilous questions. We are not here so you don't have to do your own work. -
3. Re: Regarding Message Inflow of JCA 1.5
starksm64 Jan 5, 2005 3:52 PM (in response to yogs)Interesting.
-
4. Re: Regarding Message Inflow of JCA 1.5
deejboss Jan 6, 2005 4:34 PM (in response to yogs)Hi,
Here is a good example of inbound resource adapter.
http://www.jboss.org/wiki/Wiki.jsp?page=JBossJCAMessageInflowExample
I have executed it and it works fine.
Here is another for outbound resource adapter.
http://developers.sun.com/sw/building/codesamples/integration_jca.html
Hope this helps.
Thanks