[ http://issues.apache.org/jira/browse/MYFACES-970?page=comments#action_12360993 ]
Dennis Byrne commented on MYFACES-970: -------------------------------------- I have a test that already marshalls the tld document into an object model. http://cvs.sourceforge.net/viewcvs.py/jsf-comp/test/src/java/net/sf/jsfcomp/test/AbstractTagLibTestCase.java?rev=1.1&view=auto It would be trivial to put some beanUtils assertions in a for loop for this. I can adapt this if you'd like, but this means adding a maven-taglib plugin to the myfaces repository. > Verify attributes in TLD match setters in Tag class > --------------------------------------------------- > > Key: MYFACES-970 > URL: http://issues.apache.org/jira/browse/MYFACES-970 > Project: MyFaces > Type: Test > Components: General > Reporter: Simon Kitching > Priority: Minor > > A few times MyFaces has had problems where a TLD declares an attribute but > there isn't any such setter on the Tag class. > It should be possible to check for this in a unit test: > * use Class.getResource to fetch the TLD file > * for each <tag> element in the TLD > * instantiate the specified tag class > * for each <attribute> tag > * verify there is a matching setter on the tag instance > This would need to be applied to myfaces_core.tld, myfaces_html.tld, > tomahawk.tld and sandbox.tld. > Therefore base code for this could go in "share" with the actual test class > (specifying the tld file) in the > various subproject tests. > I'm planning to tackle this in the next few weeks, but anyone else with an > itch to implement this straight away is welcome :-) -- 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
