mcr wrote:
> I took a look at the geotools transaction and state objects.
>
> The first thing is a minor issue, state and transactions should use the
> "Composite Design Pattern", it should be possible for transactions to be part
> of another transaction.
>
I can see how that would be useful;
I took a look at the geotools transaction and state objects.
The first thing is a minor issue, state and transactions should use the
"Composite Design Pattern",
it should be possible for transactions to be part of another transaction.
The big problem, and I think we should put our focus on the
mcr wrote:
> What J2EE apps do you mean. A Web App or en EJB Container.
>
I mean an EJB Container; hold a geotools DefaultTransaction in your session.
> J2EE Transactions are not jdbc transactions. A J2EE Transaction coordinates
> many jdbc and jms resources (all resources which are able to do
What J2EE apps do you mean. A Web App or en EJB Container.
J2EE Transactions are not jdbc transactions. A J2EE Transaction coordinates
many jdbc and jms resources (all resources which are able to do a 2 Phase
Commit).
If you use a Container Managed Transaction the only
thing you can do is
Nice one! One thing you should be able to do is either:
- make a Java EE specific Transaction; or
- hold a Transaction as an object associated in your sesssion
(ie if you want to get this done today - can we make a separate email
thread to sort out the details?)
We do this for uDig (each map has
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
m
