[ http://issues.apache.org/jira/browse/TOMAHAWK-70?page=comments#action_12429030 ] Gary VanMatre commented on TOMAHAWK-70: ---------------------------------------
>I mentioned this already on the mailing list. It's sort of an "all or nothing" >deal like Facelets since once we provide a >configuration, it cannot easily be >changed by the end user short of editing the jar file (maybe I'm wrong about >this, >though). You can override configurations pulled from the jar's META-INF folder by the order that the config files are registered. A core idea in clay is providing metadata inheritance (tiles like). Besides overriding, you can extend a base definition. Even clay HTML views work by extending base component definitions define in the XML configuration file. >And thus, it really needs to make it into our code generator rather than being >a manually-maintained artifact. I agree that generating these would be the best solution. >See the dev discussions on Facelets/Tomahawk and join in! Ya, I thought about doing that but didn't want to be accused of hijacking the thread :-) > Add Support for Shale-Clay to Tomahawk > -------------------------------------- > > Key: TOMAHAWK-70 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-70 > Project: MyFaces Tomahawk > Issue Type: Bug > Reporter: Ryan Wynn > Assigned To: sean schofield > Attachments: clay-config.xml, clay-tomahawk.war > > > Shale-Clay is a very useful library that allows significant reuse of JSF > components. In order to use Clay with Tomahawk, the Tomahawk jar would need > to package a clay configuration in the META-INF folder of the jar. If Clay > is used, this file will automatically be picked up by Clay. None Clay users > would not be affected by the presence of the file. Attached is a base Shale > configuration file for Tomahawk. Please consider adding this file to > Tomahawk. It will eliminate the need for those wanting to use Shale-Tomahawk > from having to create the file themselves. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
