[
https://issues.apache.org/jira/browse/TAPESTRY-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-1922.
------------------------------------------
Resolution: Fixed
I will sheepishly admit I didn't test this, so please try out the snapshot
tomorrow and give it a whirl. My solution was slightly more involved, it uses
the component class loaders, whose parent is the context class loader, and it
passes it around a bit so that we don't constantly have to figure out the right
loader. Final is the new private and all.
> EJB3 Beans can not be referenced as properties inside JBoss 4.0
> ---------------------------------------------------------------
>
> Key: TAPESTRY-1922
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1922
> Project: Tapestry
> Issue Type: Bug
> Affects Versions: 5.0.7
> Environment: JBoss 4.2.2
> Reporter: Joachim Van der Auwera
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.7
>
>
> When trying to deploy an application on JBoss which also references my EJB3
> beans, I get a "no classloader found for" exception in the when passing a
> context from one page to the next.
> This seems to be caused by the use of Class.forName in ComponentEventImpl.
> Replacing line 82
> Class desiredType = Class.forName(desiredTypeName);
> with
> ClassLoader loader = Thread.currentThread().getContextClassLoader();
> if ( loader == null ) loader = this.getClass().getClassLoader();
> Class desiredType = Class.forName(desiredTypeName, true, loader);
> Seems to fix this problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
