Re: Debugging options
Hi,
the value of the will not be sent when it is already disabled
before Wicket serializes its value.
You should use #getBeforeSendHandler() instead.
Sven
Am 07.06.2018 um 19:55 schrieb sorinev:
Ok, so I found out what it appears to be. My full code for the DropDownChoice
I'm setting up is this:
selectedAccountDropdown = new DropDownChoice("selectedAccount", new
PropertyModel(this, "selectedAccount"), accountList, new
ChoiceRenderer("name", "id"));
selectedAccountDropdown.add(new AjaxFormComponentUpdatingBehavior("change")
{
@Override
protected void onError(AjaxRequestTarget target, RuntimeException e) {
if (e != null) {
LOG.error(e, e);
error(e);
} else {
LOG.error("Exception null, see feedback on page.");
}
error("Page may not have been updated");
target.add(feedbackPanel);
}
@Override
protected void onUpdate(AjaxRequestTarget target) {
//[code here]
}
@Override
protected void updateAjaxAttributes(AjaxRequestAttributes attributes) {
super.updateAjaxAttributes(attributes);
attributes.getAjaxCallListeners().add(new AjaxCallListener()
.onBefore("$('#selectedAccount').prop('disabled',true);")
.onComplete("$('#selectedAccount').prop('disabled',false);"));
}
});
selectedAccountDropdown.setMarkupId("selectedAccount");
selectedAccountDropdown.setNullValid(false);
selectedAccountDropdown.setRequired(true);
baseForm.add(selectedAccountDropdown);
When I comment out the updateAjaxAttributes method, everything works as
expected. If I add it back in, my model object becomes null again when
changing. So, I'm obviously doing that the wrong way. What is the proper way
to achieve what I'm doing on the updateAjaxAttributes override? What I need
to do is disable the dropdown *while* the dropdown is being updated because
there's code that runs that needs to be allowed to finish. I obviously can't
disable/enable the component inside the onUpdate method because those won't
take effect until after onUpdate finishes. Which, clearly, is useless. Hence
the Ajax bits.
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Debugging options
Ok, so I found out what it appears to be. My full code for the DropDownChoice
I'm setting up is this:
selectedAccountDropdown = new DropDownChoice("selectedAccount", new
PropertyModel(this, "selectedAccount"), accountList, new
ChoiceRenderer("name", "id"));
selectedAccountDropdown.add(new AjaxFormComponentUpdatingBehavior("change")
{
@Override
protected void onError(AjaxRequestTarget target, RuntimeException e) {
if (e != null) {
LOG.error(e, e);
error(e);
} else {
LOG.error("Exception null, see feedback on page.");
}
error("Page may not have been updated");
target.add(feedbackPanel);
}
@Override
protected void onUpdate(AjaxRequestTarget target) {
//[code here]
}
@Override
protected void updateAjaxAttributes(AjaxRequestAttributes attributes) {
super.updateAjaxAttributes(attributes);
attributes.getAjaxCallListeners().add(new AjaxCallListener()
.onBefore("$('#selectedAccount').prop('disabled',true);")
.onComplete("$('#selectedAccount').prop('disabled',false);"));
}
});
selectedAccountDropdown.setMarkupId("selectedAccount");
selectedAccountDropdown.setNullValid(false);
selectedAccountDropdown.setRequired(true);
baseForm.add(selectedAccountDropdown);
When I comment out the updateAjaxAttributes method, everything works as
expected. If I add it back in, my model object becomes null again when
changing. So, I'm obviously doing that the wrong way. What is the proper way
to achieve what I'm doing on the updateAjaxAttributes override? What I need
to do is disable the dropdown *while* the dropdown is being updated because
there's code that runs that needs to be allowed to finish. I obviously can't
disable/enable the component inside the onUpdate method because those won't
take effect until after onUpdate finishes. Which, clearly, is useless. Hence
the Ajax bits.
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: FormTester, FinishButton and Wicket 8.0
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 Am 06.06.2018 um 19:00 schrieb Sven Meier: I'll take a look. Have fun Sven Am 06.06.2018 um 17:16 schrieb Francesco Chicchiriccò: 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); the failing statement is (for example): 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-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Debugging options
It seems like nothing in that class is being called when I change the
selection in the DropDownChoice.
I'm setting it up like this:
new DropDownChoice("account", new PropertyModel(this, "selectedAccount"),
accountList, new ChoiceRenderer("name", "id"));
But I've tried several other ways too, such as a CompoundPropertyModel
straight, a CompoundPropertyModel with bind(), putting the selectedAccount
object not in "this" ("this" is the page itself, derived from Wicket
WebPage), but in an normal object, etc. and it always results in
selectedAccount being null. But like I said, this same thing works in a
quickstart, so I'm baffled.
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Debugging options
Hi, Wicket doesn't need any special equals() implementations. Debug AbstractSingleSelectChoice#getModelValue() and check what it does. Have fun Sven Am 07.06.2018 um 17:12 schrieb sorinev: I don't have an equals method for the class, and most of the classes I've come across in our code that are being used in Wicket components don't. Is a class supposed to? How does it work otherwise? Bit-by-bit comparison by the JVM? Anyhow, yeah debugging is what I've been doing but I've been getting nowhere. I was wondering what I can zero in on in the Wicket sources that might help me debug why setting up the dropdown is perfectly fine, as is setting the initial value when the page is constructed, but why changing is always null. -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Debugging options
I don't have an equals method for the class, and most of the classes I've come across in our code that are being used in Wicket components don't. Is a class supposed to? How does it work otherwise? Bit-by-bit comparison by the JVM? Anyhow, yeah debugging is what I've been doing but I've been getting nowhere. I was wondering what I can zero in on in the Wicket sources that might help me debug why setting up the dropdown is perfectly fine, as is setting the initial value when the page is constructed, but why changing is always null. -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Release WiQuery for Wicket 8
8.0 is on its way to Maven Central! On Thu, Jun 7, 2018 at 5:46 PM, Emond Papegaaij wrote: > I did not build the javadoc, but I actually don't know why. But as I don't > care about these javadoc errors, I've disabled lint. You should be able to > build now. > > Emond > > On donderdag 7 juni 2018 16:32:16 CEST Martin Grigorov wrote: > > There are many javadoc related errors in this project. mvn install fails > > with: > > > > [WARNING] The requested profile "frontend" could not be activated because > > it does not exist. > > [WARNING] The requested profile "buildbot" could not be activated because > > it does not exist. > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-javadoc-plugin:2.7:jar (attach-javadocs) > on > > project wiquery-core: MavenReportException: Error while creating archive: > > [ERROR] Exit code: 1 - > > /home/martin/git/wiquery/wiquery-core/src/main/java/ > org/wicketstuff/wiquery/ > > core/util/WiQueryUtil.java:46: warning: no @return > > [ERROR] public static ResourceReference getJQueryResourceReference() > > [ERROR]^ > > [ERROR] > > /home/martin/git/wiquery/wiquery-core/src/main/java/ > org/wicketstuff/wiquery/ > > core/events/Event.java:78: warning: no @return > > [ERROR] public abstract JsScope callback(); > > [ERROR]^ > > [ERROR] > > /home/martin/git/wiquery/wiquery-core/src/main/java/ > org/wicketstuff/wiquery/ > > core/events/Event.java:53: warning: no @param for eventLabels > > [ERROR] public Event(EventLabel... eventLabels) > > [ERROR] ^ > > [ERROR] > > /home/martin/git/wiquery/wiquery-core/src/main/java/ > org/wicketstuff/wiquery/ > > core/javascript/DefaultChainableStatement.java:49: warning: no @param > for > > label > > [ERROR] public DefaultChainableStatement(String label, CharSequence... > args) > > > > > > > > How did you build it with Java 8 ? > > > > > > On Thu, Jun 7, 2018 at 3:55 PM, Martin Grigorov > > > > wrote: > > > OK. I will make a release! > > > > > > On Thu, Jun 7, 2018 at 3:25 PM, Thomas Heigl > wrote: > > >> Hi Emond, > > >> > > >> I did some exploratory testing against the current build. I checked > > >> Dialog, > > >> Autocomplete, Accordion, Slider, Sortable, and Tooltip and all seem > to be > > >> working at first glance. > > >> > > >> All my tests pass as well. > > >> > > >> Best, > > >> > > >> Thomas > > >> > > >> On Wed, Jun 6, 2018 at 1:07 PM, Emond Papegaaij < > > >> emond.papega...@topicus.nl> > > >> > > >> wrote: > > >> > I've fixed the problem. The setup currently used is discouraged and > > >> > > >> broken > > >> > > >> > in > > >> > m2e, but I don't feel like restructuring the whole thing to get rid > of > > >> > this > > >> > test-jar. > > >> > > > >> > Emond > > >> > > > >> > On woensdag 6 juni 2018 11:57:43 CEST Thomas Heigl wrote: > > >> > > The culprit is: > > >> > > > > >> > > https://github.com/wicketstuff/wiquery/commit/ > > >> > > > >> > 0235691174ceeede22b588d2f67868 > > >> > > > >> > > b940d9be3a > > >> > > On Wed, Jun 6, 2018 at 11:51 AM, Thomas Heigl < > tho...@umschalt.com> > > >> > > > >> > wrote: > > >> > > > `mvn clean install` fails for me because no test-jar is built > for > > >> > > >> the > > >> > > >> > core > > >> > > > >> > > > module: > > >> > > > > > >> > > > [INFO] WiQuery Parent 8.0-SNAPSHOT > SUCCESS > > >> > > >> [ > > >> > > >> > > >> 0.353 s] > > >> > > >> > > >> > > >> [INFO] WiQuery Core Project ... > > >> > > >> SUCCESS [ > > >> > > >> > > >> 2.673 s] > > >> > > >> > > >> > > >> [INFO] WiQuery jQuery UI Project .. > > >> > > >> FAILURE [ > > >> > > >> > > >> 0.023 s] > > >> > > >> > > >> > > >> [INFO] WiQuery Demo Project 8.0-SNAPSHOT .. > > >> > > >> SKIPPED > > >> > > >> [INFO] -- > > >> > > >> -- > > >> > > >> > > >> > > >> > > >> [INFO] BUILD FAILURE > > >> > > >> [INFO] -- > > >> > > >> -- > > >> > > >> > > >> > > >> > > >> [INFO] Total time: 3.720 s > > >> > > >> [INFO] Finished at: 2018-06-06T11:48:16+02:00 > > >> > > >> [INFO] -- > > >> > > >> -- > > >> > > >> > > >> > > >> > > >> [ERROR] Failed to execute goal on project wiquery-jquery-ui: > Could > > >> > > >> not > > >> > > >> > > >> resolve dependencies for project org.wicketstuff.wiquery: > > >> > > >> wiquery-jquery-ui:jar:8.0-SNAPSHOT: Failure to find > > >> > > >> org.wicketstuff.wiquery:wiquery-core:jar:tests:8.0-SNAPSHOT in > > >> > > >> https://oss.sonatype.org/content/repositories/snapshots was > > >> > > >> cached in > > >> > > >> > > >> the local repository, resolution will not be reattempted until > the > > >> > > > >> > update > > >> > > > >> > > >> interval of sonatype-nexus-snapshots has elapsed or updates are > > >> > > > >> > forced -> > > >> >
Re: Release WiQuery for Wicket 8
I did not build the javadoc, but I actually don't know why. But as I don't care about these javadoc errors, I've disabled lint. You should be able to build now. Emond On donderdag 7 juni 2018 16:32:16 CEST Martin Grigorov wrote: > There are many javadoc related errors in this project. mvn install fails > with: > > [WARNING] The requested profile "frontend" could not be activated because > it does not exist. > [WARNING] The requested profile "buildbot" could not be activated because > it does not exist. > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-javadoc-plugin:2.7:jar (attach-javadocs) on > project wiquery-core: MavenReportException: Error while creating archive: > [ERROR] Exit code: 1 - > /home/martin/git/wiquery/wiquery-core/src/main/java/org/wicketstuff/wiquery/ > core/util/WiQueryUtil.java:46: warning: no @return > [ERROR] public static ResourceReference getJQueryResourceReference() > [ERROR]^ > [ERROR] > /home/martin/git/wiquery/wiquery-core/src/main/java/org/wicketstuff/wiquery/ > core/events/Event.java:78: warning: no @return > [ERROR] public abstract JsScope callback(); > [ERROR]^ > [ERROR] > /home/martin/git/wiquery/wiquery-core/src/main/java/org/wicketstuff/wiquery/ > core/events/Event.java:53: warning: no @param for eventLabels > [ERROR] public Event(EventLabel... eventLabels) > [ERROR] ^ > [ERROR] > /home/martin/git/wiquery/wiquery-core/src/main/java/org/wicketstuff/wiquery/ > core/javascript/DefaultChainableStatement.java:49: warning: no @param for > label > [ERROR] public DefaultChainableStatement(String label, CharSequence... args) > > > > How did you build it with Java 8 ? > > > On Thu, Jun 7, 2018 at 3:55 PM, Martin Grigorov > > wrote: > > OK. I will make a release! > > > > On Thu, Jun 7, 2018 at 3:25 PM, Thomas Heigl wrote: > >> Hi Emond, > >> > >> I did some exploratory testing against the current build. I checked > >> Dialog, > >> Autocomplete, Accordion, Slider, Sortable, and Tooltip and all seem to be > >> working at first glance. > >> > >> All my tests pass as well. > >> > >> Best, > >> > >> Thomas > >> > >> On Wed, Jun 6, 2018 at 1:07 PM, Emond Papegaaij < > >> emond.papega...@topicus.nl> > >> > >> wrote: > >> > I've fixed the problem. The setup currently used is discouraged and > >> > >> broken > >> > >> > in > >> > m2e, but I don't feel like restructuring the whole thing to get rid of > >> > this > >> > test-jar. > >> > > >> > Emond > >> > > >> > On woensdag 6 juni 2018 11:57:43 CEST Thomas Heigl wrote: > >> > > The culprit is: > >> > > > >> > > https://github.com/wicketstuff/wiquery/commit/ > >> > > >> > 0235691174ceeede22b588d2f67868 > >> > > >> > > b940d9be3a > >> > > On Wed, Jun 6, 2018 at 11:51 AM, Thomas Heigl > >> > > >> > wrote: > >> > > > `mvn clean install` fails for me because no test-jar is built for > >> > >> the > >> > >> > core > >> > > >> > > > module: > >> > > > > >> > > > [INFO] WiQuery Parent 8.0-SNAPSHOT SUCCESS > >> > >> [ > >> > >> > > >> 0.353 s] > >> > > >> > >> > > >> [INFO] WiQuery Core Project ... > >> > >> SUCCESS [ > >> > >> > > >> 2.673 s] > >> > > >> > >> > > >> [INFO] WiQuery jQuery UI Project .. > >> > >> FAILURE [ > >> > >> > > >> 0.023 s] > >> > > >> > >> > > >> [INFO] WiQuery Demo Project 8.0-SNAPSHOT .. > >> > > >> SKIPPED > >> > > >> [INFO] -- > >> > >> -- > >> > >> > > >> > >> > > >> [INFO] BUILD FAILURE > >> > > >> [INFO] -- > >> > >> -- > >> > >> > > >> > >> > > >> [INFO] Total time: 3.720 s > >> > > >> [INFO] Finished at: 2018-06-06T11:48:16+02:00 > >> > > >> [INFO] -- > >> > >> -- > >> > >> > > >> > >> > > >> [ERROR] Failed to execute goal on project wiquery-jquery-ui: Could > >> > >> not > >> > >> > > >> resolve dependencies for project org.wicketstuff.wiquery: > >> > > >> wiquery-jquery-ui:jar:8.0-SNAPSHOT: Failure to find > >> > > >> org.wicketstuff.wiquery:wiquery-core:jar:tests:8.0-SNAPSHOT in > >> > > >> https://oss.sonatype.org/content/repositories/snapshots was > >> > >> cached in > >> > >> > > >> the local repository, resolution will not be reattempted until the > >> > > >> > update > >> > > >> > > >> interval of sonatype-nexus-snapshots has elapsed or updates are > >> > > >> > forced -> > >> > > >> > > >> [Help 1] > >> > > >> [ERROR] > >> > > > > >> > > > Did you change something about test-jar configuration? I do not see > >> > > > `test-jar` generation enabled in the POM file. > >> > > > > >> > > > On Wed, Jun 6, 2018 at 11:43 AM, Emond Papegaaij < > >> > > > > >> > > > emond.papega...@topicus.nl> wrote: > >> > > >> Hi Thomas, > >> > > >> > >> > > >> The easiest way is to just run
Re: ChainingModel warnings in Wicket 8
Also the warning is logged for `null` objects, which probably shouldn't
happen.
public ChainingModel(final Object modelObject)
> {
> if (modelObject instanceof Session)
> {
> LOG.warn("It is not a good idea to reference the .");
> } else if (modelObject instanceof Serializable == false)
> {
> LOG.warn("It is not a good idea to reference a non-serializable
> instance ");
> }
> target = modelObject;
> }
It should read something like:
if (modelObject != null && modelObject instanceof Serializable == false)
Best,
Thomas
On Thu, Jun 7, 2018 at 4:25 PM, Thomas Heigl wrote:
> Hi all,
>
> After porting our app to Wicket 8, I'm getting these warnings on my test
> environment:
>
> WAR o.a.w.model.ChainingModel It is not a good idea to reference a
>> non-serializable instance in models directly as it may lead to
>> serialization problems
>
>
> The warning is OK, but it gives me absolutely no hint where to look for
> the issue. Could someone please add the (simple) class name of the model
> object to the warning message?
>
> Currently, the only way for me to find these issues is with a breakpoint
> in `ChainingModel` and clicking through my application until I hit the
> warning.
>
> Best,
>
> Thomas
>
Re: Release WiQuery for Wicket 8
There are many javadoc related errors in this project. mvn install fails with: [WARNING] The requested profile "frontend" could not be activated because it does not exist. [WARNING] The requested profile "buildbot" could not be activated because it does not exist. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.7:jar (attach-javadocs) on project wiquery-core: MavenReportException: Error while creating archive: [ERROR] Exit code: 1 - /home/martin/git/wiquery/wiquery-core/src/main/java/org/wicketstuff/wiquery/core/util/WiQueryUtil.java:46: warning: no @return [ERROR] public static ResourceReference getJQueryResourceReference() [ERROR]^ [ERROR] /home/martin/git/wiquery/wiquery-core/src/main/java/org/wicketstuff/wiquery/core/events/Event.java:78: warning: no @return [ERROR] public abstract JsScope callback(); [ERROR]^ [ERROR] /home/martin/git/wiquery/wiquery-core/src/main/java/org/wicketstuff/wiquery/core/events/Event.java:53: warning: no @param for eventLabels [ERROR] public Event(EventLabel... eventLabels) [ERROR] ^ [ERROR] /home/martin/git/wiquery/wiquery-core/src/main/java/org/wicketstuff/wiquery/core/javascript/DefaultChainableStatement.java:49: warning: no @param for label [ERROR] public DefaultChainableStatement(String label, CharSequence... args) How did you build it with Java 8 ? On Thu, Jun 7, 2018 at 3:55 PM, Martin Grigorov wrote: > OK. I will make a release! > > On Thu, Jun 7, 2018 at 3:25 PM, Thomas Heigl wrote: > >> Hi Emond, >> >> I did some exploratory testing against the current build. I checked >> Dialog, >> Autocomplete, Accordion, Slider, Sortable, and Tooltip and all seem to be >> working at first glance. >> >> All my tests pass as well. >> >> Best, >> >> Thomas >> >> On Wed, Jun 6, 2018 at 1:07 PM, Emond Papegaaij < >> emond.papega...@topicus.nl> >> wrote: >> >> > I've fixed the problem. The setup currently used is discouraged and >> broken >> > in >> > m2e, but I don't feel like restructuring the whole thing to get rid of >> > this >> > test-jar. >> > >> > Emond >> > >> > On woensdag 6 juni 2018 11:57:43 CEST Thomas Heigl wrote: >> > > The culprit is: >> > > >> > > https://github.com/wicketstuff/wiquery/commit/ >> > 0235691174ceeede22b588d2f67868 >> > > b940d9be3a >> > > On Wed, Jun 6, 2018 at 11:51 AM, Thomas Heigl >> > wrote: >> > > > `mvn clean install` fails for me because no test-jar is built for >> the >> > core >> > > > module: >> > > > >> > > > [INFO] WiQuery Parent 8.0-SNAPSHOT SUCCESS >> [ >> > > > >> > > >> 0.353 s] >> > > >> >> > > >> [INFO] WiQuery Core Project ... >> SUCCESS [ >> > > >> >> > > >> 2.673 s] >> > > >> >> > > >> [INFO] WiQuery jQuery UI Project .. >> FAILURE [ >> > > >> >> > > >> 0.023 s] >> > > >> >> > > >> [INFO] WiQuery Demo Project 8.0-SNAPSHOT .. SKIPPED >> > > >> [INFO] -- >> -- >> > > >> >> > > >> [INFO] BUILD FAILURE >> > > >> [INFO] -- >> -- >> > > >> >> > > >> [INFO] Total time: 3.720 s >> > > >> [INFO] Finished at: 2018-06-06T11:48:16+02:00 >> > > >> [INFO] -- >> -- >> > > >> >> > > >> [ERROR] Failed to execute goal on project wiquery-jquery-ui: Could >> not >> > > >> resolve dependencies for project org.wicketstuff.wiquery: >> > > >> wiquery-jquery-ui:jar:8.0-SNAPSHOT: Failure to find >> > > >> org.wicketstuff.wiquery:wiquery-core:jar:tests:8.0-SNAPSHOT in >> > > >> https://oss.sonatype.org/content/repositories/snapshots was >> cached in >> > > >> the local repository, resolution will not be reattempted until the >> > update >> > > >> interval of sonatype-nexus-snapshots has elapsed or updates are >> > forced -> >> > > >> [Help 1] >> > > >> [ERROR] >> > > > >> > > > Did you change something about test-jar configuration? I do not see >> > > > `test-jar` generation enabled in the POM file. >> > > > >> > > > On Wed, Jun 6, 2018 at 11:43 AM, Emond Papegaaij < >> > > > >> > > > emond.papega...@topicus.nl> wrote: >> > > >> Hi Thomas, >> > > >> >> > > >> The easiest way is to just run 'mvn install' and depend on >> > 8.0-SNAPSHOT. >> > > >> I did >> > > >> not do a release, as I cannot push to central. If you want to run >> your >> > > >> tests >> > > >> on some CI server, you probably have to push the artifacts to a >> local >> > > >> repo >> > > >> also. >> > > >> >> > > >> Best regards, >> > > >> Emond >> > > >> >> > > >> On woensdag 6 juni 2018 11:36:54 CEST Thomas Heigl wrote: >> > > >> > Hi Emond, >> > > >> > >> > > >> > How can I test this? Did you do a milestone release or do I have >> to >> > > >> >> > > >> build >> > > >> >> > > >> > from source and push to my local artifact repo? >> > > >> > >> > > >> > Best, >> > > >> > >> > > >> > Thomas
ChainingModel warnings in Wicket 8
Hi all, After porting our app to Wicket 8, I'm getting these warnings on my test environment: WAR o.a.w.model.ChainingModel It is not a good idea to reference a > non-serializable instance in models directly as it may lead to > serialization problems The warning is OK, but it gives me absolutely no hint where to look for the issue. Could someone please add the (simple) class name of the model object to the warning message? Currently, the only way for me to find these issues is with a breakpoint in `ChainingModel` and clicking through my application until I hit the warning. Best, Thomas
Re: Release WiQuery for Wicket 8
OK. I will make a release! On Thu, Jun 7, 2018 at 3:25 PM, Thomas Heigl wrote: > Hi Emond, > > I did some exploratory testing against the current build. I checked Dialog, > Autocomplete, Accordion, Slider, Sortable, and Tooltip and all seem to be > working at first glance. > > All my tests pass as well. > > Best, > > Thomas > > On Wed, Jun 6, 2018 at 1:07 PM, Emond Papegaaij < > emond.papega...@topicus.nl> > wrote: > > > I've fixed the problem. The setup currently used is discouraged and > broken > > in > > m2e, but I don't feel like restructuring the whole thing to get rid of > > this > > test-jar. > > > > Emond > > > > On woensdag 6 juni 2018 11:57:43 CEST Thomas Heigl wrote: > > > The culprit is: > > > > > > https://github.com/wicketstuff/wiquery/commit/ > > 0235691174ceeede22b588d2f67868 > > > b940d9be3a > > > On Wed, Jun 6, 2018 at 11:51 AM, Thomas Heigl > > wrote: > > > > `mvn clean install` fails for me because no test-jar is built for the > > core > > > > module: > > > > > > > > [INFO] WiQuery Parent 8.0-SNAPSHOT SUCCESS [ > > > > > > > >> 0.353 s] > > > >> > > > >> [INFO] WiQuery Core Project ... > SUCCESS [ > > > >> > > > >> 2.673 s] > > > >> > > > >> [INFO] WiQuery jQuery UI Project .. FAILURE > [ > > > >> > > > >> 0.023 s] > > > >> > > > >> [INFO] WiQuery Demo Project 8.0-SNAPSHOT .. SKIPPED > > > >> [INFO] > > > >> > > > >> [INFO] BUILD FAILURE > > > >> [INFO] > > > >> > > > >> [INFO] Total time: 3.720 s > > > >> [INFO] Finished at: 2018-06-06T11:48:16+02:00 > > > >> [INFO] > > > >> > > > >> [ERROR] Failed to execute goal on project wiquery-jquery-ui: Could > not > > > >> resolve dependencies for project org.wicketstuff.wiquery: > > > >> wiquery-jquery-ui:jar:8.0-SNAPSHOT: Failure to find > > > >> org.wicketstuff.wiquery:wiquery-core:jar:tests:8.0-SNAPSHOT in > > > >> https://oss.sonatype.org/content/repositories/snapshots was cached > in > > > >> the local repository, resolution will not be reattempted until the > > update > > > >> interval of sonatype-nexus-snapshots has elapsed or updates are > > forced -> > > > >> [Help 1] > > > >> [ERROR] > > > > > > > > Did you change something about test-jar configuration? I do not see > > > > `test-jar` generation enabled in the POM file. > > > > > > > > On Wed, Jun 6, 2018 at 11:43 AM, Emond Papegaaij < > > > > > > > > emond.papega...@topicus.nl> wrote: > > > >> Hi Thomas, > > > >> > > > >> The easiest way is to just run 'mvn install' and depend on > > 8.0-SNAPSHOT. > > > >> I did > > > >> not do a release, as I cannot push to central. If you want to run > your > > > >> tests > > > >> on some CI server, you probably have to push the artifacts to a > local > > > >> repo > > > >> also. > > > >> > > > >> Best regards, > > > >> Emond > > > >> > > > >> On woensdag 6 juni 2018 11:36:54 CEST Thomas Heigl wrote: > > > >> > Hi Emond, > > > >> > > > > >> > How can I test this? Did you do a milestone release or do I have > to > > > >> > > > >> build > > > >> > > > >> > from source and push to my local artifact repo? > > > >> > > > > >> > Best, > > > >> > > > > >> > Thomas > > > >> > > > > >> > On Tue, Jun 5, 2018 at 3:01 PM, Emond Papegaaij < > > > >> > > > >> emond.papega...@topicus.nl> > > > >> > > > >> > wrote: > > > >> > > I've just pushed a massive upgrade of all components. Removed > all > > > >> > > deprecated > > > >> > > parts, upgraded jQuery UI to 1.12.1 and did some more cleanup > and > > > >> > > refactoring. > > > >> > > Please test the changes in your project. The tests pass and the > > demo > > > >> > > > >> runs > > > >> > > > >> > > fine, but my project only uses a limited set of the UI > components. > > > >> > > > > > >> > > Best regards, > > > >> > > Emond > > > >> > > > > > >> > > On zaterdag 2 juni 2018 10:31:31 CEST you wrote: > > > >> > > > I'm planning to upgrade jQuery UI to the latest version next > > week. > > > >> > > > >> We > > > >> > > > >> > > > are > > > >> > > > currently migrating all our applications to wicket 8 and also > > > >> > > > >> depend on > > > >> > > > >> > > > wiquery quite a lot. It does however seem that jQuery UI is > > mostly > > > >> > > > >> dead. > > > >> > > > >> > > > The rest of the world probably switched to yet another fancy > > > >> > > > >> JavaScript > > > >> > > > >> > > ui > > > >> > > > > > >> > > > library. At least the will make it easy to stay up to date > with > > the > > > >> > > > > > >> > > latest > > > >> > > > > > >> > > > version :) > > > >> > > > > > > >> > > > I can't push a release to central, but perhaps Martin can do > > that > > > >> > > > >> when > > > >> > > > >> > > I'm > > > >> > > > > > >> > > > done? For now you can use a snapshot build. It works, but the >
Re: Release WiQuery for Wicket 8
Hi Emond, I did some exploratory testing against the current build. I checked Dialog, Autocomplete, Accordion, Slider, Sortable, and Tooltip and all seem to be working at first glance. All my tests pass as well. Best, Thomas On Wed, Jun 6, 2018 at 1:07 PM, Emond Papegaaij wrote: > I've fixed the problem. The setup currently used is discouraged and broken > in > m2e, but I don't feel like restructuring the whole thing to get rid of > this > test-jar. > > Emond > > On woensdag 6 juni 2018 11:57:43 CEST Thomas Heigl wrote: > > The culprit is: > > > > https://github.com/wicketstuff/wiquery/commit/ > 0235691174ceeede22b588d2f67868 > > b940d9be3a > > On Wed, Jun 6, 2018 at 11:51 AM, Thomas Heigl > wrote: > > > `mvn clean install` fails for me because no test-jar is built for the > core > > > module: > > > > > > [INFO] WiQuery Parent 8.0-SNAPSHOT SUCCESS [ > > > > > >> 0.353 s] > > >> > > >> [INFO] WiQuery Core Project ... SUCCESS [ > > >> > > >> 2.673 s] > > >> > > >> [INFO] WiQuery jQuery UI Project .. FAILURE [ > > >> > > >> 0.023 s] > > >> > > >> [INFO] WiQuery Demo Project 8.0-SNAPSHOT .. SKIPPED > > >> [INFO] > > >> > > >> [INFO] BUILD FAILURE > > >> [INFO] > > >> > > >> [INFO] Total time: 3.720 s > > >> [INFO] Finished at: 2018-06-06T11:48:16+02:00 > > >> [INFO] > > >> > > >> [ERROR] Failed to execute goal on project wiquery-jquery-ui: Could not > > >> resolve dependencies for project org.wicketstuff.wiquery: > > >> wiquery-jquery-ui:jar:8.0-SNAPSHOT: Failure to find > > >> org.wicketstuff.wiquery:wiquery-core:jar:tests:8.0-SNAPSHOT in > > >> https://oss.sonatype.org/content/repositories/snapshots was cached in > > >> the local repository, resolution will not be reattempted until the > update > > >> interval of sonatype-nexus-snapshots has elapsed or updates are > forced -> > > >> [Help 1] > > >> [ERROR] > > > > > > Did you change something about test-jar configuration? I do not see > > > `test-jar` generation enabled in the POM file. > > > > > > On Wed, Jun 6, 2018 at 11:43 AM, Emond Papegaaij < > > > > > > emond.papega...@topicus.nl> wrote: > > >> Hi Thomas, > > >> > > >> The easiest way is to just run 'mvn install' and depend on > 8.0-SNAPSHOT. > > >> I did > > >> not do a release, as I cannot push to central. If you want to run your > > >> tests > > >> on some CI server, you probably have to push the artifacts to a local > > >> repo > > >> also. > > >> > > >> Best regards, > > >> Emond > > >> > > >> On woensdag 6 juni 2018 11:36:54 CEST Thomas Heigl wrote: > > >> > Hi Emond, > > >> > > > >> > How can I test this? Did you do a milestone release or do I have to > > >> > > >> build > > >> > > >> > from source and push to my local artifact repo? > > >> > > > >> > Best, > > >> > > > >> > Thomas > > >> > > > >> > On Tue, Jun 5, 2018 at 3:01 PM, Emond Papegaaij < > > >> > > >> emond.papega...@topicus.nl> > > >> > > >> > wrote: > > >> > > I've just pushed a massive upgrade of all components. Removed all > > >> > > deprecated > > >> > > parts, upgraded jQuery UI to 1.12.1 and did some more cleanup and > > >> > > refactoring. > > >> > > Please test the changes in your project. The tests pass and the > demo > > >> > > >> runs > > >> > > >> > > fine, but my project only uses a limited set of the UI components. > > >> > > > > >> > > Best regards, > > >> > > Emond > > >> > > > > >> > > On zaterdag 2 juni 2018 10:31:31 CEST you wrote: > > >> > > > I'm planning to upgrade jQuery UI to the latest version next > week. > > >> > > >> We > > >> > > >> > > > are > > >> > > > currently migrating all our applications to wicket 8 and also > > >> > > >> depend on > > >> > > >> > > > wiquery quite a lot. It does however seem that jQuery UI is > mostly > > >> > > >> dead. > > >> > > >> > > > The rest of the world probably switched to yet another fancy > > >> > > >> JavaScript > > >> > > >> > > ui > > >> > > > > >> > > > library. At least the will make it easy to stay up to date with > the > > >> > > > > >> > > latest > > >> > > > > >> > > > version :) > > >> > > > > > >> > > > I can't push a release to central, but perhaps Martin can do > that > > >> > > >> when > > >> > > >> > > I'm > > >> > > > > >> > > > done? For now you can use a snapshot build. It works, but the UI > > >> > > > API > > >> > > > > >> > > might > > >> > > > > >> > > > change a bit before the 8.0 release. > > >> > > > > > >> > > > Best regards, > > >> > > > Emond Papegaaij > > >> > > > > > >> > > > Op vr 1 jun. 2018 17:36 schreef Thomas Heigl < > tho...@umschalt.com>: > > >> > > > > Hi Ernesto, > > >> > > > > > > >> > > > > I'm not sure how many people are still using it. But as I > said, > > >> > > > > my > > >> > > > > >> > > project > >
Re: Debugging options
Hi, I'd guess you have a problem with your equals() implementation. If you can't reproduce the problem in a quickstart, you'll have to resort to debugging. If you send me some details (PM?), I can take a look. Have fun Sven Am 06.06.2018 um 21:16 schrieb sorinev: I have some code that's not working like it should, and like it does in other projects. I made a quickstart, but it works there. What other debugging options do I have besides plain Java debugging (short of sharing my repo with a maintainer / expert, which I'm 100% open to)? I have a DropDownChoice with a PropertyModel. The dropdown is set up initially just fine. But any changes to the selection result in the property object being null and I can't for the life of me figure out why. I've included the wicket sources in my debugger and have poked around in there, but can't see anything obvious to my untrained eye. I use this same pattern in lots of other files in different projects, but for some reason it's just not working here, so I'm obviously missing something, but can't figure out what. Wicket 7.11. -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
