Synchronizing with J2EE transaction

Question

Hello,
I am diving into Kodo's ability to synchronize with J2EE transactions. I
have altered JDOFactory and added a method 'getEEPersistenceManager' which
returns a new PM from a singleton EEPersistenceManangerFactory ( much the
same way the code already worked for the JDBCpmFactory... ).
I am using JBoss and added the line
<tm-location>java:/TransactionManager</tm-location> to my system.prefs file
as specified in the docs, but when I run my simple test case, I get a
java.util.MissingResourceException: tm-location.
Has anyone else tried integrating transactions with JBoss, and if so, did
you have any problems like this? Sorry for the somewhat undetailed post, I
know this is a bit of a long shot...
Thanks in advance,
Eric Lindauer

Answer 1

READ the last part
Abe's response:
To use Kodo with an external datasource from JNDI, do the following:
1. Make sure the system.prefs are set up correctly. Even though Kodo will
be using an external datasource, it still needs to know how to connect to
the DB itself so that it can use external connections for getting sequence
numbers and getting the list of persistent classes (if you're not using the
<persistent-types> array in prefs).
If you like, the system.prefs can point Kodo to a different database than
your production one, so long as you don't mind Kodo creating a sequence
table in this DB and so long as you're using the prefs to list your
persistent types, or have used the schematool to register all your
persistent types with this second datababse.
2. Set the JNDI location of the external datasource in the
PersistenceManagerFactory via the setConnectionFactoryName() method. When
Kodo needs a datasource, it will see that you've given it a location to look
for one in JNDI. It will obtain a JNDI Context and perform a lookup on the
given location, casting the result to a javax.sql.DataSource.
To obtain the Context, Kodo by default will simply create a 'new
InitialContext ()'. This means that your system JNDI properties should be
set up correctly for the JNDI provider you are using (see the
javax.naming.Context javadoc for details).
You also have the option of completely controlling how Kodo obtains the JNDI
context by implementing your own com.techtrader.modules.jndi.ContextProvider
and telling Kodo to use your custom implementation in system.prefs. As the
user guide mentions, this is covered in the javadoc for the
com.techtrader.modules.jndi package.
That's all there is to it. A couple of warnings, though:
* The use of external datasources is untested.
* If using the datasource within an appserver, the Connections from it
should not be automatically committed/rolled back with the completion of the
global transaction. Kodo performs its own transaction management on the
Connections it uses. In future releases we'll be able to handle Connections
that are controlled by the appserver.
Good luck.
-- Abe White
TechTrader
Eric Lindauer <[email protected]> wrote in message
news:[email protected]...
Hello,
I am diving into Kodo's ability to synchronize with J2EE transactions. I
have altered JDOFactory and added a method 'getEEPersistenceManager' which
returns a new PM from a singleton EEPersistenceManangerFactory ( much the
same way the code already worked for the JDBCpmFactory... ).
I am using JBoss and added the line
<tm-location>java:/TransactionManager</tm-location> to my system.prefsfile
as specified in the docs, but when I run my simple test case, I get a
java.util.MissingResourceException: tm-location.
Has anyone else tried integrating transactions with JBoss, and if so, did
you have any problems like this? Sorry for the somewhat undetailed post,I
know this is a bit of a long shot...
Thanks in advance,
Eric Lindauer