All,
<vendor>
First off, I understand the request to reduce the number of product
specific postings to this group. However, that puts us in a bind:
a) Don't respond, giving our customer the feeling that we are
unwilling to help with their problem.
b) Respond, provoking the ire of others in the group.
So, what I am trying to do is quickly answer the question, and also
suggest to the user to ask such questions on our news groups. Is
this workable?
Amanda,
What this message indicates is that the Container has observed that
you have used a particular stateful session bean first in one transaction,
and then in another transction, before the first transaction has
completed. This is not allowed by the EJB specification: stateful
session beans can only be used in serial completed transactions.
If this is not enough to resolve the issue, please post to:
news://newsgroups.borland.com/inprise.public.appserver
One last comment: I don't understand why you are using Handles. EJB
object references are perfectly valid parameter types. Wrapping
and unwrapping EJB object references into EJB Handles is probably
a waste of time. Is this a legacy from another AppServer?
</vendor>
-jkw
Amanda Sinton wrote:
>
> Can anybody give me any insight as to what I'm falling foul of here? I
> have three stateful session beans, call them A, B and C. The client
> maintains a Handle to bean C, which it passes in the AHome.create() call
> when it creates an A. A gets the actual object from the Handle, and
> holds onto it. The client then calls a method on A, which requires it to
> create a B, passing a Handle to C in the call. B then gets C from the
> Handle, and attempts to call a method on it. At this point, the
> following exception is thrown:
>
> javax.transaction.InvalidTransactionException: Cannot invoke a bean
> first in one transaction, and then in another
> at com.inprise.ejb.Dispatcher.doInvoke(Dispatcher.java, Compiled Code)
> at com.inprise.ejb.Dispatcher.invoke(Dispatcher.java, Compiled Code)
> at com.inprise.ejb.Dispatcher.invoke(Dispatcher.java, Compiled Code)
>
> All methods on the three beans are defined as transaction REQUIRED. Can
> somebody point me in the direction of a possible solution?
>
> Thanks,
>
> Amanda S.
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
