On Sun, Feb 20, 2011 at 9:33 AM, Ulrich Stärk <[email protected]> wrote:
> I'm just guessing, but Tapestry might reorder accessor methods alphabetically 
> when enhancing the
> page class.

Hm. I'm also seeing this behavior on Java Beans now if they implement
an interface and are Injected into the page.  Should I file this as a
bug or is it intentional.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to