> �...@commitafter("unit1")
>
> JPA already defines something like this does anyone have an opinion on using
> @Inject vs. @PersistenceContext("unit1")?
Hard to say, but I would prefer @Inject. I like to know that I am
working with the tapestry stuff, not in the JavaEE context. Could be
confusing if we take the same name.
For the rest, I would not try to support two PUs until the jpa module
is more stable and useable. Last time I tried I had still issues with
the ValueEncoders as well as with the PersistenceStrategy under
EclipseLink - right now I am running a custom build without these
features. Didn't have the time to look into them yet.
I've looked at the broken test cases but was not able to fix them.
Seems like much better TestNG and EasyMock knowledge than mine is
needed :/
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
