Re: Message Inflow contract in a non-managed environment
Hrishikesh Barua <[email protected]> Thu, 24 May 2007 11:32:18 +0530
| Newsgroups | gmane.comp.java.sun.connector |
|---|---|
| Message-ID | <001501c79dc9$1c2e9270$c501a8c0@hrishikesh> |
Hi Stephen,
The spec does not specifically talk about message inflow in a
non-managed environment - because as you pointed out - there are no MDBs in
a non-managed environment.
>>So, what would act as the endpoint in the
>>non-managed enviroment?
POJOs , implementing the message listener interface. So you would need a
POJO container which supports this.
I guess that the contract can be 'made to apply' in an NME not for MDBs but
for other Java objects which are message listener implementations. In
addition, there must be an implementation of the MessageEndpointFactory and
related interfaces for hooking into the RA.
Regards
Hrish
----- Original Message -----
From: "Stephen New" <[email protected]>
To: <[email protected]>
Sent: Thursday, May 24, 2007 10:58 AM
Subject: Message Inflow contract in a non-managed environment
> Hi,
>
> I have a question about the Message Inflow contracts in JCA 1.5. Does the
> Message Inflow contract provide for the possibility of using a JCA
> Resource
> Adapter in a non-managed environment?
>
> Most of the specs, documentation, articles that I read talk about using
> Message Driven Beans as the endpoints for the asynchronous messages coming
> from the Resource Adapter. However, in the non-managed environment you
> would
> not have any Message Driven Beans. So, what would act as the endpoint in
> the
> non-managed enviroment?
>
> Chapter 12 of the JCA 1.5 spec says that the Message Inflow contract
> "allows
> a resource adapter to asynchronously deliver messages to message endpoints
> residing in the application server". Does this imply that in a non-managed
> environment (without an application server) that this contract does not
> apply?
>
> Regards,
> Stephen
>
> --
> Stephen New
> Rules Architect
> Object Connections Australia
> W. www.objectconnections.com
>
> ===========================================================================
> To unsubscribe, send email to [email protected] and include in the
> body
> of the message "signoff CONNECTOR-INTEREST". For general help, send email
> to
> [email protected] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff CONNECTOR-INTEREST". For general help, send email to
[email protected] and include in the body of the message "help".