Re: [Springframework-developer] Re: JCA support

[Steve L. <spi...@ya...>]

"So for a Spring environment, we don't actually need a
JCA *container* 
in the
sense that it manages the setup of the connectors. All
we need is a JCA
ConnectionManager implementation that is XA-capable
and able to 
interact
with a given javax.transaction.TransactionManager
instance."

So it sounds sort of like running an XA resource in
non-managed mode? As in, no pooling, no security
injection, but participate/coordinate the XA directly
to the ManagedConnectionFactory?

I am planning on putting an interceptor stack in, so
basically it would be using it without the pool
interceptor. To be honest, the XA stuff is the stuff
I'm least familiar with, so I may need some guidance
as I was originally intending on tackling that last.
But I was planning on delegating all the transaction
stuff to JOTM or any other XA manager.

I know I'm sort of reinventing the wheel, but the hard
parts (like JOTM and HOWL, etc) I want to delegate as
much as possible. Make it JavaBean-ish as much as
possible, while still being standard JCA where it is
required.

Thanks,
Steve

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com