[ http://jira.andromda.org/browse/JSF-32?page=comments#action_13751 ]
Arnd Horstmann commented on JSF-32: ----------------------------------- fixed this problem by changing templates.jsf.configuration.validation.xml.vsl line 22: #if $field.validationRequired && $actionParameters.contains($field)) to #if (!$field.readOnly && $field.validationRequired && $actionParameters.contains($field)) suggestion: think about $field.validationRequired returning false for readonly values > readonly Date pretends transition to next state in release 3.2 > -------------------------------------------------------------- > > Key: JSF-32 > URL: http://jira.andromda.org/browse/JSF-32 > Project: JSF cartridge > Type: Bug > Environment: Windows XP > Reporter: Arnd Horstmann > Assignee: Chad Brandon > > model: > 1 use case > 2 FrontEnd-states with appropriate populateScreen-states and transitions > 1 ValueObject with Date-attribute > 1 ValueObject with dummy-attribute to show on second FrontEnd-state > 1 Controller with appropriate populateScreen-methodes > transition between FrontEnd-state 1 and populateScreen-state 2 owns > Date-attribute (according to VO) as readonly-parameter > cartridge: jsf with facelets, androMDA 3.2 > result: the button according to the transition with readonly-Date-parameter > does not work. It worked in androMDA 3.2-SNAPSHOT, but there is no > significant difference in the generated output... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.andromda.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
