geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: Enlisting XAResource objects
Date Thu, 24 Nov 2005 18:38:41 GMT
>I was going to mention that :-).  You still haven't told me how your 
>(presumably j2ee) application finds the part of the RM to talk to. 
>This could be an important part of the picture :-).

Applications invoke our own user-transaction-like class, which keeps
track of the change set. So when that happens, if I can find the 
manager then I can call getTransaction.enlistResource(XAResource).

It looks like any gbean can use the kernel (or some other object, I
can't remember) to invoke any method on any other gbean, so I can do
that too. Although I am going to write a gbean to emulate a startup
class so I can also use a reference.

Thanks a lot for the detailed description of how to write a recoverable
resource manager. I just realized that since my cache has no persistent
state independent of the db, so I don't need recovery.

If I did want to get list under the "ResourceManagers" collection I would
have to change the j2ee-server plan, whereas I would prefer to use an 
plan. However, you could add a line in a future release for RMs which are
not JCA-based:

<references name="ResourceManagers">


        <pattern><gbean-name> <!-- pattern for other third-party RMs -->



In compliance with applicable rules and regulations, Instinet
reviews and archives incoming and outgoing email communications,
copies of which may be produced at the request of regulators.
This message is intended only for the personal and confidential
use of the recipients named above.  If the reader of this email
is not the intended recipient, you have received this email in
error and any review, dissemination, distribution or copying is
strictly prohibited. If you have received this email in error,
please notify the sender immediately by return email and
permanently delete the copy you received.  

Instinet accepts no liability for any content contained in the
email, or any errors or omissions arising as a result of email
transmission. Any opinions contained in this email constitute
the sender's best judgment at this time and are subject to change
without notice.   Instinet does not make recommendations of a
particular security and the information contained in this email
should not be considered as a recommendation, an offer or a
solicitation of an offer to buy and sell securities.


View raw message