Worked like a charm, thanks!
https://github.com/apache/syncope/commit/f5f0bf05cd88e8d5ab6e682f7e1bb6f3c3249c82#diff-1b179dcf722c88b5094875ab9d08d6e3R65
Regards.
On 2020/01/10 13:02:20, Martin Grigorov wrote:
> On Fri, Jan 10, 2020 at 2:55 PM Francesco Chicchiriccò
> wrote:
>
> > On 2020/01/1
On Fri, Jan 10, 2020 at 2:55 PM Francesco Chicchiriccò
wrote:
> On 2020/01/10 12:24:49, Martin Grigorov wrote:
> > Hi Francesco,
> >
> > This was a bug in Wicket, a security related one.
> > You will need to fix your code.
> >
> > The change should look something like this:
> >
> >
> > -
On 2020/01/10 12:24:49, Martin Grigorov wrote:
> Hi Francesco,
>
> This was a bug in Wicket, a security related one.
> You will need to fix your code.
>
> The change should look something like this:
>
>
> - tester.getRequest().setParameter("select",
> page.option1.getValue());
>
Hi Francesco,
This was a bug in Wicket, a security related one.
You will need to fix your code.
The change should look something like this:
- tester.getRequest().setParameter("select",
page.option1.getValue());
- tester.getRequest().setParameter("text", "text is requ
Hi there,
it seems we have some issues with Wicket Tester, after upgrading to 8.7.0 from
8.6.1.
In particular, due to the change [1] for WICKET-6708, we have found that
MockWebRequest is not behaving as expected; no troubles occur instead during
normal operations with HttpServletRequest.
The t