-
1. Re: The Arquillian test case which sharing super class for deployment only succes with 2 rounds.
aslak Jun 6, 2012 4:44 AM (in response to charlee_ch)What is the exception on #3 and #4?
-
2. Re: The Arquillian test case which sharing super class for deployment only succes with 2 rounds.
charlee_ch Jun 6, 2012 6:38 AM (in response to aslak)There is no any exception. It's just the assertion failure as "The service ejb is null". I've looked at the Eclipse console, the Glassfish embedded log, and the EJB is deployed properly. Could you please help to advise further?
-
3. Re: The Arquillian test case which sharing super class for deployment only succes with 2 rounds.
aslak Jun 6, 2012 8:18 AM (in response to charlee_ch)hmm.. could you try to not cache the EAR archive in a static, but create it for each Test ?
@Deployment public static EnterpriseArchive deploy() { return ArchivePreparation.getDeployingEar(); }
-
4. Re: The Arquillian test case which sharing super class for deployment only succes with 2 rounds.
charlee_ch Jun 7, 2012 3:04 AM (in response to aslak)I apologize for late replying, since I'm at GMT+7 time zone. I would like to inform you that, even I've tried to create the EAR archive for every @Deployment, the result still same.
I also have a chance to set the log level for arquillian to the finest level as the following: -
{code:java} org.jboss.arquillian.level=FINEST {code}
The glassfish embedded log is as the following: -
{code:java}
INFO: EJB5181:Portable JNDI names for EJB DummyService:
[java:global/my-app/my-app-ejb/DummyService!test.com.scc.poc.javaee.service.ejb.DummyServiceable,
java:global/my-app/my-app-ejb/DummyService]
...
Jun 7, 2012 2:00:01 PM org.jboss.arquillian.testenricher.ejb.EJBInjectionEnricher resolveJNDINames
FINER: Trying to resolve JNDI name for field "interface test.com.scc.poc.javaee.service.ejb.DummyServiceable" with mappedName="" and beanName=""
Jun 7, 2012 2:00:01 PM org.jboss.arquillian.testenricher.ejb.EJBInjectionEnricher injectClass
FINE: Could not lookup @javax.ejb.EJB(beanName=, mappedName=, beanInterface=class java.lang.Object, description=, name=, lookup=),
other Enrichers might, move on.
Exception: No EJB found in JNDI, tried the following names: java:global/test.ear/test/DummyServiceableBean,
java:global/test.ear/test/DummyServiceable, java:global/test/DummyServiceable, java:global/test/DummyServiceableBean,
java:global/test/DummyServiceable/no-interface, test/DummyServiceableBean/local, test/DummyServiceableBean/remote,
test/DummyServiceable/no-interface, DummyServiceableBean/local, DummyServiceableBean/remote, DummyServiceable/no-interface,
ejblocal:test.com.scc.poc.javaee.service.ejb.DummyServiceable, test.com.scc.poc.javaee.service.ejb.DummyServiceable,
{code}
If you have any suggestion or any additional testing step, please do not hesitate to let me know. Thank you very much for your help in advance. I'm looking forward to hearing from you soon.
Regards,
Charlee Ch.
-
5. Re: The Arquillian test case which sharing super class for deployment only succes with 2 rounds.
aslak Jun 7, 2012 4:06 AM (in response to charlee_ch)Odd.. it's the same Bean on all of them..
Could you attach the full project, with pom, source, setup etc etc.. I can try to debug it locally.
-
6. Re: The Arquillian test case which sharing super class for deployment only succes with 2 rounds.
charlee_ch Jun 8, 2012 8:05 AM (in response to aslak)Dear Aslak Knutsen,
I apologize for late replying since I prepared the example project and published to the GitHub. I would like to inform you as the following: -
h5. The Glassfish embedded 3.1.2 configuration
1. The project URL is https://github.com/charleech/local-glassfish-embedded-312
2. The step for configuring is https://github.com/charleech/local-glassfish-embedded-312/blob/master/README.md
h5. The multiple deployment example project
1. The parent project URL is https://github.com/charleech/arquillian-evaluation
2. The project URL is https://github.com/charleech/arquillian-evaluation/tree/master/deployment It would be nice to checkout together with the parent project.
3. If you prefer to run unit testing inside the eclipse, please read the step at https://github.com/charleech/arquillian-evaluation/blob/master/deployment/README.md
I hope this information may be useful. If you have any suggestion or have any question, please do not hesitate to let me know.
Regards,
Charlee Ch.
-
7. Re: The Arquillian test case which sharing super class for deployment only succes with 2 rounds.
charlee_ch Jun 14, 2012 8:34 AM (in response to aslak)Dear Aslak Knutsen,
Do we have any chance to found the root cause? or any workaround for archive this issue?
Regards,
Charlee Ch.