I'm rather used to building this sort of optimistic lock feature in
application land. I'm not sure how this would look in an EJB container.
What would the client (i.e. servlet/jsp)'s view of this long transaction
be? would I create a UserTransaction and keep it hanging around in my
session? I don't think i'd like that - I like to be able to differentiate
between the long 'transaction' and the actual DB transactions. Or maybe
that's just me.
On Fri, 27 Oct 2000, marc fleury wrote:
>
> |It will be tough to provide an implementation...
>
> actually it won't be that tough... just some work... do you want that
> feature or not?
>
> Also it strikes as solving only the "update" problem on the *SAME* bean.
>
> In other words... if you have information displayed on the page and you
> update some OTHER bean based on that information then it doesn't work
> anyhow... I don't know.... is it that useful? A long transaction takes care
> of that for everybody and everycase (just let the transaction encompass
> several beans by propagation)... it happens that web transactions are not
> "millisecond things", tough tities ...
>
> marc
>
> |
> |I mean we need to keep the "id" version associated with the client somehow,
> |and that can only be with the proxy...
> |
> |now we need to send and return the version numbers with every
> |call... fine a
> |little overhead but I guess we can live with it.
> |
> |then we need to trap that in the client and fire an exception if there is a
> |version missmatch exception? as what?
> |
> |interesting... what do you folks think of that feature? is it really kosher
> |with EJB (exception and all)
> |
> |
> |marc
> |
> ||-----Original Message-----
> ||From: [EMAIL PROTECTED]
> ||[mailto:[EMAIL PROTECTED]]On Behalf Of Rickard �berg
> ||Sent: Friday, October 27, 2000 4:42 AM
> ||To: jBoss User
> ||Subject: [jBoss-User] Long-running pseudo transactions HOWTO
> ||
> ||
> ||Hey
> ||
> ||In the latest newsletter from TheServerSide.com there is a great tip on
> ||how to solve long running transactions (i.e. how to resolve conflicts
> ||between two users simultaneously viewing and editing EntityBean data).
> ||
> ||Read it here:
> ||http://www.TheServerSide.com/resources/news3.html
> ||
> ||regards,
> || Rickard
> ||
> ||ps. Ingo, this answers your comp.lang.java.beans question re: concurrent
> ||control to EntityBeans!
> ||
> ||--
> ||Rickard �berg
> ||
> ||Email: [EMAIL PROTECTED]
> ||http://www.telkel.com
> ||http://www.jboss.org
> ||http://www.dreambean.com
> ||
> ||
> ||
> ||--
> ||--------------------------------------------------------------
> ||To subscribe: [EMAIL PROTECTED]
> ||To unsubscribe: [EMAIL PROTECTED]
> ||Problems?: [EMAIL PROTECTED]
> ||
> ||
> |
> |
> |
> |--
> |--------------------------------------------------------------
> |To subscribe: [EMAIL PROTECTED]
> |To unsubscribe: [EMAIL PROTECTED]
> |Problems?: [EMAIL PROTECTED]
> |
> |
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
Dan Christopherson (danch)
nVisia Technical Architect (www.nvisia.com)
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
