Hi Yiping,
Thanks for your mail, that gave me a valuable hint.
When checking the TestRunnerBean, I saw that it was actually
modified and I for sure hadn’t done this. It turned out that the server
test framework makes a backup copy of the original file (to restore it later)
and modifies the TestRunnerBean class. When struggling with a database error, I
had once interrupted the test execution process manually and got stuck with the
modified version. All I needed to do to get rid of the nasty
persistence-uni-ref-name errors was to revert the TestRunnerBean :-)
Thanks and best regards,
Sabine
From:
Yiping Zhao [mailto:yiping.zhao@xxxxxxxxxx]
Sent: Montag, 8. November 2010 17:14
To: Heider, Sabine
Cc: Dev mailing list for Eclipse Persistence Services
Subject: Re: [eclipselink-dev] Some server test apps can't be deployed
on glassfish v3
There are three things you can check up:
1. if you have "ejb.lookup=false" or the property is commented out in
test.properties
2. if you have "is.JTA=true" in test.properties
3. check to see if you have "TestRunner[1...5]Bean.java" under
jpa\eclipselink.jpa.test\src\org\eclipse\persistence\testing\framework\server,
if you have, try to remove those files
If the above three things are good and the problem is still there, you need to
reinstall GlassFish V3, I met this kind of problem, somehow the server is
corrupted.
Yiping
On 08/11/2010 7:30 AM, Heider, Sabine wrote:
I’ve
got yet another question on running the server tests against a glassfish v3
server.
I’m
now in the situation that I can principally run the server tests, but many
tests suites fail entirely because the test application can’t be
deployed. I get errors like
“Could
not resolve a persistence unit corresponding to the persistence-unit-ref-name
[org.eclipse.persistence.testing.framework.server.TestRunnerBean/entityManagerFactory]
in scope of the module called
[eclipselink-cascadedeletes-model#eclipselink-cascadedeletes-model_ejb.jar].
Please verify your application.”
All
in all, I have around 520 errors, and around 400 of them are caused by this
issue. Any idea what’s wrong here?
I
played a bit around with one of the apps and found out that I can deploy it if
I change the persistence unit name from whatever it is to “default”
in both the persistence.xml file and the ejb-jar.xml - but I don’t really
understand why that works and what the actual problem is.
The
remaining errors are different, and my question here is: Do you ever get
error-free server test runs on glassfish, or is there a list of tests that are
known to be failing (for whatever reasons)?
Thanks
for your help and best regards,
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
