[
http://issues.ops4j.org/jira/browse/PAXWEB-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11464
]
Alin Dreghiciu commented on PAXWEB-98:
--------------------------------------
Well, looking at what I committed it cannot work :) Sorry for asking your to
try it out.
I will try another approach and let you know.
> JasperClassLoader causes JSF FactoryFinder to fail during request dispatch
> --------------------------------------------------------------------------
>
> Key: PAXWEB-98
> URL: http://issues.ops4j.org/jira/browse/PAXWEB-98
> Project: Pax Web
> Issue Type: Bug
> Components: JSP Support
> Affects Versions: 0.5.1
> Reporter: Thomas Joseph
> Assignee: Alin Dreghiciu
> Priority: Minor
>
> I am now trying to build JSF application with Pax Web + Extender and
> Whiteboard. I am using Spring DM to register listeners, servlets and jsps
> with the Pax Web Whiteboard.
> I faced some issue that I observed:
> 1. JSF during initialisation stores FactoryClassNames in a HashMap that is
> stored against classloaders (Classloader instance is used as key).
> 2. At all instances (initialisation and during later usage) an instance of
> "BundleClassLoader" is used as the ClassLoader, except for a place where
> there is a EL expression
> 3. At EL expression evaluation it dispatches to JspServletWrapper that uses
> the JaperClassLoader.
> 4. The JSF's hashmap is now queried for FactoryNames against the
> JasperClassLoader (that returns a different hash) and hence a null for the
> FactoryClassNames, which causes a failure in JSF page rendering whenever it
> carries a reference to a ManagedBean.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
