Yes, that fixed the problem but just to help debug this issue at a later
stage, adding the
public void testMe(String test); creates the same problem also.
It behaves as if I can't change the implementation of User. Please observe
that User extends the acegi UserDetails interface. I am not sure i
Not sure why the presense of the overrideMe() method would change things.
When Tapestry instantiates a bean (such as a User, here) it always
finds the constructor with the *most* parameters. Here it is trying
to instantiate a User instance by injecting a User instance (into your
copy-constructor)
