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?

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?


Reply via email to