Skip to content
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

PAYARA-3119 NullPointerException when starting Jersey/EJB Containers with <initialize-in-order> flag true in Ear #3949

Merged
merged 2 commits into from
Jun 24, 2019

Conversation

jGauravGupta
Copy link
Member

@jGauravGupta jGauravGupta commented Sep 28, 2018

Signed-off-by: Gaurav Gupta gaurav.gupta.jc@gmail.com

When multiple WARs are in an EAR with initialize-in-order set to true, and both contain both an EJB and a JAX-RS endpoint, a NullPointerException is thrown on startup. Actually during startup of first module, Jersey provider registers the interceptor for all modules (even other modules are not started in case of ). And during the startup of second module, again Jersey provider registers the interceptor for all modules.

…in Order

Signed-off-by: Gaurav Gupta <gaurav.gupta.jc@gmail.com>
@jGauravGupta jGauravGupta changed the title PAYARA-3119 NullPointerException when starting Jersey/EJB Containers in Order PAYARA-3119 NullPointerException when starting Jersey/EJB Containers with <initialize-in-order> flag true in Ear Sep 28, 2018
@jGauravGupta
Copy link
Member Author

Hi @jansupol,

Can you trigger CI for this PR as test passing for OracleJDK.

Copy link
Contributor

@jansupol jansupol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

EJB's are hard to be tested, currently, there is not a huge number of tests running in an EJB container and we accept the change without a test in Jersey

@senivam senivam merged commit 1719b46 into eclipse-ee4j:master Jun 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants