This one time, at band camp, David Jencks said:
DJ>I really can't tell what you are doing from your description, and you
DJ>appear at one point to imply that you have a BMT entity bean which is
DJ>impossible.
DJ>
DJ>The spec is trying to lead you, in a stateless session bean, to code ut
DJ>usage something like this:
DJ>
DJ>ut.begin();
DJ>try {
DJ>//do something
DJ>} finally {
DJ>ut.commit();//or rollback
DJ>}
DJ>
DJ>Is this what you have?
I'm way too caught up deciphering this damn architecture that I've
inherited. Your example just made it through my thick skull! Must each
operation be wrapped in a UT on the bean side? If so, the client side
calls would be similar to this:
1) client call doWork() method of bean
rather than this:
1) call to bean to begin tx
2) do some work here
3) call to bean to commit tx
Correct?
If this is true, how can I expose UserTransactions out to a client so
that developers have the ability to start, stop or rollback transactions?
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
