-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Brian the only place I set it, as you can see from my code, *IS* within
the transaction.  Other wise I would have set it in the action which
calls this method.  I could not find another way to get the insert to
work.  As you could see from my explanation, setting the user_id in the
UserInfoBean would still make UserInfoBean think the ID was empty, hence
I figured something about the transaction was breaking the state
somehow.  I don't know what's going on under the hood, I honestly
haven't looked.

But I understand your point and I agree, there is no need to do this
outside the transaction boundary.

Thanks for your suggestion though, it's what triggered the solution.
R

Brian McCallister wrote:

| On Tuesday, November 18, 2003, at 06:35 PM, Robert S. Sfeir wrote:
|
|> Second, you can't just set the userID like I did, you have to pass the
|> full bean of the first table to the second table.
|
|
| Be careful, you don't *need* to set it to maintain integrity outside of
| the transaction boundary, but if both of them are in fact state on the
| object I *would* be sure to set them at the same time so that the object
| state is consistent within the transaction boundaries. Particularly in
| the case of container managed transactions (this isn't necessarily EJb
| containers, I do it in web containers) where something else may be using
| the same object within the same transaction.
|
| I am glad it was solved!
|
| -Brian
|
|
|
| ---------------------------------------------------------------------
| To unsubscribe, e-mail: [EMAIL PROTECTED]
| For additional commands, e-mail: [EMAIL PROTECTED]
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/uruS+cV9vuB27SARAuWeAJ0eGiHLkX9awZBwGE4j5+TCsbphdgCgqzPg
4DawPQFEeV3+9Lbh2c5UeE8=
=B/r4
-----END PGP SIGNATURE-----


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to