[ http://issues.apache.org/struts/browse/SHALE-322?page=comments#action_38508 ] Gary VanMatre commented on SHALE-322: -------------------------------------
Hermod, please contribute work on item 1. I put to together something but I don't feel good about it. I'm not sure that we can figure out all we need to know for the TLD. We might need to generate XML files that can be edited. I used the simple Clay markup parser but the java XML parser would be a better choice for the full XML round trip. I also think that we might just use the XML parser in the future. Furthermore, some components will require special JSF converters to convert the String properties into the target component types. For example, the trinidad components have a partialTriggers attributes that is a String[]. Those are just a few of my thoughts but I'd like to see/hear yours. A maven plugin would be really slick. > Lessen the verbose Clay configurations > -------------------------------------- > > Key: SHALE-322 > URL: http://issues.apache.org/struts/browse/SHALE-322 > Project: Shale > Issue Type: Improvement > Components: Clay > Affects Versions: 1.0.5-SNAPSHOT > Reporter: Gary VanMatre > Assigned To: Gary VanMatre > Priority: Minor > Fix For: 1.0.5-SNAPSHOT > > > Lessen the verbose Clay XML configurations for each custom component library > by using alternative sources of meta-data. > 1) Extract the component definitions from JSP TLD's packaged with component > libraries. > 2) Extract Converter, Validator and Listener definitions from the JSF > application factories. > 3) Use java annotations in managed beans or other POJO's to define clay > component definitions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
