Re: CookieValuePersister not support encoding other than ISO8859-1
Hi, CookieValuePersister tells me that you use Wicket 1.4 or earlier. 1.4.x is not supported anymore. You are recommended to upgrade. Additionally the stacktrace says that Tomcat doesn't allow the problematic character. Better ask in Tomcat's users@ mailing list about this restriction. I guess some specification mandates it. On Wed, Jan 2, 2013 at 7:31 PM, oliver.stef ova...@gmail.com wrote: Hi, I'm trying save some values with CookieValuePersister and it all working OK when the value is in English, but when i'm trying to use other input (like Chinese, Japanese... etc. ) i get some error. The Error: ... java.lang.IllegalArgumentException: Control character in cookie value or attribute. at org.apache.tomcat.util.http.CookieSupport.isHttpSeparator(CookieSupport.java:177) at org.apache.tomcat.util.http.CookieSupport.isHttpToken(CookieSupport.java:199) at org.apache.tomcat.util.http.ServerCookie.appendCookieValue(ServerCookie.java:187) at org.apache.catalina.connector.Response.addCookieInternal(Response.java:1045) ... any ideas? 10x! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/CookieValuePersister-not-support-encoding-other-than-ISO8859-1-tp4655123.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com http://jweekend.com/
Re: Wicket form with AJAX drop down choice and AJAX button not process POST data
Hi,
If you are able to reproduce the problem in a quickstart application then
please attach it to a ticket in Jira.
But I guess the problem is related to the custom prefix you use (#
getInputNamePrefix()).
In FormComponent#getInputAsArray() check what is the inputName and compare
it against the ones shown by Firebug.
On Thu, Jan 3, 2013 at 1:56 AM, Behrooz Nobakht nob...@gmail.com wrote:
Hello,
I'm trying to have a simple widget in Apache Wicket 6.4.0 using
Form
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/markup/html/form/Form.html
, DropDownChoice
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/markup/html/form/DropDownChoice.html
,AjaxButton
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/ajax/markup/html/form/AjaxButton.html
along
with AjaxFormComponentUpdatingBehavior
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/ajax/form/AjaxFormComponentUpdatingBehavior.html
.
The model (an inner class) that is used is as follows:
private class SampleModel implements IClusterable {
private static final long serialVersionUID = 1L;
private String value;
public void setValue(String value) {
this.value = value;
}
public String getValue() {
return value;
}
@Override
public int hashCode() {
return value.hashCode();
}
@Override
public boolean equals(Object obj) {
if (obj == null) {
return false;
}
if (obj == this) {
return true;
}
if (obj instanceof SampleModel == false) {
return false;
}
return hashCode() == obj.hashCode();
}
}
The form is another class as:
private class TheForm extends FormSampleModel {
private static final long serialVersionUID = 1L;
// This form is to be used several times in a single large page
private final String prefix = form_ + (counter++) + _;
public TheForm(String id, SampleModel model) {
super(id, new CompoundPropertyModel(model));
ListString choices = getChoices();
final DropDownChoiceString select = new
DropDownChoiceString(value, choices);
select.setOutputMarkupId(true);
select.add(new AjaxFormComponentUpdatingBehavior(onchange) {
private static final long serialVersionUID = 1L;
@Override
protected void onUpdate(AjaxRequestTarget target) {
String m1 = select.getModelObject();
String m2 = TheForm.this.getModelObject().getValue();
System.out.println(m1 + = + m2);
}
});
AjaxButton action1 = new AjaxButton(action, Model.of(Ajax
Action)) {
private static final long serialVersionUID = 1L;
@Override
protected void onSubmit(AjaxRequestTarget target, Form?
form) {
String m1 = select.getModelObject();
String m2 = TheForm.this.getModelObject().getValue();
System.out.println(m1 + = + m2);
}
};
action1.setOutputMarkupId(true);
add(select);
add(action1);
}
@Override
protected String getInputNamePrefix() {
return prefix;
}
}
And putting it all together in a simple widget class:
public class SampleFormDropDownWidget extends Panel {
private static final long serialVersionUID = 1L;
private static int counter = 1;
private SampleModel model = new SampleModel();
public SampleFormDropDownWidget(String id) {
super(id);
model.setValue(C);
TheForm form = new TheForm(form, model);
add(form);
}
private ListString getChoices() {
return Lists.newArrayList(A, B, C, D, E, F, G);
}}
And the markup HTML is:
wicket:panel
form class=form-horizontal wicket:id=form
div class=control-group
label class=control-labelChoices/label
div class=controls
select class=input-xlarge wicket:id=value/select
/div
/div
div class=form-actions
input class=btn wicket:id=action /
/div
/form/wicket:panel
Using a client debugging tool such as FireBug, I can trace that the AJAX
request actually carries POST data, e.g.:
form_1_formb1_hf_0=form_1_value=5form_1_action=Ajax+Actionform_1_action=1
However, in both cases of onUpdate for the select component and onSubmit
for
the button, I getnull values. Additionally, I debugged the code until
Wicket's FormComponent#getInputAsArray()and there actually I can see that
RequestCycle.getRequest().getRequestParameters().getParameterValues(VALUE_SELECT)does
not find any data on the request parameters.
Is there a chance that this could be bug in Wicket to ignore AJAX request
payload? Or, what am I
Re: ResourceAggregator in Wicket 6.x
Hi, Check this article: http://blog.agilecoders.de/index.php/2012/12/best-practices-for-speeding-up-your-wicket6-pages-part-1/ https://github.com/l0rdn1kk0n/wicket-bootstrap/blob/master/samples/src/main/java/de/agilecoders/wicket/samples/WicketApplication.java shows how to use it. On Wed, Jan 2, 2013 at 11:40 PM, Simon B simon.bott...@gmail.com wrote: Hi, I'm trying to aggregate my javascript files into one file and then get them placed at the bottom of the page just before the /body tag. I've looked at the example here: http://www.wicket-library.com/wicket-examples-6.0.x/resourceaggregation I've managed to copy the example so that the files are placed just before the /body tag, but the aggregation bit still eludes me. I've tried and Neither seem to aggregate // merge the javascript files. Can someone give me a piece of example code that achieves this. Any help much appreciated. Cheers Simon -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/ResourceAggregator-in-Wicket-6-x-tp4655125.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com http://jweekend.com/
Re: [ANNOUNCE] Apache Wicket 6.4.0 released
Hello, I've been using net.ftlines.wicket-bean-validation for a while now and I suppose that the new experimantal org.apache.wicket.wicket-bean-validation is based on the ftlines version and will eventually replace it (at least for wicket 6 and above)? Can I just replace the ftlines version with the new one or are there any incompatibilities (except from the obvious difference in package names)? Thanks in advance 2012/12/18 Martijn Dashorst martijn.dasho...@gmail.com The Apache Wicket PMC is proud to announce Apache Wicket 6.4.0! This release marks the fourth minor release of Wicket 6. Starting with Wicket 6 we use semantic versioning for the future development of Wicket, and as such no API breaks are present in this release compared to 6.0.0. New and noteworthy === JQuery was upgraded to 1.8.3, bootstrap to 2.2.2. JSR 303 BeanValidation support -- Native support for BeanValidation (JSR 303) was added as an experimental module and released as version 0.5. You can grab it by using these maven coordinates: org.apache.wicket:wicket-bean-validation:0.5:jar or by pasting in the pom snippet below: dependency groupIdorg.apache.wicket/groupId artifactIdwicket-bean-validation/artifactId version0.5/version /dependency Note that this is an experimental module and that it is not released under the semantic versioning rules. Use at your own risk. Hierarchical feedback panel --- A new kind of feedback panel was introduced: a hierarchical feedback panel. A specialized feedback panel that only displays messages from inside a fence defined by a container component. Instances will not show messages coming from inside a nested fence, allowing the nesting of these panels to work correctly without displaying the same feedback message twice. A constructor that does not takes a fencing component creates a catch-all panel that shows messages that do not come from inside any fence or from the Session. For more information see: http://s.apache.org/wicket-FencedFeedbackPanel For the full changelog see the release notes attached to the end of this announcement. Using this release = With Apache Maven update your dependency to (and don't forget to update any other dependencies on Wicket projects to the same version): dependency groupIdorg.apache.wicket/groupId artifactIdwicket-core/artifactId version6.4.0/version /dependency Or download and build the distribution yourself, or use our convenience binary package * Source: http://www.apache.org/dyn/closer.cgi/wicket/6.4.0 * Binary: http://www.apache.org/dyn/closer.cgi/wicket/6.4.0/binaries Upgrading from earlier versions === If you upgrade from 6.0.0, 6.1.0, 6.2.0 or 6.3.0 this release is a drop in replacement. If you come from a version prior to 6.0.0, please read our Wicket 6 migration guide found at http://s.apache.org/wicket-6.0-migration Have fun! — The Wicket team == Release Notes - Wicket - Version 6.4.0 ** Sub-task * [WICKET-4880] - Make it possible to override the Ajax behavior of AjaxSubmitLink and AjaxButton ** Bug * [WICKET-4869] - Wicket-Atmosphere track message length * [WICKET-4872] - IllegalArgumentException on ReloadingWicketFilter and inheritance markup * [WICKET-4877] - encodeUrl fails parsing jsessionid when using root context * [WICKET-4878] - Rendering of feedback messages fails with DebugBar in page * [WICKET-4881] - IE 8 : error when handling Wicket Ajax Response * [WICKET-4884] - ValidationError messages for NumberTextFields with minimum/maximum are always English * [WICKET-4886] - Do not register Ajax timer if the component is removed * [WICKET-4890] - Bad validation messages after WICKET-2128 * [WICKET-4891] - UrlRenderer.renderRelativeUrl misbehavior if the filterPath is composed. * [WICKET-4894] - Internet Explorer fails fails to properly include conditional stylesheet links added via AjaxRequestTarget * [WICKET-4895] - WicketRuntimeException: addOrReplace for feedback panel does not clear Component.FEEDBACK_LIST - feedback from replaced component causes error. * [WICKET-4899] - autocomplete shows strings with quotes strings as string2 with quot;quotequot; * [WICKET-4900] - Setting a status code on an AbstractResource results in no HTTP body * [WICKET-4908] - Wrong charset or screwed up characters in Norwegian properties-file * [WICKET-4911] - Palette Ajax update does not work * [WICKET-4913] - HtmlDocumentParser does not support tags containing number (e.g. h1-h6) * [WICKET-4915] - org.apache.wicket.util.resource.Patht#find fails on Windows * [WICKET-4916] - AbstractTree$TreeItem renderHead does not call renderHead for child TreeItems. * [WICKET-4917] -
Re: [ANNOUNCE] Apache Wicket 6.4.0 released
I think it is safe to use the new one. On Thu, Jan 3, 2013 at 1:44 PM, heapifyman heapify...@gmail.com wrote: Hello, I've been using net.ftlines.wicket-bean-validation for a while now and I suppose that the new experimantal org.apache.wicket.wicket-bean-validation is based on the ftlines version and will eventually replace it (at least for wicket 6 and above)? Can I just replace the ftlines version with the new one or are there any incompatibilities (except from the obvious difference in package names)? Thanks in advance 2012/12/18 Martijn Dashorst martijn.dasho...@gmail.com The Apache Wicket PMC is proud to announce Apache Wicket 6.4.0! This release marks the fourth minor release of Wicket 6. Starting with Wicket 6 we use semantic versioning for the future development of Wicket, and as such no API breaks are present in this release compared to 6.0.0. New and noteworthy === JQuery was upgraded to 1.8.3, bootstrap to 2.2.2. JSR 303 BeanValidation support -- Native support for BeanValidation (JSR 303) was added as an experimental module and released as version 0.5. You can grab it by using these maven coordinates: org.apache.wicket:wicket-bean-validation:0.5:jar or by pasting in the pom snippet below: dependency groupIdorg.apache.wicket/groupId artifactIdwicket-bean-validation/artifactId version0.5/version /dependency Note that this is an experimental module and that it is not released under the semantic versioning rules. Use at your own risk. Hierarchical feedback panel --- A new kind of feedback panel was introduced: a hierarchical feedback panel. A specialized feedback panel that only displays messages from inside a fence defined by a container component. Instances will not show messages coming from inside a nested fence, allowing the nesting of these panels to work correctly without displaying the same feedback message twice. A constructor that does not takes a fencing component creates a catch-all panel that shows messages that do not come from inside any fence or from the Session. For more information see: http://s.apache.org/wicket-FencedFeedbackPanel For the full changelog see the release notes attached to the end of this announcement. Using this release = With Apache Maven update your dependency to (and don't forget to update any other dependencies on Wicket projects to the same version): dependency groupIdorg.apache.wicket/groupId artifactIdwicket-core/artifactId version6.4.0/version /dependency Or download and build the distribution yourself, or use our convenience binary package * Source: http://www.apache.org/dyn/closer.cgi/wicket/6.4.0 * Binary: http://www.apache.org/dyn/closer.cgi/wicket/6.4.0/binaries Upgrading from earlier versions === If you upgrade from 6.0.0, 6.1.0, 6.2.0 or 6.3.0 this release is a drop in replacement. If you come from a version prior to 6.0.0, please read our Wicket 6 migration guide found at http://s.apache.org/wicket-6.0-migration Have fun! — The Wicket team == Release Notes - Wicket - Version 6.4.0 ** Sub-task * [WICKET-4880] - Make it possible to override the Ajax behavior of AjaxSubmitLink and AjaxButton ** Bug * [WICKET-4869] - Wicket-Atmosphere track message length * [WICKET-4872] - IllegalArgumentException on ReloadingWicketFilter and inheritance markup * [WICKET-4877] - encodeUrl fails parsing jsessionid when using root context * [WICKET-4878] - Rendering of feedback messages fails with DebugBar in page * [WICKET-4881] - IE 8 : error when handling Wicket Ajax Response * [WICKET-4884] - ValidationError messages for NumberTextFields with minimum/maximum are always English * [WICKET-4886] - Do not register Ajax timer if the component is removed * [WICKET-4890] - Bad validation messages after WICKET-2128 * [WICKET-4891] - UrlRenderer.renderRelativeUrl misbehavior if the filterPath is composed. * [WICKET-4894] - Internet Explorer fails fails to properly include conditional stylesheet links added via AjaxRequestTarget * [WICKET-4895] - WicketRuntimeException: addOrReplace for feedback panel does not clear Component.FEEDBACK_LIST - feedback from replaced component causes error. * [WICKET-4899] - autocomplete shows strings with quotes strings as string2 with quot;quotequot; * [WICKET-4900] - Setting a status code on an AbstractResource results in no HTTP body * [WICKET-4908] - Wrong charset or screwed up characters in Norwegian properties-file * [WICKET-4911] - Palette Ajax update does not work * [WICKET-4913] - HtmlDocumentParser does not support tags
Re: ResourceAggregator in Wicket 6.x
Thanks Martin, I'll take a look at those, Cheers Simon -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/ResourceAggregator-in-Wicket-6-x-tp4655125p4655137.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket form with AJAX drop down choice and AJAX button not process POST data
Hi,
I've also tested without the prefix input name and it's still the same.
Thanks,
Behrooz
On Thu, Jan 3, 2013 at 9:08 AM, Martin Grigorov mgrigo...@apache.orgwrote:
Hi,
If you are able to reproduce the problem in a quickstart application then
please attach it to a ticket in Jira.
But I guess the problem is related to the custom prefix you use (#
getInputNamePrefix()).
In FormComponent#getInputAsArray() check what is the inputName and compare
it against the ones shown by Firebug.
On Thu, Jan 3, 2013 at 1:56 AM, Behrooz Nobakht nob...@gmail.com wrote:
Hello,
I'm trying to have a simple widget in Apache Wicket 6.4.0 using
Form
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/markup/html/form/Form.html
, DropDownChoice
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/markup/html/form/DropDownChoice.html
,AjaxButton
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/ajax/markup/html/form/AjaxButton.html
along
with AjaxFormComponentUpdatingBehavior
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/ajax/form/AjaxFormComponentUpdatingBehavior.html
.
The model (an inner class) that is used is as follows:
private class SampleModel implements IClusterable {
private static final long serialVersionUID = 1L;
private String value;
public void setValue(String value) {
this.value = value;
}
public String getValue() {
return value;
}
@Override
public int hashCode() {
return value.hashCode();
}
@Override
public boolean equals(Object obj) {
if (obj == null) {
return false;
}
if (obj == this) {
return true;
}
if (obj instanceof SampleModel == false) {
return false;
}
return hashCode() == obj.hashCode();
}
}
The form is another class as:
private class TheForm extends FormSampleModel {
private static final long serialVersionUID = 1L;
// This form is to be used several times in a single large page
private final String prefix = form_ + (counter++) + _;
public TheForm(String id, SampleModel model) {
super(id, new CompoundPropertyModel(model));
ListString choices = getChoices();
final DropDownChoiceString select = new
DropDownChoiceString(value, choices);
select.setOutputMarkupId(true);
select.add(new AjaxFormComponentUpdatingBehavior(onchange) {
private static final long serialVersionUID = 1L;
@Override
protected void onUpdate(AjaxRequestTarget target) {
String m1 = select.getModelObject();
String m2 = TheForm.this.getModelObject().getValue();
System.out.println(m1 + = + m2);
}
});
AjaxButton action1 = new AjaxButton(action, Model.of(Ajax
Action)) {
private static final long serialVersionUID = 1L;
@Override
protected void onSubmit(AjaxRequestTarget target, Form?
form) {
String m1 = select.getModelObject();
String m2 = TheForm.this.getModelObject().getValue();
System.out.println(m1 + = + m2);
}
};
action1.setOutputMarkupId(true);
add(select);
add(action1);
}
@Override
protected String getInputNamePrefix() {
return prefix;
}
}
And putting it all together in a simple widget class:
public class SampleFormDropDownWidget extends Panel {
private static final long serialVersionUID = 1L;
private static int counter = 1;
private SampleModel model = new SampleModel();
public SampleFormDropDownWidget(String id) {
super(id);
model.setValue(C);
TheForm form = new TheForm(form, model);
add(form);
}
private ListString getChoices() {
return Lists.newArrayList(A, B, C, D, E, F, G);
}}
And the markup HTML is:
wicket:panel
form class=form-horizontal wicket:id=form
div class=control-group
label class=control-labelChoices/label
div class=controls
select class=input-xlarge wicket:id=value/select
/div
/div
div class=form-actions
input class=btn wicket:id=action /
/div
/form/wicket:panel
Using a client debugging tool such as FireBug, I can trace that the AJAX
request actually carries POST data, e.g.:
form_1_formb1_hf_0=form_1_value=5form_1_action=Ajax+Actionform_1_action=1
However, in both cases of onUpdate for the select component and onSubmit
for
the button, I getnull values.
Re: [ANNOUNCE] Apache Wicket 6.4.0 released
there are some incompatibilities. ive optimized some code to make it faster and remove some other code that i do not thing belongs. so, no, it is not a drop in replacement and, yes, this code deprecates the net.ftlines code for wicket 6+ -igor On Thu, Jan 3, 2013 at 3:44 AM, heapifyman heapify...@gmail.com wrote: Hello, I've been using net.ftlines.wicket-bean-validation for a while now and I suppose that the new experimantal org.apache.wicket.wicket-bean-validation is based on the ftlines version and will eventually replace it (at least for wicket 6 and above)? Can I just replace the ftlines version with the new one or are there any incompatibilities (except from the obvious difference in package names)? Thanks in advance 2012/12/18 Martijn Dashorst martijn.dasho...@gmail.com The Apache Wicket PMC is proud to announce Apache Wicket 6.4.0! This release marks the fourth minor release of Wicket 6. Starting with Wicket 6 we use semantic versioning for the future development of Wicket, and as such no API breaks are present in this release compared to 6.0.0. New and noteworthy === JQuery was upgraded to 1.8.3, bootstrap to 2.2.2. JSR 303 BeanValidation support -- Native support for BeanValidation (JSR 303) was added as an experimental module and released as version 0.5. You can grab it by using these maven coordinates: org.apache.wicket:wicket-bean-validation:0.5:jar or by pasting in the pom snippet below: dependency groupIdorg.apache.wicket/groupId artifactIdwicket-bean-validation/artifactId version0.5/version /dependency Note that this is an experimental module and that it is not released under the semantic versioning rules. Use at your own risk. Hierarchical feedback panel --- A new kind of feedback panel was introduced: a hierarchical feedback panel. A specialized feedback panel that only displays messages from inside a fence defined by a container component. Instances will not show messages coming from inside a nested fence, allowing the nesting of these panels to work correctly without displaying the same feedback message twice. A constructor that does not takes a fencing component creates a catch-all panel that shows messages that do not come from inside any fence or from the Session. For more information see: http://s.apache.org/wicket-FencedFeedbackPanel For the full changelog see the release notes attached to the end of this announcement. Using this release = With Apache Maven update your dependency to (and don't forget to update any other dependencies on Wicket projects to the same version): dependency groupIdorg.apache.wicket/groupId artifactIdwicket-core/artifactId version6.4.0/version /dependency Or download and build the distribution yourself, or use our convenience binary package * Source: http://www.apache.org/dyn/closer.cgi/wicket/6.4.0 * Binary: http://www.apache.org/dyn/closer.cgi/wicket/6.4.0/binaries Upgrading from earlier versions === If you upgrade from 6.0.0, 6.1.0, 6.2.0 or 6.3.0 this release is a drop in replacement. If you come from a version prior to 6.0.0, please read our Wicket 6 migration guide found at http://s.apache.org/wicket-6.0-migration Have fun! — The Wicket team == Release Notes - Wicket - Version 6.4.0 ** Sub-task * [WICKET-4880] - Make it possible to override the Ajax behavior of AjaxSubmitLink and AjaxButton ** Bug * [WICKET-4869] - Wicket-Atmosphere track message length * [WICKET-4872] - IllegalArgumentException on ReloadingWicketFilter and inheritance markup * [WICKET-4877] - encodeUrl fails parsing jsessionid when using root context * [WICKET-4878] - Rendering of feedback messages fails with DebugBar in page * [WICKET-4881] - IE 8 : error when handling Wicket Ajax Response * [WICKET-4884] - ValidationError messages for NumberTextFields with minimum/maximum are always English * [WICKET-4886] - Do not register Ajax timer if the component is removed * [WICKET-4890] - Bad validation messages after WICKET-2128 * [WICKET-4891] - UrlRenderer.renderRelativeUrl misbehavior if the filterPath is composed. * [WICKET-4894] - Internet Explorer fails fails to properly include conditional stylesheet links added via AjaxRequestTarget * [WICKET-4895] - WicketRuntimeException: addOrReplace for feedback panel does not clear Component.FEEDBACK_LIST - feedback from replaced component causes error. * [WICKET-4899] - autocomplete shows strings with quotes strings as string2 with quot;quotequot; * [WICKET-4900] - Setting a status code on an AbstractResource results in no HTTP body * [WICKET-4908] - Wrong charset or screwed up characters in Norwegian properties-file * [WICKET-4911] - Palette Ajax
Re: [ANNOUNCE] Apache Wicket 6.4.0 released
Thanks for clarifying. I tested a bit with the new bean-validation module and so far everything seems to be working. 2013/1/3 Igor Vaynberg igor.vaynb...@gmail.com there are some incompatibilities. ive optimized some code to make it faster and remove some other code that i do not thing belongs. so, no, it is not a drop in replacement and, yes, this code deprecates the net.ftlines code for wicket 6+ -igor On Thu, Jan 3, 2013 at 3:44 AM, heapifyman heapify...@gmail.com wrote: Hello, I've been using net.ftlines.wicket-bean-validation for a while now and I suppose that the new experimantal org.apache.wicket.wicket-bean-validation is based on the ftlines version and will eventually replace it (at least for wicket 6 and above)? Can I just replace the ftlines version with the new one or are there any incompatibilities (except from the obvious difference in package names)? Thanks in advance 2012/12/18 Martijn Dashorst martijn.dasho...@gmail.com The Apache Wicket PMC is proud to announce Apache Wicket 6.4.0! This release marks the fourth minor release of Wicket 6. Starting with Wicket 6 we use semantic versioning for the future development of Wicket, and as such no API breaks are present in this release compared to 6.0.0. New and noteworthy === JQuery was upgraded to 1.8.3, bootstrap to 2.2.2. JSR 303 BeanValidation support -- Native support for BeanValidation (JSR 303) was added as an experimental module and released as version 0.5. You can grab it by using these maven coordinates: org.apache.wicket:wicket-bean-validation:0.5:jar or by pasting in the pom snippet below: dependency groupIdorg.apache.wicket/groupId artifactIdwicket-bean-validation/artifactId version0.5/version /dependency Note that this is an experimental module and that it is not released under the semantic versioning rules. Use at your own risk. Hierarchical feedback panel --- A new kind of feedback panel was introduced: a hierarchical feedback panel. A specialized feedback panel that only displays messages from inside a fence defined by a container component. Instances will not show messages coming from inside a nested fence, allowing the nesting of these panels to work correctly without displaying the same feedback message twice. A constructor that does not takes a fencing component creates a catch-all panel that shows messages that do not come from inside any fence or from the Session. For more information see: http://s.apache.org/wicket-FencedFeedbackPanel For the full changelog see the release notes attached to the end of this announcement. Using this release = With Apache Maven update your dependency to (and don't forget to update any other dependencies on Wicket projects to the same version): dependency groupIdorg.apache.wicket/groupId artifactIdwicket-core/artifactId version6.4.0/version /dependency Or download and build the distribution yourself, or use our convenience binary package * Source: http://www.apache.org/dyn/closer.cgi/wicket/6.4.0 * Binary: http://www.apache.org/dyn/closer.cgi/wicket/6.4.0/binaries Upgrading from earlier versions === If you upgrade from 6.0.0, 6.1.0, 6.2.0 or 6.3.0 this release is a drop in replacement. If you come from a version prior to 6.0.0, please read our Wicket 6 migration guide found at http://s.apache.org/wicket-6.0-migration Have fun! — The Wicket team == Release Notes - Wicket - Version 6.4.0 ** Sub-task * [WICKET-4880] - Make it possible to override the Ajax behavior of AjaxSubmitLink and AjaxButton ** Bug * [WICKET-4869] - Wicket-Atmosphere track message length * [WICKET-4872] - IllegalArgumentException on ReloadingWicketFilter and inheritance markup * [WICKET-4877] - encodeUrl fails parsing jsessionid when using root context * [WICKET-4878] - Rendering of feedback messages fails with DebugBar in page * [WICKET-4881] - IE 8 : error when handling Wicket Ajax Response * [WICKET-4884] - ValidationError messages for NumberTextFields with minimum/maximum are always English * [WICKET-4886] - Do not register Ajax timer if the component is removed * [WICKET-4890] - Bad validation messages after WICKET-2128 * [WICKET-4891] - UrlRenderer.renderRelativeUrl misbehavior if the filterPath is composed. * [WICKET-4894] - Internet Explorer fails fails to properly include conditional stylesheet links added via AjaxRequestTarget * [WICKET-4895] - WicketRuntimeException: addOrReplace for feedback panel does not clear Component.FEEDBACK_LIST - feedback from replaced component causes error. * [WICKET-4899]
Clearing Browser Cookies
This is a rehash of a previous discussion on this forum relating to immediate removal of a browser cookie. I have a list view that displays data loaded from 1 or more browser cookies. On this panel I also have a clear action (Link) that when clicked deletes the cookies. The underlying list view model is detached which forces (verified) the cookies to be re-read. The problem is that when I re-read them after deleting them from the response, they are still present. If I then execute the clear action again, the list view is refreshed again and the cookies are no longer present. I'm not sure what is going on here. Are they being cached, is it a timing issue? Why on the second clear action does it finally indicate the cookies have been removed. My immediate need is to be able to delete the cookies, refresh the list view, and see that they are no longer present (no data rows in list view). J.D.
Re: Wicket form with AJAX drop down choice and AJAX button not process POST data
Hi again,
I tried the quick start application and tracked down the issue to this.
When a selection is changed (using FireBug/Chrome),
* in the quick start application, I see that of the request is
Content-Type:
application/x-www-form-urlencoded; charset=UTF-8
* in my application, I see that the content-type of the request is
text/plain
This is why in my application, the request POST data is actually ignored.
I verified that all my HTML files start with
!DOCTYPE html
html xmlns:wicket=http://wicket.apache.org;
So, can you please let me know how to fix this?
Thanks,
Behrooz
On Thu, Jan 3, 2013 at 5:42 PM, Behrooz Nobakht nob...@gmail.com wrote:
Hi,
I've also tested without the prefix input name and it's still the same.
Thanks,
Behrooz
On Thu, Jan 3, 2013 at 9:08 AM, Martin Grigorov mgrigo...@apache.orgwrote:
Hi,
If you are able to reproduce the problem in a quickstart application then
please attach it to a ticket in Jira.
But I guess the problem is related to the custom prefix you use (#
getInputNamePrefix()).
In FormComponent#getInputAsArray() check what is the inputName and compare
it against the ones shown by Firebug.
On Thu, Jan 3, 2013 at 1:56 AM, Behrooz Nobakht nob...@gmail.com wrote:
Hello,
I'm trying to have a simple widget in Apache Wicket 6.4.0 using
Form
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/markup/html/form/Form.html
, DropDownChoice
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/markup/html/form/DropDownChoice.html
,AjaxButton
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/ajax/markup/html/form/AjaxButton.html
along
with AjaxFormComponentUpdatingBehavior
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/ajax/form/AjaxFormComponentUpdatingBehavior.html
.
The model (an inner class) that is used is as follows:
private class SampleModel implements IClusterable {
private static final long serialVersionUID = 1L;
private String value;
public void setValue(String value) {
this.value = value;
}
public String getValue() {
return value;
}
@Override
public int hashCode() {
return value.hashCode();
}
@Override
public boolean equals(Object obj) {
if (obj == null) {
return false;
}
if (obj == this) {
return true;
}
if (obj instanceof SampleModel == false) {
return false;
}
return hashCode() == obj.hashCode();
}
}
The form is another class as:
private class TheForm extends FormSampleModel {
private static final long serialVersionUID = 1L;
// This form is to be used several times in a single large page
private final String prefix = form_ + (counter++) + _;
public TheForm(String id, SampleModel model) {
super(id, new CompoundPropertyModel(model));
ListString choices = getChoices();
final DropDownChoiceString select = new
DropDownChoiceString(value, choices);
select.setOutputMarkupId(true);
select.add(new AjaxFormComponentUpdatingBehavior(onchange) {
private static final long serialVersionUID = 1L;
@Override
protected void onUpdate(AjaxRequestTarget target) {
String m1 = select.getModelObject();
String m2 = TheForm.this.getModelObject().getValue();
System.out.println(m1 + = + m2);
}
});
AjaxButton action1 = new AjaxButton(action, Model.of(Ajax
Action)) {
private static final long serialVersionUID = 1L;
@Override
protected void onSubmit(AjaxRequestTarget target, Form?
form) {
String m1 = select.getModelObject();
String m2 = TheForm.this.getModelObject().getValue();
System.out.println(m1 + = + m2);
}
};
action1.setOutputMarkupId(true);
add(select);
add(action1);
}
@Override
protected String getInputNamePrefix() {
return prefix;
}
}
And putting it all together in a simple widget class:
public class SampleFormDropDownWidget extends Panel {
private static final long serialVersionUID = 1L;
private static int counter = 1;
private SampleModel model = new SampleModel();
public SampleFormDropDownWidget(String id) {
super(id);
model.setValue(C);
TheForm form = new TheForm(form, model);
add(form);
}
private ListString getChoices() {
return Lists.newArrayList(A, B, C, D, E, F, G);
}}
And the markup HTML is:
wicket:panel
form class=form-horizontal wicket:id=form
Re: Clearing Browser Cookies
Hi James, deleting a cookie on the response doesn't change the cookies in the HTTP request. A redirect should help to get a fresh cookie list from the browser. Sven On 01/03/2013 08:29 PM, Corbin, James wrote: This is a rehash of a previous discussion on this forum relating to immediate removal of a browser cookie. I have a list view that displays data loaded from 1 or more browser cookies. On this panel I also have a clear action (Link) that when clicked deletes the cookies. The underlying list view model is detached which forces (verified) the cookies to be re-read. The problem is that when I re-read them after deleting them from the response, they are still present. If I then execute the clear action again, the list view is refreshed again and the cookies are no longer present. I'm not sure what is going on here. Are they being cached, is it a timing issue? Why on the second clear action does it finally indicate the cookies have been removed. My immediate need is to be able to delete the cookies, refresh the list view, and see that they are no longer present (no data rows in list view). J.D. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket form with AJAX drop down choice and AJAX button not process POST data
Hi again,
Just wanted to update that the issue is resolved. There was a custom script
that sets the content type of AJAX on jQuery.$ to be text/plain and it had
a side effect.
Sorry for the inconvenience.
Regards,
Behrooz
On Thu, Jan 3, 2013 at 9:01 PM, Behrooz Nobakht nob...@gmail.com wrote:
Hi again,
I tried the quick start application and tracked down the issue to this.
When a selection is changed (using FireBug/Chrome),
* in the quick start application, I see that of the request is
Content-Type:
application/x-www-form-urlencoded; charset=UTF-8
* in my application, I see that the content-type of the request is
text/plain
This is why in my application, the request POST data is actually ignored.
I verified that all my HTML files start with
!DOCTYPE html
html xmlns:wicket=http://wicket.apache.org;
So, can you please let me know how to fix this?
Thanks,
Behrooz
On Thu, Jan 3, 2013 at 5:42 PM, Behrooz Nobakht nob...@gmail.com wrote:
Hi,
I've also tested without the prefix input name and it's still the same.
Thanks,
Behrooz
On Thu, Jan 3, 2013 at 9:08 AM, Martin Grigorov mgrigo...@apache.orgwrote:
Hi,
If you are able to reproduce the problem in a quickstart application then
please attach it to a ticket in Jira.
But I guess the problem is related to the custom prefix you use (#
getInputNamePrefix()).
In FormComponent#getInputAsArray() check what is the inputName and
compare
it against the ones shown by Firebug.
On Thu, Jan 3, 2013 at 1:56 AM, Behrooz Nobakht nob...@gmail.com
wrote:
Hello,
I'm trying to have a simple widget in Apache Wicket 6.4.0 using
Form
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/markup/html/form/Form.html
, DropDownChoice
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/markup/html/form/DropDownChoice.html
,AjaxButton
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/ajax/markup/html/form/AjaxButton.html
along
with AjaxFormComponentUpdatingBehavior
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/ajax/form/AjaxFormComponentUpdatingBehavior.html
.
The model (an inner class) that is used is as follows:
private class SampleModel implements IClusterable {
private static final long serialVersionUID = 1L;
private String value;
public void setValue(String value) {
this.value = value;
}
public String getValue() {
return value;
}
@Override
public int hashCode() {
return value.hashCode();
}
@Override
public boolean equals(Object obj) {
if (obj == null) {
return false;
}
if (obj == this) {
return true;
}
if (obj instanceof SampleModel == false) {
return false;
}
return hashCode() == obj.hashCode();
}
}
The form is another class as:
private class TheForm extends FormSampleModel {
private static final long serialVersionUID = 1L;
// This form is to be used several times in a single large page
private final String prefix = form_ + (counter++) + _;
public TheForm(String id, SampleModel model) {
super(id, new CompoundPropertyModel(model));
ListString choices = getChoices();
final DropDownChoiceString select = new
DropDownChoiceString(value, choices);
select.setOutputMarkupId(true);
select.add(new AjaxFormComponentUpdatingBehavior(onchange) {
private static final long serialVersionUID = 1L;
@Override
protected void onUpdate(AjaxRequestTarget target) {
String m1 = select.getModelObject();
String m2 = TheForm.this.getModelObject().getValue();
System.out.println(m1 + = + m2);
}
});
AjaxButton action1 = new AjaxButton(action, Model.of(Ajax
Action)) {
private static final long serialVersionUID = 1L;
@Override
protected void onSubmit(AjaxRequestTarget target, Form?
form) {
String m1 = select.getModelObject();
String m2 = TheForm.this.getModelObject().getValue();
System.out.println(m1 + = + m2);
}
};
action1.setOutputMarkupId(true);
add(select);
add(action1);
}
@Override
protected String getInputNamePrefix() {
return prefix;
}
}
And putting it all together in a simple widget class:
public class SampleFormDropDownWidget extends Panel {
private static final long serialVersionUID = 1L;
private static int counter = 1;
private SampleModel model = new SampleModel();
public SampleFormDropDownWidget(String id) {
Re: Clearing Browser Cookies
Thanks Sven. I wasn't sure if I could do so without a page reload, but I think it is okay in this case. J.D. On 1/3/13 1:04 PM, Sven Meier s...@meiers.net wrote: Hi James, deleting a cookie on the response doesn't change the cookies in the HTTP request. A redirect should help to get a fresh cookie list from the browser. Sven On 01/03/2013 08:29 PM, Corbin, James wrote: This is a rehash of a previous discussion on this forum relating to immediate removal of a browser cookie. I have a list view that displays data loaded from 1 or more browser cookies. On this panel I also have a clear action (Link) that when clicked deletes the cookies. The underlying list view model is detached which forces (verified) the cookies to be re-read. The problem is that when I re-read them after deleting them from the response, they are still present. If I then execute the clear action again, the list view is refreshed again and the cookies are no longer present. I'm not sure what is going on here. Are they being cached, is it a timing issue? Why on the second clear action does it finally indicate the cookies have been removed. My immediate need is to be able to delete the cookies, refresh the list view, and see that they are no longer present (no data rows in list view). J.D. - 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: wicket-cdi and TomEE
Thanks to you both for you help. Here's what I did so far: -Upgraded from TomEE 1.0.0 to 1.5.1 (not sure if that made a change, but it was a todo anyway) -Removing the seam-conversation-weld dependency -Finally, added the following section to my pom: dependencyManagement dependencies dependency artifactIdcdi-api/artifactId groupIdjavax.enterprise/groupId scopeprovided/scope /dependency /dependencies /dependencyManagement wicket-cdi includes this dependency as compile but it is provided by the Java EE container. Igor: perhaps you could modify your blog post to include the info about changing the scope of cdi-api? With these changes, I can get @RequestScoped, @SessionScoped and @ApplicationScoped working, although with warnings. I get a ton of log messages of the following type: org.apache.webbeans.component.creation.AnnotatedTypeBeanCreatorImpl defineConstructor INFO: No suitable constructor found for injection target class : [class org.apache.wicket.cdi.DetachEventEmitter]. produce() method does not work! I can't understand why I get these or what they mean. As for the conversion scope, from what I understand I should simply have to replace the seam-conversation-weld dependency with seam-conversation-owb to run with OpenWebBeans (used by TomEE). However, when I do that, all wicket pages throw an exception: java.lang.NoSuchMethodError: org.apache.webbeans.conversation.ConversationManager.getInstance()Lorg/apache/webbeans/conversation/ConversationManager; org.jboss.seam.conversation.plugins.openwebbeans.OpenWebBeansSeamConversationManager.doActivate(OpenWebBeansSeamConversationManager.java:41) org.jboss.seam.conversation.plugins.openwebbeans.OpenWebBeansHttpSeamConversationContext.doActivate(OpenWebBeansHttpSeamConversationContext.java:44) org.jboss.seam.conversation.api.AbstractSeamConversationContext.activate(AbstractSeamConversationContext.java:54) org.apache.wicket.cdi.CdiContainer.activateConversationalContext(CdiContainer.java:94) org.apache.wicket.cdi.ConversationPropagator.activateConversationIfNeeded(ConversationPropagator.java:147) org.apache.wicket.cdi.ConversationPropagator.onRequestHandlerResolved(ConversationPropagator.java:123) org.apache.wicket.request.cycle.RequestCycleListenerCollection$5.notify(RequestCycleListenerCollection.java:155) I don't need conversion scope right now, but all these warnings and errors worry me. Kurt, do you get all these errors? Regards, Bertrand On 21/12/2012 2:53 AM, Kurt Sys wrote: ... forgot this one: my full system setup, used jars etc. http://openejb.979440.n4.nabble.com/tomee-eclipselink-gt-NoClassDefFoundError-ClassNotFoundException-td4658870.html Kurt 2012/12/20 Igor Vaynberg igor.vaynb...@gmail.com: looks like you have two jars on the classpath that provide the javax.enterprise.inject.spi.BeanManager interface. maybe one comes with wicket-cdi and the other one is included in tomee... -igor On Thu, Dec 20, 2012 at 12:54 PM, Bertrand Guay-Paquet ber...@step.polymtl.ca wrote: javax.enterprise.inject.spi.BeanManage - 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: Clearing Browser Cookies
Hi Sven, I did try redirecting a couple of ways with no success. I tried throwing a RestartResponseException which didn't work, then tried setResponsePage(Š) to the same page and that didn't work either. I was still forced to press the Clear action again to see the cookies disappear. J.D. On 1/3/13 1:04 PM, Sven Meier s...@meiers.net wrote: Hi James, deleting a cookie on the response doesn't change the cookies in the HTTP request. A redirect should help to get a fresh cookie list from the browser. Sven On 01/03/2013 08:29 PM, Corbin, James wrote: This is a rehash of a previous discussion on this forum relating to immediate removal of a browser cookie. I have a list view that displays data loaded from 1 or more browser cookies. On this panel I also have a clear action (Link) that when clicked deletes the cookies. The underlying list view model is detached which forces (verified) the cookies to be re-read. The problem is that when I re-read them after deleting them from the response, they are still present. If I then execute the clear action again, the list view is refreshed again and the cookies are no longer present. I'm not sure what is going on here. Are they being cached, is it a timing issue? Why on the second clear action does it finally indicate the cookies have been removed. My immediate need is to be able to delete the cookies, refresh the list view, and see that they are no longer present (no data rows in list view). J.D. - 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: Clearing Browser Cookies
So, I tried one more thing that worked... setResponsePage(new RedirectPage(somePage)); The first time I tried it was without using the RedirectPage class. J.D. On 1/3/13 4:15 PM, Corbin, James jcor...@iqnavigator.com wrote: Hi Sven, I did try redirecting a couple of ways with no success. I tried throwing a RestartResponseException which didn't work, then tried setResponsePage(Š) to the same page and that didn't work either. I was still forced to press the Clear action again to see the cookies disappear. J.D. On 1/3/13 1:04 PM, Sven Meier s...@meiers.net wrote: Hi James, deleting a cookie on the response doesn't change the cookies in the HTTP request. A redirect should help to get a fresh cookie list from the browser. Sven On 01/03/2013 08:29 PM, Corbin, James wrote: This is a rehash of a previous discussion on this forum relating to immediate removal of a browser cookie. I have a list view that displays data loaded from 1 or more browser cookies. On this panel I also have a clear action (Link) that when clicked deletes the cookies. The underlying list view model is detached which forces (verified) the cookies to be re-read. The problem is that when I re-read them after deleting them from the response, they are still present. If I then execute the clear action again, the list view is refreshed again and the cookies are no longer present. I'm not sure what is going on here. Are they being cached, is it a timing issue? Why on the second clear action does it finally indicate the cookies have been removed. My immediate need is to be able to delete the cookies, refresh the list view, and see that they are no longer present (no data rows in list view). J.D. - 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
