[ 
https://issues.apache.org/jira/browse/ISIS-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875048#comment-13875048
 ] 

Dan Haywood commented on ISIS-637:
----------------------------------

In fact, there are two errors:
- a required (entity link) drop-down was not validating correctly, so did not 
show its feedback message
- the validation message also was not shown.

In both cases, the StalePageException arises because of a spurious call to 
setResponsePage, which results in the HTML of the entity page being sent back 
to the Wicket ajax code.... hence it flashing red.  That's been removed.

The missing required message is due to the cr*ppy way in which the 
EntityLinkSelect2Panel (a subclass of FormComponentPanel) wraps the 
Select2Choice (itself also a FormComponent).  

> StalePage exceptions ... when omitting mandatory entity drop-down in action 
> prompt 
> -----------------------------------------------------------------------------------
>
>                 Key: ISIS-637
>                 URL: https://issues.apache.org/jira/browse/ISIS-637
>             Project: Isis
>          Issue Type: Bug
>          Components: Viewer: Wicket
>    Affects Versions: viewer-wicket-1.3.1
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: viewer-wicket-1.4.0
>
>
> This can be reproduced in Estatio.   Make sure to uncomment the 
> InvoiceService#validateCalculateInvoiceForProperty method.
> # install the demo fixtures (Administration>install demo fixtures)
> then:
> # Invoices > calculate invoices for property
> # leave the first drop-down (for property) deliberately empty 
> # Hit OK.
> Get no error message, though the Wicket ajax box flashes red indicating 
> somethings wrong.
> Now enter a valid property in the drop-down, 
> ... triggers stale page exception.
> Alternatively you can also enter a period end date which lies before a period 
> start date.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to