Hey
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?
HM.. I think you got it backwards.. this is something that is done by
the *bean* developer not the container developer.. as noted in earlier
post I can (easily) add this to the EJBDoclet templates so that there's
no extra work to be done by the bean developer.
> 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 ...
As above. This is a bean thing that is application dependent. If it
makes sense in a particular application for a particular bean, then use
it.
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
