No, that is in place.
Putting a simpler test component inside the same JAR showed that the
loading is done correctely. So the problem is not the refernciation of the
CC, it is the implementation.
The xhtml of the component is here:
http://svn.codehaus.org/openxma/org.openxma.dsl/trunk/org.openxma.
Hi
I think the problem is mix ui:composition with cc:interface or
cc:implementation. The compiler check these tags and do some special
steps. Just use other different tag like this.
http://www.w3.org/1999/xhtml";
xmlns:h="http://java.sun.com/jsf/html"; >
regards,
Leonardo Uribe
2014-0
Maybe you are missing a faces-config.xml in the jar inside META-INF. JSF
won't scan the jar otherwise. See my post at JSFlive [1] for details.
Best regards
Michi
[1]: http://jsflive.wordpress.com/2011/03/24/custom-component-library/
Am 24.02.2014 13:26, schrieb Johannes Murth:
The output of
The output of DOCTYPE was related to another issue:
The XHTML that is embedded with ui:include had this as root element.
ui:composition as root element solved the problem.
- Side question: is this an official change from 2.1 to 2.2?
But there is still the issue that the composite component from t
Hi,
would be interesting how your composite component looks like (the basic
structure) and how it is embedded in the page.
Best regards
Michi
Am 13.02.2014 13:10, schrieb Johannes Murth:
Hi! I just upgraded from 2.1 to 2.2 and have rendering problem because xml
doctype and html tag are rende
Hi! I just upgraded from 2.1 to 2.2 and have rendering problem because xml
doctype and html tag are rendered right before composite component. These
break the layout and should just be swallowed.
Thanks for any advice!
6 matches
Mail list logo
