On 2 Mar 2013 20:32, "Kevin Meyer - KMZ" <[email protected]> wrote:
>
> Hi,
>
> Am I going crazy or is the Wicket Viewer missing something...
>
> I can't get the Wicket Viewer to pick up a previously-viewed object as
> a parameter to an action.
>
> I thought that if you viewed an object it became available for use as
> an action parameter? Or is that only the HTML viewer?
That's the html viewer.
With the wicket viewer, and you either use choices, and as you say, or you
can use the @Autocomplete annotation.
There's a example in the simple to do app that w use for the archetype.
Cheers,
Dan
> I now have a situation where one of my domain objects has a method
> that I can't call:
>
> public class Equipment {
> public boolean checkConnectedTo(Equipment equipment2) {
> ...
> }
> }
>
> I can not assign any value to the parameter... or choose any other
> existing Equipment.
>
> Once I got the "Claims" application working with Wicket, I found that
> the same thing happened when I tried the "claimsFor" action from the
> Claims service...
>
> Do I explicitly have to provide "choices" methods?
>
>
