[
https://issues.apache.org/jira/browse/CAUSEWAY-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Keir Haywood updated CAUSEWAY-3175:
------------------------------------------
Component/s: Viewer Wicket
(was: Docs & Website)
Description:
still an issue as of 2.0.0-RC3 and 2.0.0-RC4. Have also confirmed its a
problem even for the regular programming model, not just Parameters model.
repro using 'CAUSEWAY-3175' branch of helloworld app (jdo)
* create a HelloWorld object
* create two child objects, 'aaa' and 'bbb'
* use "LookupChildUsingChoices" - this works ok
** can select the parent HelloWorldObject in first param
** both children are listed in second param
* use "LookupChildUsingAutoComplete" - this doesn't work
** can select the parent HelloWorldObject in first param
** but there is no drop-down in the second param.
~~~~
original issue text:
Brian:
Meanwhile, I was following the M7 cheat sheet for contributed actions with
static Parameters class. The choicesXxx() method works but not the
autoCompleteXxx() one. [...] it'd be good to ensure that code that follows the
last page of the cheat sheet is intact. For one thing, I needed to add
@Programmatic to the Parameters class to get past metamodel validation.
was:
still an issue as of 2.0.0-RC3
repro using 'CAUSEWAY-3175' branch of helloworld app (jdo)
* create a HelloWorld object
* create two child objects, 'aaa' and 'bbb'
* use "LookupChildUsingChoices" - this works ok
** can select the parent HelloWorldObject in first param
** both children are listed in second param
* use "LookupChildUsingAutoComplete" - this doesn't work
** can select the parent HelloWorldObject in first param
** but there is no drop-down in the second param.
~~~~
original issue text:
Brian:
Meanwhile, I was following the M7 cheat sheet for contributed actions with
static Parameters class. The choicesXxx() method works but not the
autoCompleteXxx() one. [...] it'd be good to ensure that code that follows the
last page of the cheat sheet is intact. For one thing, I needed to add
@Programmatic to the Parameters class to get past metamodel validation.
Issue Type: Bug (was: Documentation)
Summary: Dependent Autocomplete facet not picked up (was:
Autocomplete facet with Parameters programming model is not picked up )
[~hobrom] - could you pick this one up ? I don't really have a good handle on
the way in which parameters are bound within the Wicket viewer, so I think you
might get to the bottom of it rather quicker than I would.
The 3175 branch for helloworld demo's the issue.
> Dependent Autocomplete facet not picked up
> -------------------------------------------
>
> Key: CAUSEWAY-3175
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3175
> Project: Causeway
> Issue Type: Bug
> Components: Viewer Wicket
> Affects Versions: 2.0.0-RC2
> Reporter: Andi Huber
> Priority: Major
> Labels: hello-world, reproduced
> Fix For: 2.0.0-RC5
>
>
> still an issue as of 2.0.0-RC3 and 2.0.0-RC4. Have also confirmed its a
> problem even for the regular programming model, not just Parameters model.
>
> repro using 'CAUSEWAY-3175' branch of helloworld app (jdo)
> * create a HelloWorld object
> * create two child objects, 'aaa' and 'bbb'
> * use "LookupChildUsingChoices" - this works ok
> ** can select the parent HelloWorldObject in first param
> ** both children are listed in second param
> * use "LookupChildUsingAutoComplete" - this doesn't work
> ** can select the parent HelloWorldObject in first param
> ** but there is no drop-down in the second param.
>
>
> ~~~~
> original issue text:
> Brian:
> Meanwhile, I was following the M7 cheat sheet for contributed actions with
> static Parameters class. The choicesXxx() method works but not the
> autoCompleteXxx() one. [...] it'd be good to ensure that code that follows
> the last page of the cheat sheet is intact. For one thing, I needed to add
> @Programmatic to the Parameters class to get past metamodel validation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
