From: Reynolds, James [EMAIL PROTECTED]
Solved - except I have one more issue.
I incorrectly assumed that I had to update the path to the component as
it exists in the tomahawk jar.
Changing it back to the specifications in the wiki, plus adding the
proper renderer-type (that was the missing piece), fixed the problem.
I'm not surprised that facelets needs the rendererType to be specified. Shale
Clay has a similar issue with the tomahawk components. Theses guys
(components) are pretty relaxed on making sure that the component's
getRendererType method is overridden with the correct value. Sometimes they
default to the super class. On the flip side, there seems to be a ton of reuse
with the runtime.
Here's how it looks now for the commandLink:
commandLink
org.apache.myfaces.HtmlCommandLink
javax.faces.Link
-Original Message-
From: Reynolds, James [mailto:[EMAIL PROTECTED]
Sent: Friday, January 26, 2007 11:26 AM
To: MyFaces Discussion
Subject: Tomahawk + Facelets + Shale
I'm having trouble configuring myfaces tomahawk components to work with
my Facelets + Shale environment. Is anyone else using this combination
successfully? I'm attempting to use the 1.1.5 Snapshot jars for myfaces
core and tomahawk. Is anyone here using this combination successfully?
Based on instructions at the facelets wiki, this is what I've done so
far:
I've created a file named tomahawk.taglib.xml under /WEB-INF:
-//Sun Microsystems, Inc.//DTD Facelet Taglib 1.0//EN
http://java.sun.com/dtd/facelet-taglib_1_0.dtd;
http://myfaces.apache.org/tomahawk
commandLink
org.apache.myfaces.component.html.ext.HtmlCommandLink omponent-type
org.apache.myfaces.renderkit.html.HtmlLinkRenderer rer-type
I've registered the file in my web.xml:
...
facelets.LIBRARIES
/WEB-INF/tomahawk.taglib.xml
...
I've referenced the namespace declared in the taglib file in the root
html element of my page as such:
xmlns:t=http://myfaces.apache.org/tomahawk;
Am I missing something?
Thanks
E-Mail messages may contain viruses, worms, or other malicious code. By
reading
the message and opening any attachments, the recipient accepts full
responsibility for taking protective action against such code. Sender is not
liable for any loss or damage arising from this message.
The information in this e-mail is confidential and may be legally privileged.
It
is intended solely for the addressee(s). Access to this e-mail by anyone else
is
unauthorized.