-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor assembly module tests #1546
Conversation
TSNamingContext lookup issue: I was getting When I added glassfish-naming.jar in the classpath I am getting below:
Hi @dmatej Would you know if setting java.naming.factory.initial(I tried setting it to com.sun.enterprise.naming.impl.SerialInitContextFactory, it did not help) or any other property would help fix this issue with glassfish. cc @gurunrao |
This sounds like OmniFish-EE/arquillian-container-glassfish#4 to me. The symptoms are any test that involves Jakarta EE Application Client deployment trying to call an EJB bean but only the EJB client classes are expected to reside in the Application Client, the EJB bean implementation is expected to only be available via the GlassFish Platform implementation (server). The cause is that the GlassFish server is not started and the test EAR is also not copied to the GlassFish server. I tried to hack around this by pre-starting the GF server but we really need proper support for starting the GlassFish Application Client and Server (as well as copy EAR deployment to both). |
This is a different issue. @alwin-joseph you need to synch your fork with the current main branch as with the following changes:
I'm seeing CNFE errors due to missing changes in other modules in the platform-tck. |
Merging this now to address the test failures separately. |
Fixes Issue
#1477
Describe the change