Jvrg Schorr wrote:
>
> Hi,
>
> sorry, actually I had the mistake only when another EJB was calling it (and
> not from a servlet for example).
> It was coming from a mistake in the ejb-jar.xml, because by mistake my
> ListManager was the only one where the transaction was set to 'Bean' and the
> others were set to 'Container'.
> That's the reason, now whether it is normal or not I cannot tell... I
> haven't checked the spec.
>
> Thanks a lot for your answer,
And thanks for your help.
> jorg
>
> PS - do you still want me to check if [ListManager] Cannot import
> transaction ...... appears somewhere?
Yes. That should be the only way this could happen.
But I think that message only occurs if the transaction
is propagated from another VM.
Did you run all your enterprise beans in the same VM?
Actually I am also interested what is in the server log
just before the snippet you included.
Would it be possible for you to mail me (privately) the
entire server log?
Best Regards,
Ole Husgaard.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
