Discussion:
FormTester, FinishButton and Wicket 8.0
Sven Meier
2018-06-07 16:43:58 UTC
Permalink
Hi,

I'm not able to run the test in Intellij nor in Eclipse:

java.lang.NoSuchMethodError:
org.junit.platform.commons.util.ReflectionUtils.getDefaultClassLoader

I suspect your problem might be caused by WICKET-6541, but I don't see
why the changes should fail during tests.

Have fun
Sven
I'll take a look.
Have fun
Sven
Hi all,
I am migrating the Syncope master branch from Wicket 7 to 8.
It seems all is working fine when dealing via browser, but the
integration tests are mostly failing.
As Syncope heavily uses Wizards, the reason seems that FormTester
fails somehow to submit the Finish button (though no error is
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L64
but I can see that no submit was effectively performed by
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L62
hence no feedback message was generated.
Strange is that I am also sure that the Next button is effectively
submitted by
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L56
Is there anything relevant that was changed in WicketTester with
Wicket 8? The code above works fine with Wicket 7, and performing the
same actions via browser works fine too.
TIA.
Regards.
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-***@wicket.apache.org
For additional commands, e-mail: users-***@wicket.apache.org
Francesco Chicchiriccò
2018-06-11 10:43:32 UTC
Permalink
Post by Sven Meier
Hi,
org.junit.platform.commons.util.ReflectionUtils.getDefaultClassLoader
Thanks for reporting, it seems that the problem was due to an accidental inclusion of the old junit artifact in the test classpath.
Anyway, what you can currently find on the Syncope master branch is still based on Wicket 7 (and the tests run fine); the Wicket 8 branch is not published.
Post by Sven Meier
I suspect your problem might be caused by WICKET-6541, but I don't see
why the changes should fail during tests.
Thanks for pointing this out, I will look at it.

Regards.
Post by Sven Meier
I'll take a look.
Have fun
Sven
Hi all,
I am migrating the Syncope master branch from Wicket 7 to 8.
It seems all is working fine when dealing via browser, but the
integration tests are mostly failing.
As Syncope heavily uses Wizards, the reason seems that FormTester
fails somehow to submit the Finish button (though no error is
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L64
but I can see that no submit was effectively performed by
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L62
hence no feedback message was generated.
Strange is that I am also sure that the Next button is effectively
submitted by
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L56
Is there anything relevant that was changed in WicketTester with
Wicket 8? The code above works fine with Wicket 7, and performing the
same actions via browser works fine too.
TIA.
Regards.
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-***@wicket.apache.org
For additional commands, e-mail: users-***@wicket.apache.org
Francesco Chicchiriccò
2018-06-13 11:33:05 UTC
Permalink
I have spent some time investigating this issue, and I have finally found that the actual problem lies at

https://github.com/apache/syncope/blob/SYNCOPE-1323/client/console/src/main/java/org/apache/syncope/client/console/wizards/AjaxWizard.java#L198

e.g.

RequestCycle.get().find(AjaxRequestTarget.class)

returns an Optional holding null, when onFinish() is invoked by WicketTester (actual execution works fine, as said below).

Does this ring any bell?
Regards.
Post by Francesco Chicchiriccò
Post by Sven Meier
Hi,
org.junit.platform.commons.util.ReflectionUtils.getDefaultClassLoader
Thanks for reporting, it seems that the problem was due to an accidental inclusion of the old junit artifact in the test classpath.
Anyway, what you can currently find on the Syncope master branch is still based on Wicket 7 (and the tests run fine); the Wicket 8 branch is not published.
Post by Sven Meier
I suspect your problem might be caused by WICKET-6541, but I don't see
why the changes should fail during tests.
Thanks for pointing this out, I will look at it.
Regards.
Post by Sven Meier
I'll take a look.
Have fun
Sven
Hi all,
I am migrating the Syncope master branch from Wicket 7 to 8.
It seems all is working fine when dealing via browser, but the
integration tests are mostly failing.
As Syncope heavily uses Wizards, the reason seems that FormTester
fails somehow to submit the Finish button (though no error is
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L64
but I can see that no submit was effectively performed by
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L62
hence no feedback message was generated.
Strange is that I am also sure that the Next button is effectively
submitted by
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L56
Is there anything relevant that was changed in WicketTester with
Wicket 8? The code above works fine with Wicket 7, and performing the
same actions via browser works fine too.
TIA.
Regards.
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-***@wicket.apache.org
For additional commands, e-mail: users-***@wicket.apache.org
Martin Grigorov
2018-06-13 11:57:24 UTC
Permalink
I guess those two should really use Optional.ofNullable():
https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/request/cycle/RequestCycle.java#L886-L892
Post by Francesco Chicchiriccò
I have spent some time investigating this issue, and I have finally found
that the actual problem lies at
https://github.com/apache/syncope/blob/SYNCOPE-1323/client/console/src/main/java/org/apache/syncope/client/console/wizards/AjaxWizard.java#L198
e.g.
RequestCycle.get().find(AjaxRequestTarget.class)
returns an Optional holding null, when onFinish() is invoked by
WicketTester (actual execution works fine, as said below).
Does this ring any bell?
Regards.
Post by Francesco Chicchiriccò
Post by Sven Meier
Hi,
org.junit.platform.commons.util.ReflectionUtils.getDefaultClassLoader
Thanks for reporting, it seems that the problem was due to an accidental
inclusion of the old junit artifact in the test classpath.
Post by Francesco Chicchiriccò
Anyway, what you can currently find on the Syncope master branch is
still based on Wicket 7 (and the tests run fine); the Wicket 8 branch is
not published.
Post by Francesco Chicchiriccò
Post by Sven Meier
I suspect your problem might be caused by WICKET-6541, but I don't see
why the changes should fail during tests.
Thanks for pointing this out, I will look at it.
Regards.
Post by Sven Meier
I'll take a look.
Have fun
Sven
Hi all,
I am migrating the Syncope master branch from Wicket 7 to 8.
It seems all is working fine when dealing via browser, but the
integration tests are mostly failing.
As Syncope heavily uses Wizards, the reason seems that FormTester
fails somehow to submit the Finish button (though no error is
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L64
Post by Francesco Chicchiriccò
Post by Sven Meier
but I can see that no submit was effectively performed by
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L62
Post by Francesco Chicchiriccò
Post by Sven Meier
hence no feedback message was generated.
Strange is that I am also sure that the Next button is effectively
submitted by
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L56
Post by Francesco Chicchiriccò
Post by Sven Meier
Is there anything relevant that was changed in WicketTester with
Wicket 8? The code above works fine with Wicket 7, and performing
the
Post by Francesco Chicchiriccò
Post by Sven Meier
same actions via browser works fine too.
TIA.
Regards.
---------------------------------------------------------------------
Post by Francesco Chicchiriccò
Post by Sven Meier
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
Sven Meier
2018-06-13 16:58:50 UTC
Permalink
@Martin The result is garantueed to be non-null in these lines, how should ofNullable() make any difference?

@Francesco FormTester submits via Ajax request only in case of an AjaxButton or AjaxSubmitLink, which ist not the case with AjaxButtonBar. As fallback the whole form is submitted instead, but without triggering the wizard finish button. An optional with null value is to be expected then.

Please open a Jira issue, we should improve that (and investigate why this didn't break before Wicket 8).

Thanks
Sven
Post by Martin Grigorov
https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/request/cycle/RequestCycle.java#L886-L892
On Wed, Jun 13, 2018 at 2:33 PM Francesco Chicchiriccò
Post by Francesco Chicchiriccò
I have spent some time investigating this issue, and I have finally
found
Post by Francesco Chicchiriccò
that the actual problem lies at
https://github.com/apache/syncope/blob/SYNCOPE-1323/client/console/src/main/java/org/apache/syncope/client/console/wizards/AjaxWizard.java#L198
Post by Francesco Chicchiriccò
e.g.
RequestCycle.get().find(AjaxRequestTarget.class)
returns an Optional holding null, when onFinish() is invoked by
WicketTester (actual execution works fine, as said below).
Does this ring any bell?
Regards.
Post by Francesco Chicchiriccò
Post by Sven Meier
Hi,
org.junit.platform.commons.util.ReflectionUtils.getDefaultClassLoader
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Thanks for reporting, it seems that the problem was due to an
accidental
Post by Francesco Chicchiriccò
inclusion of the old junit artifact in the test classpath.
Post by Francesco Chicchiriccò
Anyway, what you can currently find on the Syncope master branch is
still based on Wicket 7 (and the tests run fine); the Wicket 8 branch
is
Post by Francesco Chicchiriccò
not published.
Post by Francesco Chicchiriccò
Post by Sven Meier
I suspect your problem might be caused by WICKET-6541, but I
don't see
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
why the changes should fail during tests.
Thanks for pointing this out, I will look at it.
Regards.
Post by Sven Meier
I'll take a look.
Have fun
Sven
Hi all,
I am migrating the Syncope master branch from Wicket 7 to 8.
It seems all is working fine when dealing via browser, but the
integration tests are mostly failing.
As Syncope heavily uses Wizards, the reason seems that
FormTester
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
fails somehow to submit the Finish button (though no error is
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L64
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
but I can see that no submit was effectively performed by
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L62
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
hence no feedback message was generated.
Strange is that I am also sure that the Next button is
effectively
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
submitted by
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L56
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
Is there anything relevant that was changed in WicketTester
with
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
Wicket 8? The code above works fine with Wicket 7, and
performing
Post by Francesco Chicchiriccò
the
Post by Francesco Chicchiriccò
Post by Sven Meier
same actions via browser works fine too.
TIA.
Regards.
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
Post by Francesco Chicchiriccò
---------------------------------------------------------------------
Sven Meier
2018-06-13 19:09:35 UTC
Permalink
Hi,

minor correction:

If no an AjaxButton or AjaxSubmitLink, FormTester submits the button via
a non-Ajax request.
Thus no AjaxRequestTarget can be  found.

Have fun
Sven
Post by Sven Meier
@Martin The result is garantueed to be non-null in these lines, how
should ofNullable() make any difference?
@Francesco FormTester submits via Ajax request only in case of an
AjaxButton or AjaxSubmitLink, which ist not the case with
AjaxButtonBar. As fallback the whole form is submitted instead, but
without triggering the wizard finish button. An optional with null
value is to be expected then.
Please open a Jira issue, we should improve that (and investigate why
this didn't break before Wicket 8).
Thanks
Sven
Am 13. Juni 2018 13:57:24 MESZ schrieb Martin Grigorov
https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/request/cycle/RequestCycle.java#L886-L892
I have spent some time investigating this issue, and I have
finally found that the actual problem lies at
https://github.com/apache/syncope/blob/SYNCOPE-1323/client/console/src/main/java/org/apache/syncope/client/console/wizards/AjaxWizard.java#L198
e.g. RequestCycle.get().find(AjaxRequestTarget.class) returns
an Optional holding null, when onFinish() is invoked by
WicketTester (actual execution works fine, as said below).
Does this ring any bell? Regards. On 2018/06/11 10:43:32,
Hi, I'm not able to run the test in Intellij nor in
org.junit.platform.commons.util.ReflectionUtils.getDefaultClassLoader
Thanks for reporting, it seems that the problem was due to
an accidental
inclusion of the old junit artifact in the test classpath.
Anyway, what you can currently find on the Syncope master branch is
still based on Wicket 7 (and the tests run fine); the Wicket 8
branch is not published.
I suspect your problem might be caused by WICKET-6541,
but I don't see why the changes should fail during tests.
Thanks for pointing this out, I will look at it. Regards.
I'll take a look. Have fun Sven Am 06.06.2018 um
Hi all, I am migrating the Syncope master
branch from Wicket 7 to 8. It seems all is
working fine when dealing via browser, but the
integration tests are mostly failing. As
Syncope heavily uses Wizards, the reason seems
that FormTester fails somehow to submit the
Finish button (though no error is reported);
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L64
but I can see that no submit was effectively
performed by
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L62
hence no feedback message was generated.
Strange is that I am also sure that the Next
button is effectively submitted by
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L56
Is there anything relevant that was changed in
WicketTester with Wicket 8? The code above
works fine with Wicket 7, and performing
the
same actions via browser works fine too. TIA.
Regards.
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
Martin Grigorov
2018-06-14 05:40:39 UTC
Permalink
Post by Sven Meier
@Martin The result is garantueed to be non-null in these lines, how should
ofNullable() make any difference?
Right! Just checked that Class.isInstance(null) would return false.

The problem is in AjaxFallbackButton methods.
https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/ajax/markup/html/form/AjaxFallbackButton.java#L76
Those should use ofNullable().
Post by Sven Meier
@Francesco FormTester submits via Ajax request only in case of an
AjaxButton or AjaxSubmitLink, which ist not the case with AjaxButtonBar. As
fallback the whole form is submitted instead, but without triggering the
wizard finish button. An optional with null value is to be expected then.
Please open a Jira issue, we should improve that (and investigate why this
didn't break before Wicket 8).
Thanks
Sven
Am 13. Juni 2018 13:57:24 MESZ schrieb Martin Grigorov <
https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/request/cycle/RequestCycle.java#L886-L892
Post by Martin Grigorov
On Wed, Jun 13, 2018 at 2:33 PM Francesco Chicchiriccò
Post by Francesco Chicchiriccò
I have spent some time investigating this issue, and I have finally
found
Post by Francesco Chicchiriccò
that the actual problem lies at
https://github.com/apache/syncope/blob/SYNCOPE-1323/client/console/src/main/java/org/apache/syncope/client/console/wizards/AjaxWizard.java#L198
Post by Martin Grigorov
Post by Francesco Chicchiriccò
e.g.
RequestCycle.get().find(AjaxRequestTarget.class)
returns an Optional holding null, when onFinish() is invoked by
WicketTester (actual execution works fine, as said below).
Does this ring any bell?
Regards.
Post by Francesco Chicchiriccò
Post by Sven Meier
Hi,
org.junit.platform.commons.util.ReflectionUtils.getDefaultClassLoader
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Thanks for reporting, it seems that the problem was due to an
accidental
Post by Francesco Chicchiriccò
inclusion of the old junit artifact in the test classpath.
Post by Francesco Chicchiriccò
Anyway, what you can currently find on the Syncope master branch is
still based on Wicket 7 (and the tests run fine); the Wicket 8 branch
is
Post by Francesco Chicchiriccò
not published.
Post by Francesco Chicchiriccò
Post by Sven Meier
I suspect your problem might be caused by WICKET-6541, but I
don't see
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
why the changes should fail during tests.
Thanks for pointing this out, I will look at it.
Regards.
Post by Sven Meier
I'll take a look.
Have fun
Sven
Hi all,
I am migrating the Syncope master branch from Wicket 7 to 8.
It seems all is working fine when dealing via browser, but the
integration tests are mostly failing.
As Syncope heavily uses Wizards, the reason seems that
FormTester
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
fails somehow to submit the Finish button (though no error is
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L64
Post by Martin Grigorov
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
but I can see that no submit was effectively performed by
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L62
Post by Martin Grigorov
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
hence no feedback message was generated.
Strange is that I am also sure that the Next button is
effectively
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
submitted by
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L56
Post by Martin Grigorov
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
Is there anything relevant that was changed in WicketTester
with
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
Wicket 8? The code above works fine with Wicket 7, and
performing
Post by Francesco Chicchiriccò
the
Post by Francesco Chicchiriccò
Post by Sven Meier
same actions via browser works fine too.
TIA.
Regards.
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
Post by Francesco Chicchiriccò
---------------------------------------------------------------------
Martin Grigorov
2018-06-14 05:47:02 UTC
Permalink
Post by Martin Grigorov
Post by Sven Meier
@Martin The result is garantueed to be non-null in these lines, how
should ofNullable() make any difference?
Right! Just checked that Class.isInstance(null) would return false.
The problem is in AjaxFallbackButton methods.
https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/ajax/markup/html/form/AjaxFallbackButton.java#L76
Those should use ofNullable().
No, those should be called only in Ajax request so it should be fine.
The non-Ajax ones are below in the class.
Post by Martin Grigorov
Post by Sven Meier
@Francesco FormTester submits via Ajax request only in case of an
AjaxButton or AjaxSubmitLink, which ist not the case with AjaxButtonBar. As
fallback the whole form is submitted instead, but without triggering the
wizard finish button. An optional with null value is to be expected then.
Please open a Jira issue, we should improve that (and investigate why
this didn't break before Wicket 8).
Thanks
Sven
Am 13. Juni 2018 13:57:24 MESZ schrieb Martin Grigorov <
https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/request/cycle/RequestCycle.java#L886-L892
Post by Martin Grigorov
On Wed, Jun 13, 2018 at 2:33 PM Francesco Chicchiriccò
Post by Francesco Chicchiriccò
I have spent some time investigating this issue, and I have finally
found
Post by Francesco Chicchiriccò
that the actual problem lies at
https://github.com/apache/syncope/blob/SYNCOPE-1323/client/console/src/main/java/org/apache/syncope/client/console/wizards/AjaxWizard.java#L198
Post by Martin Grigorov
Post by Francesco Chicchiriccò
e.g.
RequestCycle.get().find(AjaxRequestTarget.class)
returns an Optional holding null, when onFinish() is invoked by
WicketTester (actual execution works fine, as said below).
Does this ring any bell?
Regards.
Post by Francesco Chicchiriccò
Post by Sven Meier
Hi,
org.junit.platform.commons.util.ReflectionUtils.getDefaultClassLoader
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Thanks for reporting, it seems that the problem was due to an
accidental
Post by Francesco Chicchiriccò
inclusion of the old junit artifact in the test classpath.
Post by Francesco Chicchiriccò
Anyway, what you can currently find on the Syncope master branch is
still based on Wicket 7 (and the tests run fine); the Wicket 8 branch
is
Post by Francesco Chicchiriccò
not published.
Post by Francesco Chicchiriccò
Post by Sven Meier
I suspect your problem might be caused by WICKET-6541, but I
don't see
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
why the changes should fail during tests.
Thanks for pointing this out, I will look at it.
Regards.
Post by Sven Meier
I'll take a look.
Have fun
Sven
Hi all,
I am migrating the Syncope master branch from Wicket 7 to 8.
It seems all is working fine when dealing via browser, but the
integration tests are mostly failing.
As Syncope heavily uses Wizards, the reason seems that
FormTester
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
fails somehow to submit the Finish button (though no error is
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L64
Post by Martin Grigorov
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
but I can see that no submit was effectively performed by
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L62
Post by Martin Grigorov
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
hence no feedback message was generated.
Strange is that I am also sure that the Next button is
effectively
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
submitted by
https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L56
Post by Martin Grigorov
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
Is there anything relevant that was changed in WicketTester
with
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Sven Meier
Wicket 8? The code above works fine with Wicket 7, and
performing
Post by Francesco Chicchiriccò
the
Post by Francesco Chicchiriccò
Post by Sven Meier
same actions via browser works fine too.
TIA.
Regards.
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
Post by Francesco Chicchiriccò
---------------------------------------------------------------------
Loading...