Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Long-Lived Transactions  RSS feed

 
Alexander Lebedev
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We are now working on a big j2ee project (moving billing system from Oracle Forms to j2ee). One of an important requirement is to keep record locking mechanism provided by Oracle Forms in a new system. Another important requirement is to use connection pools.
Does anyone has an experience to move systems from Oracle Forms to j2ee? And how do you implement locking mechanisms in your j2ee apps?
Regards,
alex.
 
Simon Brown
sharp shooter, and author
Ranch Hand
Posts: 1913
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
For those of us that aren't familar with Oracle Forms, could you quickly explain what locking mechanism they provide for you?
Cheers
Simon
 
SJ Adnams
Ranch Hand
Posts: 925
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
things like "select for update".
 
Alexander Lebedev
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Simon Brown:
For those of us that aren't familar with Oracle Forms, could you quickly explain what locking mechanism they provide for you?
Cheers
Simon

By default Oracle Forms uses the following locking mechanism (chapter from Oracle Forms help):
"Specifies that Form Builder should attempt to lock the corresponding row immediately after an end user modifies an item value in a queried record. With this setting, Form Builder locks the record as soon as the end user presses a key to enter or edit the value in a text item."
 
Chris Mathews
Ranch Hand
Posts: 2712
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Alexander Lebedev:
Does anyone has an experience to move systems from Oracle Forms to j2ee? And how do you implement locking mechanisms in your j2ee apps?

Long-lived system transactions should be avoided at all costs. They are too much trouble.
However, you can have a business transaction that spans multiple system transactions. I highly suggest you get a copy of
Patterns of Enterprise Architecture. The book does a wonderful job addressing these and many other issues. In particular, you will be interested in the Optimistic Offline Lock Pattern and the Pessimistic Offline Lock Pattern. This is really good stuff.
 
Alexander Lebedev
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
May I implement checkin/checkout locking mechanism on application server?
What patterns (if exists) can I use to implement this mechanism?
We currently work with Weblogic 7.0. And we don't use entity beans for performance reasons.
 
Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!