Basically I don't think you should have any problems running the jca
container and the tm in something other than the geronimo kernel. The
only real geronimo dependency I can think of at the moment is that
connection factory serialization/deserialization currently relies on
looking up the actual connection manager instance in the geronimo
kernel. If you don't need to support cf serialization (I think it's
pretty silly) you may be able to just ignore this :-).
Please let me know if you run into problems or need tweaks to the code.
I would prefer if possible to support use in other containers without
making people copy and modify the code.
thanks
david jencks
On May 22, 2005, at 5:56 PM, Dmitriy Kopylenko wrote:
Dain Sundstrom wrote:
On May 22, 2005, at 4:05 PM, Dmitriy Kopylenko wrote:
Hi Dain,
thanks for the reply. We'll post do the dev-list. One more thing.
Would it be feasible to package TM and Connector (with pool impl)
as as a separate, reusable modules, let's say geronimo-tx.jar and
jeronimo-jca.jar or something to that effect?
Absolutely. David Jencks has written an fabulous piece of software
here and I personally would love to see it become the implementation
everyone uses. I think that having a single jar along with some
standalone how-to docs would help a ton.
BTW, I added a demonstration of using Spring in the core of geronimo
to wire up beans and for configuration. The spring.xml file I use
for geronimo may help you get the configurations right:
http://svn.apache.org/viewcvs.cgi/geronimo/trunk/sandbox/spring-
assembly/src/conf/server.xml?rev=170517&view=markup
-dain
This is so cool! By looking at the app ctx for Geronimo server, gives
you an overall, clear picture of the server architecture!
Dmitriy.
