Thanks.. I set up a choices method, and have to admit I don't like that I have to type something before any choices actually appear.
I can see the use for it later, but when the list is short, it forces an unneeded keypress. Is there any way a domain app service can access the bread crumb list? I saw the autocomplete annotation, thanks. Dan Haywood <d...@haywood-associates.co.uk> wrote: >On 2 Mar 2013 20:32, "Kevin Meyer - KMZ" <ke...@kmz.co.za> 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? >> >> -- Sent from my phone with K-9 Mail. Please excuse my brevity.