Re: Contributing to Wicket - Client side form validation
Jeremy, Thanks. If the problem can no longer be replicated (OK here now but I haven't checked if Carl is still experiencing this) I assume that the parent POMs are in good shape. Regards - Cemal http://www.jWeekend.co.uk jWeekend Jeremy Thomerson-5 wrote: Cemal, I didn't have much time to look into it, but didn't see anything real obvious in any of the yav poms. Do you know what's causing the dependency? On Mon, Jan 19, 2009 at 11:16 AM, jWeekend jweekend_for...@cabouge.comwrote: Jeremy, Since you're digging around in there and if what you wanted to change doesn't already fix this, the yav and yav-examples project have unnecessary dependencies on jmxtools and jms jars (probably from some parent/grand parent POM). Regards - Cemal http://jWeekende.co.uk jWeekend Jeremy Thomerson-5 wrote: Carl, Would you mind if I made a few minor changes to your pom files to make this project conform to the standards of the wicketstuff-core projects? Things I noticed are: - yav-parent/yav/pom.xml - artifact ID must be yav rather than wicketstuff-yav - yav-parent/yav-examples/pom.xml - artifact ID must be yav-examples rather than wicketstuff-yav-examples - add yav-parent to the modules list in wicketstuff-core/pom.xml Thank you, -- Jeremy Thomerson http://www.wickettraining.com On Sun, Jan 18, 2009 at 7:35 AM, cazoury carl.azo...@zenika.com wrote: Hi, I have finally added the Wicket Yav Integration into the trunk of wicketstuff-core. There is an exemple application provided to test the actual Wicket rules that has been converted to Yav Every feedback is the most welcome and contribution also. It is a first step, but we can make it evolve maybe as Cemal suggested to include more advanced validation (like apache validator or Hibernate Validator) Cheers Nino Martinez-2 wrote: ok you should be in... We take jira and CI later.. Ok? Happy new year cazoury wrote: Thank you every one for your answers and interests on the project. I will be very happy for the project to go on Wicketstuff repo. My nick on sourceforge is : cazoury, I will post that on the dev list. Hopefully everything will be checked in before the end of the week. In terms of the actual validation, have you given any thought yet to how this can be done as DRY as possible wrt respecifying (equivalent/similar) validation at various layers including Wicket's, the ORM's, in business rules etc? for the DRY principle we only take into account the validators defined on the form components. Nothing else for the moment. They are some Validators in Wicket that are not available in YAV and the contrary. Maybe a next step will be to add them on the YAV side so all the default Wicket validators can be taken into account. But first, the checkin of the code :) Nino Martinez-2 wrote: I like to keep my contributions in wicketstuff repo, and I think us wicketstuffers would be happy to have your project there .. But no matter what I think you should contribute the stuff you've done :) So if you want, just post your sourceforge nick to the dev list to get write permissions.. And I think your project should go into wicketstuff core, but jeremy can fill you in on that :) cazoury wrote: Hi, We have been working on a small project to integrate http://yav.sourceforge.net/ YAV library with Wicket. It is javascript validation purely on the client side. YAV has a LGPL licence and is a sourceforge project. I know that we can use an Ajax Behavior to validate the form with the validators present on the server side, but this is to respond to one of our client needs and also to illustrate how easy it is to integrate an existing javascript library with Wicket. It has also some nice features like using in the javascript validation the same messages as the ones used by the Wicket application (default messages and user defined messages) We would like to contribute, if possible, this code (wicket-contrib / wicket-stuff) if people finds this interesting. But I am not sure what are the different steps for that. We where thinking making it a sourceforge or googlecode project, maybe it is the first step and then I could post the link to it on this forum. Everyone enjoy the last day(s) of this year :) Carl Azoury - 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,
Re: Contributing to Wicket - Client side form validation
Sorry it took a while, but I just got this done. jt On Mon, Jan 19, 2009 at 3:59 AM, cazoury carl.azo...@zenika.com wrote: Hi Jeremy, No problem at all, and thanks a lot for reviewing that Please feel free, let me know if you need any action from me on that subject. Carl Jeremy Thomerson-5 wrote: Carl, Would you mind if I made a few minor changes to your pom files to make this project conform to the standards of the wicketstuff-core projects? Things I noticed are: - yav-parent/yav/pom.xml - artifact ID must be yav rather than wicketstuff-yav - yav-parent/yav-examples/pom.xml - artifact ID must be yav-examples rather than wicketstuff-yav-examples - add yav-parent to the modules list in wicketstuff-core/pom.xml Thank you, -- Jeremy Thomerson http://www.wickettraining.com On Sun, Jan 18, 2009 at 7:35 AM, cazoury carl.azo...@zenika.com wrote: Hi, I have finally added the Wicket Yav Integration into the trunk of wicketstuff-core. There is an exemple application provided to test the actual Wicket rules that has been converted to Yav Every feedback is the most welcome and contribution also. It is a first step, but we can make it evolve maybe as Cemal suggested to include more advanced validation (like apache validator or Hibernate Validator) Cheers Nino Martinez-2 wrote: ok you should be in... We take jira and CI later.. Ok? Happy new year cazoury wrote: Thank you every one for your answers and interests on the project. I will be very happy for the project to go on Wicketstuff repo. My nick on sourceforge is : cazoury, I will post that on the dev list. Hopefully everything will be checked in before the end of the week. In terms of the actual validation, have you given any thought yet to how this can be done as DRY as possible wrt respecifying (equivalent/similar) validation at various layers including Wicket's, the ORM's, in business rules etc? for the DRY principle we only take into account the validators defined on the form components. Nothing else for the moment. They are some Validators in Wicket that are not available in YAV and the contrary. Maybe a next step will be to add them on the YAV side so all the default Wicket validators can be taken into account. But first, the checkin of the code :) Nino Martinez-2 wrote: I like to keep my contributions in wicketstuff repo, and I think us wicketstuffers would be happy to have your project there .. But no matter what I think you should contribute the stuff you've done :) So if you want, just post your sourceforge nick to the dev list to get write permissions.. And I think your project should go into wicketstuff core, but jeremy can fill you in on that :) cazoury wrote: Hi, We have been working on a small project to integrate http://yav.sourceforge.net/ YAV library with Wicket. It is javascript validation purely on the client side. YAV has a LGPL licence and is a sourceforge project. I know that we can use an Ajax Behavior to validate the form with the validators present on the server side, but this is to respond to one of our client needs and also to illustrate how easy it is to integrate an existing javascript library with Wicket. It has also some nice features like using in the javascript validation the same messages as the ones used by the Wicket application (default messages and user defined messages) We would like to contribute, if possible, this code (wicket-contrib / wicket-stuff) if people finds this interesting. But I am not sure what are the different steps for that. We where thinking making it a sourceforge or googlecode project, maybe it is the first step and then I could post the link to it on this forum. Everyone enjoy the last day(s) of this year :) Carl Azoury - 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 -- View this message in context: http://www.nabble.com/Contributing-to-Wicket---Client-side-form-validation-tp21219136p21527885.html Sent from the Wicket - User 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 -- View this message in context:
Re: Contributing to Wicket - Client side form validation
Cemal, I didn't have much time to look into it, but didn't see anything real obvious in any of the yav poms. Do you know what's causing the dependency? On Mon, Jan 19, 2009 at 11:16 AM, jWeekend jweekend_for...@cabouge.comwrote: Jeremy, Since you're digging around in there and if what you wanted to change doesn't already fix this, the yav and yav-examples project have unnecessary dependencies on jmxtools and jms jars (probably from some parent/grand parent POM). Regards - Cemal http://jWeekende.co.uk jWeekend Jeremy Thomerson-5 wrote: Carl, Would you mind if I made a few minor changes to your pom files to make this project conform to the standards of the wicketstuff-core projects? Things I noticed are: - yav-parent/yav/pom.xml - artifact ID must be yav rather than wicketstuff-yav - yav-parent/yav-examples/pom.xml - artifact ID must be yav-examples rather than wicketstuff-yav-examples - add yav-parent to the modules list in wicketstuff-core/pom.xml Thank you, -- Jeremy Thomerson http://www.wickettraining.com On Sun, Jan 18, 2009 at 7:35 AM, cazoury carl.azo...@zenika.com wrote: Hi, I have finally added the Wicket Yav Integration into the trunk of wicketstuff-core. There is an exemple application provided to test the actual Wicket rules that has been converted to Yav Every feedback is the most welcome and contribution also. It is a first step, but we can make it evolve maybe as Cemal suggested to include more advanced validation (like apache validator or Hibernate Validator) Cheers Nino Martinez-2 wrote: ok you should be in... We take jira and CI later.. Ok? Happy new year cazoury wrote: Thank you every one for your answers and interests on the project. I will be very happy for the project to go on Wicketstuff repo. My nick on sourceforge is : cazoury, I will post that on the dev list. Hopefully everything will be checked in before the end of the week. In terms of the actual validation, have you given any thought yet to how this can be done as DRY as possible wrt respecifying (equivalent/similar) validation at various layers including Wicket's, the ORM's, in business rules etc? for the DRY principle we only take into account the validators defined on the form components. Nothing else for the moment. They are some Validators in Wicket that are not available in YAV and the contrary. Maybe a next step will be to add them on the YAV side so all the default Wicket validators can be taken into account. But first, the checkin of the code :) Nino Martinez-2 wrote: I like to keep my contributions in wicketstuff repo, and I think us wicketstuffers would be happy to have your project there .. But no matter what I think you should contribute the stuff you've done :) So if you want, just post your sourceforge nick to the dev list to get write permissions.. And I think your project should go into wicketstuff core, but jeremy can fill you in on that :) cazoury wrote: Hi, We have been working on a small project to integrate http://yav.sourceforge.net/ YAV library with Wicket. It is javascript validation purely on the client side. YAV has a LGPL licence and is a sourceforge project. I know that we can use an Ajax Behavior to validate the form with the validators present on the server side, but this is to respond to one of our client needs and also to illustrate how easy it is to integrate an existing javascript library with Wicket. It has also some nice features like using in the javascript validation the same messages as the ones used by the Wicket application (default messages and user defined messages) We would like to contribute, if possible, this code (wicket-contrib / wicket-stuff) if people finds this interesting. But I am not sure what are the different steps for that. We where thinking making it a sourceforge or googlecode project, maybe it is the first step and then I could post the link to it on this forum. Everyone enjoy the last day(s) of this year :) Carl Azoury - 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 -- View this message in context: http://www.nabble.com/Contributing-to-Wicket---Client-side-form-validation-tp21219136p21527885.html Sent from the Wicket - User mailing list archive at Nabble.com.
Re: Contributing to Wicket - Client side form validation
Hi Jeremy, No problem at all, and thanks a lot for reviewing that Please feel free, let me know if you need any action from me on that subject. Carl Jeremy Thomerson-5 wrote: Carl, Would you mind if I made a few minor changes to your pom files to make this project conform to the standards of the wicketstuff-core projects? Things I noticed are: - yav-parent/yav/pom.xml - artifact ID must be yav rather than wicketstuff-yav - yav-parent/yav-examples/pom.xml - artifact ID must be yav-examples rather than wicketstuff-yav-examples - add yav-parent to the modules list in wicketstuff-core/pom.xml Thank you, -- Jeremy Thomerson http://www.wickettraining.com On Sun, Jan 18, 2009 at 7:35 AM, cazoury carl.azo...@zenika.com wrote: Hi, I have finally added the Wicket Yav Integration into the trunk of wicketstuff-core. There is an exemple application provided to test the actual Wicket rules that has been converted to Yav Every feedback is the most welcome and contribution also. It is a first step, but we can make it evolve maybe as Cemal suggested to include more advanced validation (like apache validator or Hibernate Validator) Cheers Nino Martinez-2 wrote: ok you should be in... We take jira and CI later.. Ok? Happy new year cazoury wrote: Thank you every one for your answers and interests on the project. I will be very happy for the project to go on Wicketstuff repo. My nick on sourceforge is : cazoury, I will post that on the dev list. Hopefully everything will be checked in before the end of the week. In terms of the actual validation, have you given any thought yet to how this can be done as DRY as possible wrt respecifying (equivalent/similar) validation at various layers including Wicket's, the ORM's, in business rules etc? for the DRY principle we only take into account the validators defined on the form components. Nothing else for the moment. They are some Validators in Wicket that are not available in YAV and the contrary. Maybe a next step will be to add them on the YAV side so all the default Wicket validators can be taken into account. But first, the checkin of the code :) Nino Martinez-2 wrote: I like to keep my contributions in wicketstuff repo, and I think us wicketstuffers would be happy to have your project there .. But no matter what I think you should contribute the stuff you've done :) So if you want, just post your sourceforge nick to the dev list to get write permissions.. And I think your project should go into wicketstuff core, but jeremy can fill you in on that :) cazoury wrote: Hi, We have been working on a small project to integrate http://yav.sourceforge.net/ YAV library with Wicket. It is javascript validation purely on the client side. YAV has a LGPL licence and is a sourceforge project. I know that we can use an Ajax Behavior to validate the form with the validators present on the server side, but this is to respond to one of our client needs and also to illustrate how easy it is to integrate an existing javascript library with Wicket. It has also some nice features like using in the javascript validation the same messages as the ones used by the Wicket application (default messages and user defined messages) We would like to contribute, if possible, this code (wicket-contrib / wicket-stuff) if people finds this interesting. But I am not sure what are the different steps for that. We where thinking making it a sourceforge or googlecode project, maybe it is the first step and then I could post the link to it on this forum. Everyone enjoy the last day(s) of this year :) Carl Azoury - 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 -- View this message in context: http://www.nabble.com/Contributing-to-Wicket---Client-side-form-validation-tp21219136p21527885.html Sent from the Wicket - User 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 -- View this message in context: http://www.nabble.com/Contributing-to-Wicket---Client-side-form-validation-tp21219136p21539881.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands,
Re: Contributing to Wicket - Client side form validation
Jeremy, Since you're digging around in there and if what you wanted to change doesn't already fix this, the yav and yav-examples project have unnecessary dependencies on jmxtools and jms jars (probably from some parent/grand parent POM). Regards - Cemal http://jWeekende.co.uk jWeekend Jeremy Thomerson-5 wrote: Carl, Would you mind if I made a few minor changes to your pom files to make this project conform to the standards of the wicketstuff-core projects? Things I noticed are: - yav-parent/yav/pom.xml - artifact ID must be yav rather than wicketstuff-yav - yav-parent/yav-examples/pom.xml - artifact ID must be yav-examples rather than wicketstuff-yav-examples - add yav-parent to the modules list in wicketstuff-core/pom.xml Thank you, -- Jeremy Thomerson http://www.wickettraining.com On Sun, Jan 18, 2009 at 7:35 AM, cazoury carl.azo...@zenika.com wrote: Hi, I have finally added the Wicket Yav Integration into the trunk of wicketstuff-core. There is an exemple application provided to test the actual Wicket rules that has been converted to Yav Every feedback is the most welcome and contribution also. It is a first step, but we can make it evolve maybe as Cemal suggested to include more advanced validation (like apache validator or Hibernate Validator) Cheers Nino Martinez-2 wrote: ok you should be in... We take jira and CI later.. Ok? Happy new year cazoury wrote: Thank you every one for your answers and interests on the project. I will be very happy for the project to go on Wicketstuff repo. My nick on sourceforge is : cazoury, I will post that on the dev list. Hopefully everything will be checked in before the end of the week. In terms of the actual validation, have you given any thought yet to how this can be done as DRY as possible wrt respecifying (equivalent/similar) validation at various layers including Wicket's, the ORM's, in business rules etc? for the DRY principle we only take into account the validators defined on the form components. Nothing else for the moment. They are some Validators in Wicket that are not available in YAV and the contrary. Maybe a next step will be to add them on the YAV side so all the default Wicket validators can be taken into account. But first, the checkin of the code :) Nino Martinez-2 wrote: I like to keep my contributions in wicketstuff repo, and I think us wicketstuffers would be happy to have your project there .. But no matter what I think you should contribute the stuff you've done :) So if you want, just post your sourceforge nick to the dev list to get write permissions.. And I think your project should go into wicketstuff core, but jeremy can fill you in on that :) cazoury wrote: Hi, We have been working on a small project to integrate http://yav.sourceforge.net/ YAV library with Wicket. It is javascript validation purely on the client side. YAV has a LGPL licence and is a sourceforge project. I know that we can use an Ajax Behavior to validate the form with the validators present on the server side, but this is to respond to one of our client needs and also to illustrate how easy it is to integrate an existing javascript library with Wicket. It has also some nice features like using in the javascript validation the same messages as the ones used by the Wicket application (default messages and user defined messages) We would like to contribute, if possible, this code (wicket-contrib / wicket-stuff) if people finds this interesting. But I am not sure what are the different steps for that. We where thinking making it a sourceforge or googlecode project, maybe it is the first step and then I could post the link to it on this forum. Everyone enjoy the last day(s) of this year :) Carl Azoury - 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 -- View this message in context: http://www.nabble.com/Contributing-to-Wicket---Client-side-form-validation-tp21219136p21527885.html Sent from the Wicket - User 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 -- View this message in context: http://www.nabble.com/Contributing-to-Wicket---Client-side-form-validation-tp21219136p21547407.html Sent from the Wicket - User mailing list archive at Nabble.com.
Re: Contributing to Wicket - Client side form validation
Hi, I have finally added the Wicket Yav Integration into the trunk of wicketstuff-core. There is an exemple application provided to test the actual Wicket rules that has been converted to Yav Every feedback is the most welcome and contribution also. It is a first step, but we can make it evolve maybe as Cemal suggested to include more advanced validation (like apache validator or Hibernate Validator) Cheers Nino Martinez-2 wrote: ok you should be in... We take jira and CI later.. Ok? Happy new year cazoury wrote: Thank you every one for your answers and interests on the project. I will be very happy for the project to go on Wicketstuff repo. My nick on sourceforge is : cazoury, I will post that on the dev list. Hopefully everything will be checked in before the end of the week. In terms of the actual validation, have you given any thought yet to how this can be done as DRY as possible wrt respecifying (equivalent/similar) validation at various layers including Wicket's, the ORM's, in business rules etc? for the DRY principle we only take into account the validators defined on the form components. Nothing else for the moment. They are some Validators in Wicket that are not available in YAV and the contrary. Maybe a next step will be to add them on the YAV side so all the default Wicket validators can be taken into account. But first, the checkin of the code :) Nino Martinez-2 wrote: I like to keep my contributions in wicketstuff repo, and I think us wicketstuffers would be happy to have your project there .. But no matter what I think you should contribute the stuff you've done :) So if you want, just post your sourceforge nick to the dev list to get write permissions.. And I think your project should go into wicketstuff core, but jeremy can fill you in on that :) cazoury wrote: Hi, We have been working on a small project to integrate http://yav.sourceforge.net/ YAV library with Wicket. It is javascript validation purely on the client side. YAV has a LGPL licence and is a sourceforge project. I know that we can use an Ajax Behavior to validate the form with the validators present on the server side, but this is to respond to one of our client needs and also to illustrate how easy it is to integrate an existing javascript library with Wicket. It has also some nice features like using in the javascript validation the same messages as the ones used by the Wicket application (default messages and user defined messages) We would like to contribute, if possible, this code (wicket-contrib / wicket-stuff) if people finds this interesting. But I am not sure what are the different steps for that. We where thinking making it a sourceforge or googlecode project, maybe it is the first step and then I could post the link to it on this forum. Everyone enjoy the last day(s) of this year :) Carl Azoury - 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 -- View this message in context: http://www.nabble.com/Contributing-to-Wicket---Client-side-form-validation-tp21219136p21527885.html Sent from the Wicket - User 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: Contributing to Wicket - Client side form validation
Carl, Would you mind if I made a few minor changes to your pom files to make this project conform to the standards of the wicketstuff-core projects? Things I noticed are: - yav-parent/yav/pom.xml - artifact ID must be yav rather than wicketstuff-yav - yav-parent/yav-examples/pom.xml - artifact ID must be yav-examples rather than wicketstuff-yav-examples - add yav-parent to the modules list in wicketstuff-core/pom.xml Thank you, -- Jeremy Thomerson http://www.wickettraining.com On Sun, Jan 18, 2009 at 7:35 AM, cazoury carl.azo...@zenika.com wrote: Hi, I have finally added the Wicket Yav Integration into the trunk of wicketstuff-core. There is an exemple application provided to test the actual Wicket rules that has been converted to Yav Every feedback is the most welcome and contribution also. It is a first step, but we can make it evolve maybe as Cemal suggested to include more advanced validation (like apache validator or Hibernate Validator) Cheers Nino Martinez-2 wrote: ok you should be in... We take jira and CI later.. Ok? Happy new year cazoury wrote: Thank you every one for your answers and interests on the project. I will be very happy for the project to go on Wicketstuff repo. My nick on sourceforge is : cazoury, I will post that on the dev list. Hopefully everything will be checked in before the end of the week. In terms of the actual validation, have you given any thought yet to how this can be done as DRY as possible wrt respecifying (equivalent/similar) validation at various layers including Wicket's, the ORM's, in business rules etc? for the DRY principle we only take into account the validators defined on the form components. Nothing else for the moment. They are some Validators in Wicket that are not available in YAV and the contrary. Maybe a next step will be to add them on the YAV side so all the default Wicket validators can be taken into account. But first, the checkin of the code :) Nino Martinez-2 wrote: I like to keep my contributions in wicketstuff repo, and I think us wicketstuffers would be happy to have your project there .. But no matter what I think you should contribute the stuff you've done :) So if you want, just post your sourceforge nick to the dev list to get write permissions.. And I think your project should go into wicketstuff core, but jeremy can fill you in on that :) cazoury wrote: Hi, We have been working on a small project to integrate http://yav.sourceforge.net/ YAV library with Wicket. It is javascript validation purely on the client side. YAV has a LGPL licence and is a sourceforge project. I know that we can use an Ajax Behavior to validate the form with the validators present on the server side, but this is to respond to one of our client needs and also to illustrate how easy it is to integrate an existing javascript library with Wicket. It has also some nice features like using in the javascript validation the same messages as the ones used by the Wicket application (default messages and user defined messages) We would like to contribute, if possible, this code (wicket-contrib / wicket-stuff) if people finds this interesting. But I am not sure what are the different steps for that. We where thinking making it a sourceforge or googlecode project, maybe it is the first step and then I could post the link to it on this forum. Everyone enjoy the last day(s) of this year :) Carl Azoury - 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 -- View this message in context: http://www.nabble.com/Contributing-to-Wicket---Client-side-form-validation-tp21219136p21527885.html Sent from the Wicket - User 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: Contributing to Wicket - Client side form validation
ok you should be in... We take jira and CI later.. Ok? Happy new year cazoury wrote: Thank you every one for your answers and interests on the project. I will be very happy for the project to go on Wicketstuff repo. My nick on sourceforge is : cazoury, I will post that on the dev list. Hopefully everything will be checked in before the end of the week. In terms of the actual validation, have you given any thought yet to how this can be done as DRY as possible wrt respecifying (equivalent/similar) validation at various layers including Wicket's, the ORM's, in business rules etc? for the DRY principle we only take into account the validators defined on the form components. Nothing else for the moment. They are some Validators in Wicket that are not available in YAV and the contrary. Maybe a next step will be to add them on the YAV side so all the default Wicket validators can be taken into account. But first, the checkin of the code :) Nino Martinez-2 wrote: I like to keep my contributions in wicketstuff repo, and I think us wicketstuffers would be happy to have your project there .. But no matter what I think you should contribute the stuff you've done :) So if you want, just post your sourceforge nick to the dev list to get write permissions.. And I think your project should go into wicketstuff core, but jeremy can fill you in on that :) cazoury wrote: Hi, We have been working on a small project to integrate http://yav.sourceforge.net/ YAV library with Wicket. It is javascript validation purely on the client side. YAV has a LGPL licence and is a sourceforge project. I know that we can use an Ajax Behavior to validate the form with the validators present on the server side, but this is to respond to one of our client needs and also to illustrate how easy it is to integrate an existing javascript library with Wicket. It has also some nice features like using in the javascript validation the same messages as the ones used by the Wicket application (default messages and user defined messages) We would like to contribute, if possible, this code (wicket-contrib / wicket-stuff) if people finds this interesting. But I am not sure what are the different steps for that. We where thinking making it a sourceforge or googlecode project, maybe it is the first step and then I could post the link to it on this forum. Everyone enjoy the last day(s) of this year :) Carl Azoury - 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: Contributing to Wicket - Client side form validation
Carl, This addresses a question that comes up on this list from time to time and knowing some of the people at Zenika you have probably developed this with, I am sure it will be a well thought out, robust and useful tool. It hopefully also gives us a pretext on which to get you over to London again for another talk at one of our upcoming London Wicket events! In terms of the actual validation, have you given any thought yet to how this can be done as DRY as possible wrt respecifying (equivalent/similar) validation at various layers including Wicket's, the ORM's, in business rules etc? Regards - Cemal http://www.jWeekend.co.uk jWeekend cazoury wrote: Hi, We have been working on a small project to integrate http://yav.sourceforge.net/ YAV library with Wicket. It is javascript validation purely on the client side. YAV has a LGPL licence and is a sourceforge project. I know that we can use an Ajax Behavior to validate the form with the validators present on the server side, but this is to respond to one of our client needs and also to illustrate how easy it is to integrate an existing javascript library with Wicket. It has also some nice features like using in the javascript validation the same messages as the ones used by the Wicket application (default messages and user defined messages) We would like to contribute, if possible, this code (wicket-contrib / wicket-stuff) if people finds this interesting. But I am not sure what are the different steps for that. We where thinking making it a sourceforge or googlecode project, maybe it is the first step and then I could post the link to it on this forum. Everyone enjoy the last day(s) of this year :) Carl Azoury -- View this message in context: http://www.nabble.com/Contributing-to-Wicket---Client-side-form-validation-tp21219136p21219589.html Sent from the Wicket - User 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: Contributing to Wicket - Client side form validation
Carl, I think this project is very interesting. I was recently investigating on client side validation with wicket and could not find any pure client-side solution. I will be waiting for your link... David On Wed, Dec 31, 2008 at 12:10 PM, jWeekend jweekend_for...@cabouge.comwrote: Carl, This addresses a question that comes up on this list from time to time and knowing some of the people at Zenika you have probably developed this with, I am sure it will be a well thought out, robust and useful tool. It hopefully also gives us a pretext on which to get you over to London again for another talk at one of our upcoming London Wicket events! In terms of the actual validation, have you given any thought yet to how this can be done as DRY as possible wrt respecifying (equivalent/similar) validation at various layers including Wicket's, the ORM's, in business rules etc? Regards - Cemal http://www.jWeekend.co.uk jWeekend cazoury wrote: Hi, We have been working on a small project to integrate http://yav.sourceforge.net/ YAV library with Wicket. It is javascript validation purely on the client side. YAV has a LGPL licence and is a sourceforge project. I know that we can use an Ajax Behavior to validate the form with the validators present on the server side, but this is to respond to one of our client needs and also to illustrate how easy it is to integrate an existing javascript library with Wicket. It has also some nice features like using in the javascript validation the same messages as the ones used by the Wicket application (default messages and user defined messages) We would like to contribute, if possible, this code (wicket-contrib / wicket-stuff) if people finds this interesting. But I am not sure what are the different steps for that. We where thinking making it a sourceforge or googlecode project, maybe it is the first step and then I could post the link to it on this forum. Everyone enjoy the last day(s) of this year :) Carl Azoury -- View this message in context: http://www.nabble.com/Contributing-to-Wicket---Client-side-form-validation-tp21219136p21219589.html Sent from the Wicket - User 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: Contributing to Wicket - Client side form validation
Hi Carl, Yeah, Pure Javascript validation is something needed. I've been trying to integrate wicket with yav a couple of days ago . I think you contribution will be very interesting. Googlecode project is a good step. Azarias Tomás 2008/12/30 cazoury carl.azo...@zenika.com -- AT(R)
Re: Contributing to Wicket - Client side form validation
I like to keep my contributions in wicketstuff repo, and I think us wicketstuffers would be happy to have your project there .. But no matter what I think you should contribute the stuff you've done :) So if you want, just post your sourceforge nick to the dev list to get write permissions.. And I think your project should go into wicketstuff core, but jeremy can fill you in on that :) cazoury wrote: Hi, We have been working on a small project to integrate http://yav.sourceforge.net/ YAV library with Wicket. It is javascript validation purely on the client side. YAV has a LGPL licence and is a sourceforge project. I know that we can use an Ajax Behavior to validate the form with the validators present on the server side, but this is to respond to one of our client needs and also to illustrate how easy it is to integrate an existing javascript library with Wicket. It has also some nice features like using in the javascript validation the same messages as the ones used by the Wicket application (default messages and user defined messages) We would like to contribute, if possible, this code (wicket-contrib / wicket-stuff) if people finds this interesting. But I am not sure what are the different steps for that. We where thinking making it a sourceforge or googlecode project, maybe it is the first step and then I could post the link to it on this forum. Everyone enjoy the last day(s) of this year :) Carl Azoury - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Contributing to Wicket - Client side form validation
Thank you every one for your answers and interests on the project. I will be very happy for the project to go on Wicketstuff repo. My nick on sourceforge is : cazoury, I will post that on the dev list. Hopefully everything will be checked in before the end of the week. In terms of the actual validation, have you given any thought yet to how this can be done as DRY as possible wrt respecifying (equivalent/similar) validation at various layers including Wicket's, the ORM's, in business rules etc? for the DRY principle we only take into account the validators defined on the form components. Nothing else for the moment. They are some Validators in Wicket that are not available in YAV and the contrary. Maybe a next step will be to add them on the YAV side so all the default Wicket validators can be taken into account. But first, the checkin of the code :) Nino Martinez-2 wrote: I like to keep my contributions in wicketstuff repo, and I think us wicketstuffers would be happy to have your project there .. But no matter what I think you should contribute the stuff you've done :) So if you want, just post your sourceforge nick to the dev list to get write permissions.. And I think your project should go into wicketstuff core, but jeremy can fill you in on that :) cazoury wrote: Hi, We have been working on a small project to integrate http://yav.sourceforge.net/ YAV library with Wicket. It is javascript validation purely on the client side. YAV has a LGPL licence and is a sourceforge project. I know that we can use an Ajax Behavior to validate the form with the validators present on the server side, but this is to respond to one of our client needs and also to illustrate how easy it is to integrate an existing javascript library with Wicket. It has also some nice features like using in the javascript validation the same messages as the ones used by the Wicket application (default messages and user defined messages) We would like to contribute, if possible, this code (wicket-contrib / wicket-stuff) if people finds this interesting. But I am not sure what are the different steps for that. We where thinking making it a sourceforge or googlecode project, maybe it is the first step and then I could post the link to it on this forum. Everyone enjoy the last day(s) of this year :) Carl Azoury - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://www.nabble.com/Contributing-to-Wicket---Client-side-form-validation-tp21219136p21223881.html Sent from the Wicket - User 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
