I am using geotools since version 2.3.0 and wanted to use all the jdbc stuff in an ejb container. (Especially the db2 extension from Dave Adler)
It is simply not possible to have a global Transaction and to register a geotools spatial jdbc extension to the transaction manager. If you have to modifiy spatial data in one db and to modifiy classic data in another within a transaction using the global transaction manager, the game is over. The primary reason for this is that the plugins do commit and rollback statements against the db. For container managed transactions this is forbidden, for bean managed transactions it is simply not right. No db mapping tool/plugin should make decisions about transaction boundaries. As an example, if you look at the EJB 3.0 mapping, there is no interface for transaction handling. (What they call commit is simply executing an sql insert,update,delete to synchronize the cache to the db ), not a db commit. The business logic makes decisions about transaction boundaries, never does a mapping tool/plugin. Summary: At the moment, the jdbc plugins are usefull for client apps (UDIG) and for simple Server Apps, Deployment in an ejb container or web container with a global transaction requirement ist not possible. -- View this message in context: http://www.nabble.com/Geotools-3-Planning---Transaction-Handling-tp18131680p18131680.html Sent from the geotools-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
