> because he wants to link to a page, the obvious component is PageLink and it
> takes a Page instance in its contructor - so its the most obvious way to
> link to a page for a noob.

Erm. Maybe. I didn't get that from his email.

> you guys keep outvoting me on removing that
> constructor, but its just causing problems :) The whole class is not even
> necessary. You have Link and BookmarkableLink, implementing the auto-enable
> is as simple as overriding isenabled().

Huh? Who is 'you guys'? I don't remember a formal vote, and if there
would have been any the last year I would have voted +1 for removal -
certainly after we had setResponsePage. So start a vote then.


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
Wicket-user mailing list

Reply via email to