I think we should revert 1139 [1]: I warned against this in the comments and behold... we are in shit. It is causing more problems than it solves. Basically we have been able to work with Wicket in production systems for over 3 years now without 1139. Now we did apply it, and we are unable to ship 1.3.
Martijn [1] WICKET-1139-comment<https://issues.apache.org/jira/browse/WICKET-1139#action_12541299> On Dec 27, 2007 8:55 PM, Matej Knopp <[EMAIL PROTECTED]> wrote: > Do the error pages work already in IE, because that's quite a blocker > I think :) Is there a jira entry for it? > > -Matej > > On Dec 27, 2007 8:05 PM, Frank Bille <[EMAIL PROTECTED]> wrote: > > On Dec 27, 2007 7:26 PM, Frank Bille <[EMAIL PROTECTED]> wrote: > > > > > IMHO this is required to be fixed before 1.3 final, but I will look at > it > > > now: > > > > > > https://issues.apache.org/jira/browse/WICKET-1241 > > > > > > > I mean: > > https://issues.apache.org/jira/browse/WICKET-1224 > > > > Frank > > > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0-rc2 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-rc1/
