[
https://issues.apache.org/jira/browse/CAUSEWAY-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Keir Haywood updated CAUSEWAY-1659:
------------------------------------------
Description:
HMM, WE DON'T HAVE A WAY TO REPRODUCE in the demo app... I've realized in
writing this up that the demo itself is flawed, because this can only work for
entities, not for view models (where a change of state is in effect a different
instance).
Even so, I think that the feature is still broken.
to reproduce ? (no, see statement above):
demo app
go to ActionLayout > redirectPolicy
Click on "Increment redirect only if differs"
what should happen is that the counter should be incremented, but the timestamp
should remain unchanged because of two things:
a) that the redirect policy is set to "only if differs", while the returned
object does _not_ differ
b) the timestamp property is set to "don't repaint".
Some earlier analysis:
eg:
{code:java}
public SomeObject toggle() {
setFlag(! isFlag());
return this;
}
{code}
will cause a redirect to the same page, even though the same object is being
rendered.
The reason is because the current viewer implementation does not expose the
AjaxRequestTarget. Need some deep surgery somewhere...
was:
eg:
{code}
public SomeObject toggle() {
setFlag(! isFlag());
return this;
}
{code}
will cause a redirect to the same page, even though the same object is being
rendered.
The reason is because the current viewer implementation does not expose the
AjaxRequestTarget. Need some deep surgery somewhere...
> [demo app] Reinstate Support for RedirectFacet
> ----------------------------------------------
>
> Key: CAUSEWAY-1659
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-1659
> Project: Causeway
> Issue Type: Improvement
> Components: Viewer Wicket
> Reporter: Daniel Keir Haywood
> Assignee: Andi Huber
> Priority: Minor
> Fix For: 2.0.0
>
>
> HMM, WE DON'T HAVE A WAY TO REPRODUCE in the demo app... I've realized in
> writing this up that the demo itself is flawed, because this can only work
> for entities, not for view models (where a change of state is in effect a
> different instance).
> Even so, I think that the feature is still broken.
>
> to reproduce ? (no, see statement above):
> demo app
> go to ActionLayout > redirectPolicy
> Click on "Increment redirect only if differs"
> what should happen is that the counter should be incremented, but the
> timestamp should remain unchanged because of two things:
> a) that the redirect policy is set to "only if differs", while the returned
> object does _not_ differ
> b) the timestamp property is set to "don't repaint".
>
> Some earlier analysis:
> eg:
> {code:java}
> public SomeObject toggle() {
> setFlag(! isFlag());
> return this;
> }
> {code}
> will cause a redirect to the same page, even though the same object is being
> rendered.
> The reason is because the current viewer implementation does not expose the
> AjaxRequestTarget. Need some deep surgery somewhere...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
