-
Bug
-
Resolution: Cannot Reproduce
-
Blocker
-
None
-
1.1.0.Alpha11
-
None
Project Structure:
Root -> myproject
Child -> mylib
Child -> mywebapp
In "mylib", i have a:
1) de.test.MyController as CDI Bean
2) JSF composite component with the following attribute:
<cc:attribute name="controller" required="true" type="de.test.MyController" />
when the component is included in a view in "mywebapp" and started via wilfly:run, the following exception occurs:
de.test.MyController from [Module "deployment.ROOT.war:main" from Service Module Loader]: java.lang.ClassNotFoundException: de.test.MyController from [Module "deployment.ROOT.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at com.sun.faces.facelets.util.ReflectionUtil.forName(ReflectionUtil.java:100)
at com.sun.faces.facelets.tag.composite.AttributeHandler$CCAttributePropertyDescriptor.getValue(AttributeHandler.java:208)
at com.sun.faces.facelets.tag.jsf.CompositeComponentTagHandler$CompositeComponentMetaRuleset$CompositeMetadataTarget.getPropertyType(Composite
ComponentTagHandler.java:464)
at com.sun.faces.facelets.tag.jsf.CompositeComponentTagHandler$CompositeComponentRule.applyRule(CompositeComponentTagHandler.java:536)
at com.sun.faces.facelets.tag.MetaRulesetImpl.finish(MetaRulesetImpl.java:177)
at com.sun.faces.facelets.tag.jsf.CompositeComponentTagHandler.setAttributes(CompositeComponentTagHandler.java:242)
at com.sun.faces.facelets.tag.jsf.CompositeComponentTagHandler.applyNextHandler(CompositeComponentTagHandler.java:181)
at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:202)
It's very likely that the exception does not belong to the maven plugin but to wildfly core directly.