Re: [Wicket-user] AbortWithWebErrorCodeException not working as expected

2007-05-10 Thread Eelco Hillenius
1.3.x is the next version, and this is in trunk. I've only fixed it for that. If you really need it for 1.2.7, please re-open the issue and state that and selected 1.2.7 in the list. There's no roadmap for 1.2.7. It depends on severity of the bugs we fix for it and how badly people (tell us they)

Re: [Wicket-user] AbortWithWebErrorCodeException not working as expected

2007-05-10 Thread Lowell Kirsh
Thanks for your attention to this. Is there a roadmap of when 1.2.7 will be out? Or is 1.3.0 the next version? On 5/10/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > It was a bug we didn't support it properly, and in trunk it's fixed > now (note that the issue is set to 'resolved'). So put in th

Re: [Wicket-user] AbortWithWebErrorCodeException not working as expected

2007-05-10 Thread Eelco Hillenius
It was a bug we didn't support it properly, and in trunk it's fixed now (note that the issue is set to 'resolved'). So put in that exception again, and you should be good. Eelco On 5/10/07, Lowell Kirsh <[EMAIL PROTECTED]> wrote: > The solution you posted there looks workable. Instead of throwing

Re: [Wicket-user] AbortWithWebErrorCodeException not working as expected

2007-05-10 Thread Lowell Kirsh
The solution you posted there looks workable. Instead of throwing an AbortException, I'd just call RequestCycle.get().setRequestTarget(...). However, it seems that to prevent the rest of my constructor from running (due to the error), I have to explicitly call 'return' (ie. can't use exception to g

Re: [Wicket-user] AbortWithWebErrorCodeException not working as expected

2007-05-10 Thread Eelco Hillenius
See https://issues.apache.org/jira/browse/WICKET-552 On 5/10/07, Lowell Kirsh <[EMAIL PROTECTED]> wrote: > I easily reproduced this problem. I did not use svn access, but > instead went to the wicket main page and downloaded the 1.2.6 > quickstart. I ran it and it worked. Then I went to the Index.

Re: [Wicket-user] AbortWithWebErrorCodeException not working as expected

2007-05-09 Thread Lowell Kirsh
I easily reproduced this problem. I did not use svn access, but instead went to the wicket main page and downloaded the 1.2.6 quickstart. I ran it and it worked. Then I went to the Index.java and inserted the following line in the constructor: throw new AbortWithWebErrorCodeException(HttpServletRe

Re: [Wicket-user] AbortWithWebErrorCodeException not working as expected

2007-05-09 Thread Lowell Kirsh
I will look into it tomorrow... On 5/9/07, Johan Compagner <[EMAIL PROTECTED]> wrote: > yes see our quickstart project in svn > > i can try to build an example for this > for example if i change one of the wicket examples homepages that it throws > such an exception > does it fail then? > > johan

Re: [Wicket-user] AbortWithWebErrorCodeException not working as expected

2007-05-09 Thread Johan Compagner
yes see our quickstart project in svn i can try to build an example for this for example if i change one of the wicket examples homepages that it throws such an exception does it fail then? johan On 5/9/07, Lowell Kirsh <[EMAIL PROTECTED]> wrote: > do you have a quickstart that you can attac

Re: [Wicket-user] AbortWithWebErrorCodeException not working as expected

2007-05-09 Thread Lowell Kirsh
> do you have a quickstart that you can attach to a jira issue? What do you mean by this? Is a quickstart some sort of self-contained minimal jar? - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the F

Re: [Wicket-user] AbortWithWebErrorCodeException not working as expected

2007-05-09 Thread Johan Compagner
that should work fine looking in the code i do see this: RequestCycle.get().setRequestTarget(new WebErrorCodeResponseTarget(errorCode, message)); do you have a quickstart that you can attach to a jira issue? johan On 5/9/07, Lowell Kirsh <[EMAIL PROTECTED]> wrote: I throw an AbortWithWebErr

[Wicket-user] AbortWithWebErrorCodeException not working as expected

2007-05-08 Thread Lowell Kirsh
I throw an AbortWithWebErrorCodeException with status=HttpServletResponse.SC_BAD_REQUEST from my WebPage constructor and my web browser receives a 200 status code and shows a blank page. What am I doing wrong? Thanks, Lowell