Jeremy Bauer,
Thanks for your help. Wonderful.
Then the test is passed. I knew the reason.
Thans again.
---
Open Gloves
Jeremy Bauer wrote:
>
> Open Gloves,
>
> Apologies. I did not verify that the insert into the collection actually
> took place. After re-running the test, paying close a
Open Gloves,
Apologies. I did not verify that the insert into the collection actually
took place. After re-running the test, paying close attention to the trace
output, I found the source of the problem. During entity enhancement
several warnings were logged of this form:
1656 sample WARN
Hi,
Thanks for your response.
I hardcoded is just for test @ManyToMany and see the effect. @GeneratedValue
is not the point of this issue.
I also do not think this is the bug of OpenJPA, and I had been modified the
code like your advice before, and It didn't passed test either. because the
test co
Hi,
Interesting that this works on Hibernate. The first potential issue I found
in the test is that it uses a hardcoded id and your entities are annotated
with @GeneratedValue. Depending on how the value is generated, the values
could be different between test runs and providers. Storing away t
IDE Environment: Eclipse-3.4
DB Environment: Apache-Derby-10.5.1.1
JDK Environment: Sun JDK-1.6.0_07
Jar Environment: from
http://openjpa.apache.org/builds/latest/downloads/apache-openjpa-2.0.0-SNAPSHOT-binary.zip
Eclipse PlugIn Environment:Apache-Derby, JUnit4
I want to test the @ManyToMany(the
