[#JSF-32] readonly Date pretends transition to next state in release 3.2

Issue Details [XML]

Key:	JSF-32
Type:	Bug
Status:	Open
Priority:	Major
Assignee:	Chad Brandon
Reporter:	Arnd Horstmann
Votes:	0 (View)
Watchers:	0 (View)

Operations

If you were logged in you would be able to see more operations.

JSF cartridge

readonly Date pretends transition to next state in release 3.2

Created: 24/Nov/06 10:08 AM Updated: 24/Nov/06 01:20 PM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

None

Environment:

Windows XP

Description

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...

All

Comments

Change History

Sort Order:

[ Permlink ]

Comment by Arnd Horstmann [24/Nov/06 10:38 AM]

This behavior occurs on not-required Dates too, so I posted this issue according to JSF-20 and JSF-25

[ Permlink ]

Comment by Arnd Horstmann [24/Nov/06 01:20 PM]

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