>I understood that the bean calls the entity? in which case it is a tx tag
>problem, but if you are right and he is indeed calling the bean from the
>client client/bean and client/bean as opposed to client/bean/bean then yes
>it is broken.
>
>About the only way I can see this working is the client starts the
>transaction and it propagates (which will work in vm only currently) but
the
>BMT stuff will break then
>
>if you are right and that is what he did, good catch
>marc
Hi all,
Thanks for the information, I'm trying to do that, client/bean and
client/bean, and as you told me that doesn't work because the client can't
start the transaction, so I take my code and I change it to do
client/bean/bean, but it doesn't work either, I mean in the bean that I call
from the client y map all the methods of the other bean and create the
second bean in the first bean, so I can call the methods of it from the
first bean, and in the first bean is where I start the transaction in the
create method and commit it in a save method, so as I read in books and in
this list all the methods of any bean created in this bean with it's methods
with required transactions or supports transaction should attach the first
transaction, but when I make a save in the second bean this time called from
the first time it still save the data and when I do a rollback it only make
a rollback of the data in the first bean. I don't know what I am doing
wrong, any help will be well welcome.
Thanks, Oscar.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
