Sure, I'm working on the test case. About the exception page that don't get
presented, it is an excepted behaviour since the commit 1027208, or I get it
wrong?

https://fisheye6.atlassian.com/changelog/wicket/?cs=1027208


On Fri, Oct 29, 2010 at 3:05 PM, Jeremy Thomerson <[email protected]
> wrote:

> On Fri, Oct 29, 2010 at 11:41 AM, Pedro Santos <[email protected]>
> wrote:
>
> > I'm just concerned about the side effects. A bug on the component data
> > index
> > can cause URL issues. For instance an URL generated for one behavior
> > invoking another behavior on the same component. Then we will have
> > developers evaluating the milestone and returning different problems than
> > the one reported by Nino. But I'm ok releasing the milestone with a note
> > explaining the possible issues.
>
>
> Good point Pedro.  I won't personally have any time to look at this today
> or
> tomorrow.  Perhaps one of the other devs will.  Can you create a quickstart
> that demonstrates another use case where this issue will happen (like you
> describe above)?  Or create a test case for it?  A test case would make
> sure
> that this doesn't ever happen again.
>
> --
> Jeremy Thomerson
> http://wickettraining.com
> *Need a CMS for Wicket?  Use Brix! http://brixcms.org*
>



-- 
Pedro Henrique Oliveira dos Santos

Reply via email to