Non transactional resources management

[Pedro De Majo]

Hi all,
I'm starting to design a solution for non transactional resources management.
I have some legacy systems accessed by http call which have to act as partecipating in a transaction.
These systems provide an interface working in do/undo way i.e. you can do something like:
http://do.jsp?p=1&c=1 and http://undo.jsp?p=1&c=1

My idea would be to hide one (or more) legacy system behind one XAResource implementation and enlist it (at ejb level)
in a bean managed transaction with others 'standard' resources (connection to db).
I guess will have to consider locking and concurrence issues ...
Have someone approached one similar problem ? Are there different ways to do that?
I'm doing things too much complicated, I'm missing something?
Any tip will be welcome.
Thanks

[Bill Dudney]

Hi Pedro,
If I understand your question it sounds like you might want to consider a J2EE conector. What is your 'non-transactional resource'. If you can cover it with a connector then you'd be good to go and be able to use delcartive transactions from a session facade that could cover your entities and the other resource.
Hope this helps.