DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=37024>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37024 ------- Additional Comments From [EMAIL PROTECTED] 2005-10-12 08:04 ------- (In reply to comment #5) [snip] > Clay does automatically load the base clay-config.xml. The base only > accounts > for the RI components. It would make sense to auto-load all META-INF/clay-config.xml resources, in the same way that a JSF implementation will autoload all META-INF/faces-config.xml resources. > > My thought was that if you choose the myfaces runtime, it is likely that you > will want to take advantage of the tomahawk components and why start from > scratch. I see what you mean in terms of trying to accommodate for all > component libraries but that might also be an interesting problem to have > too :-) > > Would the struts wiki be a better location than clay-plugin/src/conf/ as Mike > has suggested? > No ... the tomahawk.jar file should include a META-INF/clay-config.xml file to define its components for Clay, a META-INF/facelets-config.xml (or whatever Facelets uses) for Facelets, and similar files for whatever other view handler technology this component library wants to support. That way, you get zero-config-file-modification deployment of a component library that is Clay-compliant, no muss no fuss. > > > -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
