Ouch! Frames Bad!
At worst, you could grab the stateful session instance interceptor and
modify it so that you can have your own, non-compliant stack.
Bryan Field-Elliot wrote:
>
> I am developing a web application, in which the web tier is creating a
> Stateful Session bean for each user, and invoking methods on it for all
> business logic.
>
> Problem is, part of my web application requires framesets, and each
> frame pane needs to invoke methods on the session bean. When two frames
> simultaneously load, and their corresponding JSP pages simultaneously
> try to invoke methods on the same session bean, one of them fails with a
> "TRANSACTIONS ROLLED BACK EXCEPTION", having to do with being called
> from the wrong transaction context.
>
> I know that this is the correct behavior per the EJB spec, but what I am
> wondering is, can I configure jBoss to block the second call until the
> first call is done, rather than instantly throw an exception?
>
> This would instantly solve my problem, without writing a ton of extra
> code in my web tier to do syncronization etc.
>
> Thanks in advance,
>
> Bryan
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
Confidential e-mail for addressee only. Access to this e-mail by anyone else is
unauthorized.
If you have received this message in error, please notify the sender immediately by
reply e-mail
and destroy the original communication.
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user