> I think we also call this a bug :) see > http://issues.apache.org/jira/browse/WICKET-791
Yes, but I did want to suggest that someone reconsider having the method in the first place. If it's there people will tend to call it, but committers who know better won't and also might not remember to update it as the API changes, then it becomes a bug again. ;) It's supposed to help IDEs suggest a good constructor, but as far as I can tell Eclipse doesn't do that. Balanced against the work to maintain and test it, and the weirdness of having unused parameters, I don't think it's worth it. But I'll let you guys decide that--I'm off to the mountains! Nathan ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ IMPORTANT NOTICE: This mailing list is shutting down. Please subscribe to the Apache Wicket user list. Send a message to: "users-subscribe at wicket.apache.org" and follow the instructions. _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
