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
WFLY-3989 Setup the right TCCL during endpoint instance creation as well as view instance creation #6852
Conversation
Linux Build 5299 is now running using a merge of 10ae59c |
Linux with security manager Build 291 outcome was FAILURE using a merge of 10ae59c Build problems:Failed tests detected Failed tests
|
Windows Build 406 outcome was FAILURE using a merge of 10ae59c Build problems:Failed tests detected Failed tests
|
Linux Build 5299 outcome was FAILURE using a merge of 10ae59c Build problems:Failed tests detected Failed tests
|
Genuine failures due to a typo in the code. Fixing now. |
…ell as view instance creation
Typo fixed. retest this please |
Linux Build 5300 is now running using a merge of aa14566 |
Linux with security manager Build 292 outcome was FAILURE using a merge of aa14566 Build problems:Failed tests detected Failed tests
|
Linux Build 5300 outcome was SUCCESS using a merge of aa14566 |
WFLY-3989 Setup the right TCCL during endpoint instance creation as well as view instance creation
https://issues.jboss.org/browse/WFLY-3989 describes the issue where the TCCL isn't set to the application's classloader when the MDB object instantiation is being done. As noted in an old (related) discussion http://lists.jboss.org/pipermail/jboss-as7-dev/2011-July/003339.html the user application code is expected to have the correct TCCL (which in this case should be the application's deployment classloader).
This commit fixes the issue by using the right TCCL during the endpoint instantiation as well as the component view instance creation (which in case of MDBs can lead to the MDB implementation object instantiation). The commit also updates the MDBTestCase to verify these changes.
P.S: This needs review from the EE team as well as JCA team. Specifically, the TCCL switch during the view instance creation in ViewService. Although the change fixes this issue and does seem logical, I haven't been in this code for a long time now and I'm not fully sure of its impact.