On Dec 3, 2009, at 11:20 AM, Piero Sartini wrote:
>> @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.
Can @Inject take a parameter? Can @Commit?
>
> 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.
My memory is a little fuzzy because it was about a month ago, but I had to
switch to Hibernate-3.5.0-SNAPSHOT for those to work, specifically because of
issues on the EclipseLink 2.0 side that were definitely bugs on the EL 2.0
side. I've been planning on switching back to check I just haven gotten to it
yet. All the JPA2 stuff is a moving target remember. If you're using 2.0, you
can't expect it to be stable yet, until about 2 weeks ago, I couldn't do
count(f) from Foo f in Hibernate-3.5.0 and it's still broken in 3.5.0-Beta-2.
>
> 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 :/
Yeah, I had the same problem. I know TestNG well enough, but not EasyMock.
Pierce
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
