Hi Joe,
> Statement: Mutations to entity beans are not written to the DBMS until
> end-of-transaction. Therefore, direct DBMS access after the bean mutation
> and during the same transaction will not reflect the bean's state.
This is only half of the truth. If your DBMS supports distributed transactions
(XA-Interface), in theory it should be possible to let the DBMS-local transaction run
within the global transaction coordinated by JOnAS TM. I have not done it, but it
should work. You have to let TM run in it's own process (there's a switch for that in
jonas.properties; run TMServer.bat to start it) and then you should be able to access
it by JTA to get a reference to the current transaction; with this reference it should
be possible to feed the XA-Interface of the JDBC driver. As I said above, I have not
done this before, but I think it should be working somehow.
HTH
Markus
To: [EMAIL PROTECTED]
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
