This week's book giveaway is in the JDBC and Relational Databases forum.
We're giving away four copies of Murach's MySQL and have Joel Murach on-line!
See this thread for details.
Win a copy of Murach's MySQL this week in the JDBC and Relational Databases forum!

Alex Paransky

Greenhorn
+ Follow
since May 29, 2003
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Alex Paransky

The real problem occurs not when an exception happens while in HTTP call, and then the calling function receives some sort of an exception and rolls back the transaction. The real problem occurs when the HTTP call has finished executing and committed it�s changes to the data-store and then the transaction is rolled back by the client who called the HTTP method to start with. Without XA there is no way to work around this problem.
Here are two scenarious:
EJB A, calls HTTP, error occurs inside of HTTP call, returned to EJB A, EJB A rolls back TX, all is fine and everyone is happy.
EJB A, calls HTTP, HTTP call completes and returns success to EBJ A, EJB A proceeds to execute other functions, and then receives a fatal exception, EJB A attempts to roll-back TX, TX rolls back for EJB A and it�s clients, but changes which have been persisted by the HTTP call are not rolled back.
I don�t think there is a way to reliably implement 2 phase transactions between components which are not participating with the Transaction Manager.
-AP_
http://www.myprofiles.com/member/profile/apara_business
The basic principle behind a Use Case is that it should provide some value to the actor who is corresponding with such a use case. Some use cases could be: Open New Bank Account, Register for BLOG, Transfer funds. Use cases such as: Update Database, Write Log Record, Begin Transaction do not really provide any value to the actor, unless of course, your actor is another system to which Begin Transaction has some value.
On the issue of Use Cases calling other Use Cases, I believe, it is wrong to call it �calling�. A better term is �includes�. For example, Open Bank Account use case could include a Transfer Funds use case in it. Transfer Funds, use case could include Deposit New Funds use case in it.
As another writer pointed out, use cases, are not functions or subroutines that can be called. They are really composed of multiple scenarios. I suppose for the purposes of modeling scenarios one could use state transition or sequence diagrams, however, use cases and code are at different Meta-levels, sort of speak.
-AP_
http://www.myprofiles.com/member/profile/apara_business