Menu
▾
▴
formproc-developer — Developer interests
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(37) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(37) |
Feb
(18) |
Mar
(33) |
Apr
(8) |
May
(7) |
Jun
(13) |
Jul
(20) |
Aug
|
Sep
|
Oct
(1) |
Nov
(5) |
Dec
(2) |
| 2003 |
Jan
|
Feb
(7) |
Mar
(3) |
Apr
(15) |
May
(7) |
Jun
(6) |
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
| 2004 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
(2) |
Sep
(4) |
Oct
|
Nov
(5) |
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(3) |
Dec
|
|
From: Anthony E. <me...@an...> - 2002-05-23 14:06:01
|
I think that the best approach is to create a new class which extends from the Form class and converts Struts form beans to FormData objects and then submits that data to the parent Form class. The FormData class is merely a class which encapsulates a name/value pair. An example of this is the HttpForm ( http://formproc.sourceforge.net/docs/api/org/formproc/servlet/HttpForm.html ) class which converts the parameters of an HttpServletRequest to FormData objects and then passes those FormData objects to the superclass for processing. Sincerely, Anthony Eden > -----Original Message----- > From: for...@li... > [mailto:for...@li...]On Behalf Of > CARDON Denis > Sent: Thursday, May 23, 2002 8:59 AM > To: 'for...@li...' > Subject: [FormProc-developer] bean 2 bean mapping > > > Hi Anthony, > > I have come accross your project recently while looking for is a framework > to map properties between two beans (bean to bean mapping). > First I congratulate you for the great flexibility of this library (bsf > stuff, etc.). It looks like FormProc could be a great tool to map Struts > FormBean (jakarta.apache.org/struts/) to persistence objects. > > However there is a point that bother me : for the moment, it looks like > FormProc input can only be a List of FormData element. If this is the case, > is there any plan to make input plugable like for the Storer stuff? If I > have time to get familiar with FormProc design, I may help. > > If the bean to bean mapping could be integrated into your library, I think > you could gain a lot of support from Struts users who are, like me, tired of > making mapping from FormBean to Business Objects ! > > Regards > > Denis > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > FormProc-developer mailing list > For...@li... > https://lists.sourceforge.net/lists/listinfo/formproc-developer > |
|
From: CARDON D. <De...@CP...> - 2002-05-23 13:03:10
|
Hi Anthony, I have come accross your project recently while looking for is a framework to map properties between two beans (bean to bean mapping). First I congratulate you for the great flexibility of this library (bsf stuff, etc.). It looks like FormProc could be a great tool to map Struts FormBean (jakarta.apache.org/struts/) to persistence objects. However there is a point that bother me : for the moment, it looks like FormProc input can only be a List of FormData element. If this is the case, is there any plan to make input plugable like for the Storer stuff? If I have time to get familiar with FormProc design, I may help. If the bean to bean mapping could be integrated into your library, I think you could gain a lot of support from Struts users who are, like me, tired of making mapping from FormBean to Business Objects ! Regards Denis |
|
From: Anthony E. <me...@an...> - 2002-05-21 14:55:03
|
I have made some modifications to FormProc to better handle null and empty values. - Removed the value == null check in Form.java:353 to allow null values through to the convert() and store() methods. - Null values are skipped in the Form.convert() method, thus bypassing conversion when the value is null. - Updated MapStorer to call map.remove(name) when a null value is passed to the storer. - Updated the EdenLib MethodUtilities class to better handle null values so that the ReflectionStorer works properly. These changes, along with some minor changes to the example code, are in the CVS and will be part of the next release (beta 3). Sincerely, Anthony Eden |
|
From: Anthony E. <me...@an...> - 2002-05-20 17:24:21
|
I am currently working on how FormProc handles empty fields. I have defined empty fields as either being null or being an empty String. Currently FormProc handles empty fields in the following manner: If there is a default value specified in the Form configuration, use that If there is no default value then the FormData.getValue() returns either null or an empty String If validation succeeds and the value is the empty String it is converted and stored If validation succeeds and the value is null, then conversion and storage are skipped The issue at hand is that a null value may actually be a valid argument. For example it might be important for a null value to be stored into the target object (i.e. a field which originally had a value is now empty and thus the target object should be updated to reflect that). However, if null values are passed to converters, then each converter must be able to handle null values. In addition, converters may also want to handle empty Strings as well. So, as I see it we have two options: - Leave things the way they are now. - Allow null values to be passed to converters and storers and expect them to handle null values. Comments and suggestions are welcome. Sincerely, Anthony Eden |
|
From: Anthony E. <me...@an...> - 2002-05-20 17:11:12
|
FormProc version 1.0b2 is now available at http://www.formproc.org/ FormProc is an open source Java library designed to make handling and validating forms easy. Forms are represented as objects which manage a collection of form elements. Submitted data can be validated through several mechanisms including regular expressions, BSF supported scripting languages and custom Java classes. This release includes the following changes: Added pluggable message providers for FormElement messages and validator error messages. Provided two implementations which support previous message types (inline and ResourceBundles). Added support for default values in form elements. If no value is submitted the default value will be used instead. Added annotated configuration files to the documentation. Added comments to DTDs. Added and improved more JavaDoc comments. Updated Guide with new features. Updated Overview. Sincerely, Anthony Eden |
|
From: Anthony E. <me...@an...> - 2002-05-17 18:25:42
|
Greetings all, Here is an update on recent modifications to FormProc. After a little more work I will be releasing FormProc 1.0b2. If there are no more significant issues after that then I will release 1.0. Changes: Added pluggable message providers for FormElement messages and validator error messages. Provided two implementations which support previous message types (inline and ResourceBundles). This pluggability should greatly improve how error messages are provided. Added support for default values in FormElements. If a null or empty String value is submitted then the default value is used instead if it is specified. Added annotated configuration files to the documentation and detailed comments to DTDs. Hopefully this will make it easier to understand the variety of configuration options in FormProc. Comments and suggestions are welcome. Sincerely, Anthony Eden |
|
From: Anthony E. <me...@an...> - 2002-05-17 13:20:40
|
I am preparing to move FormProc to a 1.0 release, and I would like to know if anyone has found any showstoppers which need to be fixed before the production release? This could include bugs, missing documentation, etc. If not, then I will release it within the next couple of days as 1.0. Sincerely, Anthony Eden |
|
From: Anthony E. <ae...@si...> - 2002-04-11 21:56:54
|
FormProc version 1.0b1 is now available at http://www.formproc.org/ FormProc is an open source Java library designed to make handling and validating forms easy. Forms are represented as objects which manage a collection of form elements. Submitted data can be validated through several mechanisms including regular expressions, BSF supported scripting languages and custom Java classes. This release includes the following changes: Improved localization support. Default validator, storer and type can be specified in each form's configuration. TypeConverter.loadConfiguration() and Storer.loadConfiguration() methods are now executed when the TypeConverter or Storer is loaded. Configuration formproc.xml now supports an include tag for including other configuration files. Shared validators are now cloned when FormElements are configured so that overriding works properly. Error and message lang attribute no longer required. Validator error tag and element message tag both support resource bundles. Error and messages which use the inline message form (i.e. the message is defined in the configuration) will fall back to the messages defined without a lang attribute if the given language is not found. For more information please visit http://www.formproc.org/ or contact Anthony Eden [me...@an...]. You can also join the FormProc mailing list at http://lists.sourceforge.net/lists/listinfo/formproc-developer Sincerely, Anthony Eden |
|
From: Anthony E. <me...@an...> - 2002-04-11 16:42:27
|
I have just checked in some changes to FormProc which will hopefully improve the way error messages are specified. I have added support for resource bundles as per the request of Emmanuel Venisse. The new changes allow error and message tags to include a resource attribute which specifies the name of the resource bundle to use. If a resource attribute is specified, then the value of the XML element will be the resource key. Here is an example: <validator type="class" classname="org.formproc.example.UsernameValidator"> <error resource="org.formproc.example.ExampleResourceBundle">username.error</error> </validator> This should work for both error messages and form element messages. The old system for specifying error messages in the configuration will also work if no resource bundle is specified. I have also updated this to allow a error or message with no lang attribute. If specified this value will be used if there is no error or message for the specified locale. As always, comments and questions are welcome. Sincerely, Anthony Eden |
|
From: <sim...@fr...> - 2002-04-10 13:57:21
|
Hello. I'm a french Student and i try to use jakarta-oro perhaps could you help me ??? I want to match the end of an sentance in a text file. But the end is given by the chracters ", it is also the end-character of a string in JAVA. So i can't put it in my regexp, it end the regexp without doing what i want. How would my regexp recognize this character ? Do you have an idea to help me to do that ? Thanks |
|
From: Anthony E. <me...@an...> - 2002-04-08 20:59:34
|
> -----Original Message----- > From: for...@li... > [mailto:for...@li...]On Behalf Of > Emmanuel Venisse > Sent: Monday, April 08, 2002 4:14 AM > To: for...@li... > Subject: [FormProc-developer] Feature requests > > > I've add two feature requests for formproc : > - an include tag for cut big files This feature is now in the CVS. I have modified the example applications to demonstrate the use of this feature. Sincerely, Anthony Eden |
|
From: Anthony E. <me...@an...> - 2002-04-08 11:24:48
|
Yes, I am going to put these features in prior to the next release. Sincerely, Anthony Eden > -----Original Message----- > From: for...@li...=20 > [mailto:for...@li...] On=20 > Behalf Of Emmanuel Venisse > Sent: Monday, April 08, 2002 4:14 AM > To: for...@li... > Subject: [FormProc-developer] Feature requests >=20 >=20 > I've add two feature requests for formproc : > - an include tag for cut big files > - attribute resource for error tag >=20 > Would it be possible to have these modifications in the next release? >=20 >=20 > thanks > Emmanuel Venisse >=20 > ___________________________________________________________ > Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en=20 > fran=E7ais ! Yahoo! Mail : http://fr.mail.yahoo.com >=20 > _______________________________________________ > FormProc-developer mailing list=20 > For...@li... > https://lists.sourceforge.net/lists/listinfo/formproc-developer >=20 |
|
From: <eve...@ya...> - 2002-04-08 08:13:38
|
I've add two feature requests for formproc : - an include tag for cut big files - attribute resource for error tag Would it be possible to have these modifications in the next release? thanks Emmanuel Venisse ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com |
|
From: Anthony E. <me...@an...> - 2002-04-02 14:28:44
|
This is because you have two validators as a child for an element. An element can only have one validator. If you want
to have multiple validators for a single element then you will need to use a validator group:
<element name="birth_year">
<validator type="group">
<validator type="shared" name="year"/>
<validator type="rule">
<rule>my.form.BirthYearRule</rule>
<error lang="en">Must be a valid birth year</error>
</validator>
</validator>
<message lang="en">Birth year must be 4 digits</message>
<write-method>setBirthYear</write-method>
</element>
Sincerely,
Anthony Eden
> -----Original Message-----
> From: for...@li...
> [mailto:for...@li...]On Behalf Of
> ek...@co...
> Sent: Monday, April 01, 2002 7:29 PM
> To: for...@li...
> Subject: [FormProc-developer] shared-validator and rules
>
>
> I seem to be running into problems when I used a shared validator with a
> rule. For example: the following works:
>
> <element name="birth_year">
> <validator type="rule">
> <rule>my.form.BirthYearRule</rule>
> <error lang="en">Must be a valid birth year</error>
> </validator>
> <message lang="en">Birth year must be 4 digits</message>
> <write-method>setBirthYear</write-method>
> </element>
>
> But if I add a shared validator:
>
> <element name="birth_year">
> <validator type="shared" name="year"/> <!-- *NEW* -->
> <validator type="rule">
> <rule>my.form.BirthYearRule</rule>
> <error lang="en">Must be a valid birth year</error>
> </validator>
> <message lang="en">Birth year must be 4 digits</message>
> <write-method>setBirthYear</write-method>
> </element>
>
> The rule is never called. Can someone try and duplicate this?
>
> thanks,
> --eric
>
> _______________________________________________
> FormProc-developer mailing list
> For...@li...
> https://lists.sourceforge.net/lists/listinfo/formproc-developer
>
|
|
From: <ek...@co...> - 2002-04-02 00:29:40
|
I seem to be running into problems when I used a shared validator with a
rule. For example: the following works:
<element name="birth_year">
<validator type="rule">
<rule>my.form.BirthYearRule</rule>
<error lang="en">Must be a valid birth year</error>
</validator>
<message lang="en">Birth year must be 4 digits</message>
<write-method>setBirthYear</write-method>
</element>
But if I add a shared validator:
<element name="birth_year">
<validator type="shared" name="year"/> <!-- *NEW* -->
<validator type="rule">
<rule>my.form.BirthYearRule</rule>
<error lang="en">Must be a valid birth year</error>
</validator>
<message lang="en">Birth year must be 4 digits</message>
<write-method>setBirthYear</write-method>
</element>
The rule is never called. Can someone try and duplicate this?
thanks,
--eric
|
|
From: Anthony E. <me...@an...> - 2002-03-27 20:13:45
|
> -----Original Message----- > From: Nick Bauman [mailto:ni...@co...] > Sent: Wednesday, March 27, 2002 2:38 PM > To: me...@an... > Subject: RE: [FormProc-developer] Changes for Localization support > > > > > > > >> -----Original Message----- > >> From: Nick Bauman [mailto:ni...@co...] > >> Sent: Wednesday, March 27, 2002 2:06 PM > >> To: me...@an... > >> Subject: Re: [FormProc-developer] Changes for Localization support > >> > >> > >> Anthony, > >> > >> I did the Locale thing in Integradata a while back. What made you > >> think of it / want to do it now? > > > > A desire to solidify the API prior to going to version 1.0. > > That seems vague. OK, how about this: I am responding to developer needs. The choice to do it now rather than later is because I want to lock in the API before 1.0. Is that less vague? > > > BTW - Does this mean that the Rule interface should be changed to the > > folowing: > > > > public RuleResult validate(Object value, Locale locale); > > I think that's how I have it. > > http://www.cortexity.com/cgi- > py/viewcvs.cgi/integradata/src/com/cortexity/integradata/rules/Rule.java? > rev=1.9&content-type=text/vnd.viewcvs-markup > > I see it as an Integradata Rule to FormProc is just another Validator. I have modified the CVS to reflect the Rule interface change. > >> > >> > Greetings all, > >> > > >> > I have just checked in some changes to the CVS server which modify > >> > the Validator and Storer interfaces so that validate() and store() > >> > methods now include a Locale object. If you have written any > >> > Validator or Storer implementations in Java then they will need to > >> > be modified to support this change. I have already modified all of > >> > the built in validators to handle this change. > >> > > >> > I am trying to get all of these API-breaking changes in prior to > >> > going to 1.0. The next release will be a 1.0 beta release, so get > >> > your changes in now if you think that it will break the API. > >> > > >> > In addition to the change above, the ValidationResult class now > >> > includes a getLocale() method which returns the Locale which was > >> > used during the validation. Right now the > >> > ValidationResult.getErrorMessage() method uses the value of > >> > Locale.getDefault() if you do not specify the Locale as an argument > >> > to the getErrorMessage() method. Do you think this should be > >> > changed so it uses the locale used during validation and then falls > >> > back to the Locale.getDefault() as a last resort? The > >> > getErrorMessage(Locale > >> > >> > >> Yes, always. I have no idea why you'd want it any other way. > > > > It was the other way before because the VaidatorResult did not know the > > Locale which was used during validation because that information was > > not being passed to the validator. I have modified the CVS for this change as well. Sincerely, Anthony Eden |
|
From: Anthony E. <me...@an...> - 2002-03-27 19:55:04
|
> -----Original Message----- > From: Nick Bauman [mailto:ni...@co...] > Sent: Wednesday, March 27, 2002 2:06 PM > To: me...@an... > Subject: Re: [FormProc-developer] Changes for Localization support > > > Anthony, > > I did the Locale thing in Integradata a while back. What made you think of > it / want to do it now? A desire to solidify the API prior to going to version 1.0. BTW - Does this mean that the Rule interface should be changed to the folowing: public RuleResult validate(Object value, Locale locale); > > > Greetings all, > > > > I have just checked in some changes to the CVS server which modify the > > Validator and Storer interfaces so that validate() and store() methods > > now include a Locale object. If you have written any Validator or > > Storer implementations in Java then they will need to be modified to > > support this change. I have already modified all of the built in > > validators to handle this change. > > > > I am trying to get all of these API-breaking changes in prior to going > > to 1.0. The next release will be a 1.0 beta release, so get your > > changes in now if you think that it will break the API. > > > > In addition to the change above, the ValidationResult class now > > includes a getLocale() method which returns the Locale which was used > > during the validation. Right now the > > ValidationResult.getErrorMessage() method uses the value of > > Locale.getDefault() if you do not specify the Locale as an argument to > > the getErrorMessage() method. Do you think this should be changed so > > it uses the locale used during validation and then falls back to the > > Locale.getDefault() as a last resort? The getErrorMessage(Locale > > > Yes, always. I have no idea why you'd want it any other way. It was the other way before because the VaidatorResult did not know the Locale which was used during validation because that information was not being passed to the validator. Sincerely, Anthony Eden |
|
From: Anthony E. <me...@an...> - 2002-03-27 18:27:38
|
Greetings all, I have just checked in some changes to the CVS server which modify the Validator and Storer interfaces so that validate() and store() methods now include a Locale object. If you have written any Validator or Storer implementations in Java then they will need to be modified to support this change. I have already modified all of the built in validators to handle this change. I am trying to get all of these API-breaking changes in prior to going to 1.0. The next release will be a 1.0 beta release, so get your changes in now if you think that it will break the API. In addition to the change above, the ValidationResult class now includes a getLocale() method which returns the Locale which was used during the validation. Right now the ValidationResult.getErrorMessage() method uses the value of Locale.getDefault() if you do not specify the Locale as an argument to the getErrorMessage() method. Do you think this should be changed so it uses the locale used during validation and then falls back to the Locale.getDefault() as a last resort? The getErrorMessage(Locale locale) version will of course remain the same and can always be used to explicitly specify the error message locale to use. Sincerely, Anthony Eden |
|
From: Anthony E. <me...@an...> - 2002-03-22 17:19:59
|
I just tested this against both version 0.9 and the current CVS revision and it works fine. I was able to override the error message specified in the shared validator without any problems. Do you have the current version or the current CVS revision? Sincerely, Anthony Eden > -----Original Message----- > From: for...@li... > [mailto:for...@li...] On > Behalf Of Eric Kolve > Sent: Wednesday, March 20, 2002 11:14 AM > To: for...@li... > Subject: [FormProc-developer] shared-validator and error messages > > > I ran into a small problem when trying to use a different > error message for a shared-validator. I did something like: > > <shared-validator name="username"> > <validator type="class" > classname="org.formproc.example.UsernameValidator"> > <error lang="en">Username must be more than 4 characters</error> > </validator> > </shared-validator> > > <element name="username"> > <validator type="shared" name="username"> > <error lang="en">Your XXXX Username must be more than 4 > characters</error> > </validator> > <message lang="en">5 characters or more.</message> > </element> > > Basically, I want to be able to override the shared error > message. Is this possible? > > thanks, > > --eric > > _______________________________________________ > FormProc-developer mailing list > For...@li... > https://lists.sourceforge.net/lists/listinfo/formproc-developer > |
|
From: Dan B. <da...@ch...> - 2002-03-22 16:26:57
|
even better... thanks again!
On Fri, 2002-03-22 at 11:10, Anthony Eden wrote:
> The problem is fixed now...actually I had it fixed yesterday but I
> didn=92t get a chance to send out a message (even though I thought I
> did...go figure).
>=20
> Sincerely,
> Anthony Eden
>=20
> > -----Original Message-----
> > From: for...@li...=20
> > [mailto:for...@li...] On=20
> > Behalf Of Dan Bachelder
> > Sent: Friday, March 22, 2002 10:58 AM
> > To: for...@li...
> > Subject: RE: [FormProc-developer] REValidator
> >=20
> >=20
> > thanks!
> >=20
> > On Thu, 2002-03-21 at 13:35, Anthony Eden wrote:
> > > Yes, I see that there is a problem...I am troubleshooting=20
> > it now and=20
> > > will let you know when the fix is in the CVS.
> > >=20
> > > -Anthony
> > >=20
> > > > -----Original Message-----
> > > > From: for...@li...
> > > > [mailto:for...@li...] On=20
> > > > Behalf Of Dan Bachelder
> > > > Sent: Tuesday, March 19, 2002 3:36 PM
> > > > To: FormProc Developer List
> > > > Subject: [FormProc-developer] REValidator
> > > >=20
> > > >=20
> > > > REValidator doesn't appear to be working the way it used to...
> > > >=20
> > > > I have the following:
> > > >=20
> > > > ------ formproc.xml ---------
> > > >=20
> > > > <shared-validator name=3D"notempty">
> > > > <validator type=3D"expression">
> > > > <pattern>.{1,}</pattern>
> > > > <error lang=3D"en">Field must not be empty</error>
> > > > </validator>
> > > > </shared-validator>
> > > >=20
> > > > ------ userform.xml ---------
> > > >=20
> > > > <element name=3D"username">
> > > > <validator type=3D"shared" name=3D"notempty"/>
> > > > <message lang=3D"en">username must not be empty.</message>
> > > > </element>
> > > >=20
> > > >=20
> > > > ------ my log -------------
> > > >=20
> > > > [DEBUG]:org.formproc.validation.REValidator - Validating form
> > > > data username with value of test=20
> > > > [DEBUG]:org.formproc.validation.REValidator - The pattern is:=20
> > > > [DEBUG]:org.formproc.validation.REValidator - Form data value=20
> > > > NOT matched.
> > > >=20
> > > >=20
> > > > so.. REValidator doesn't seem to have my expression in it...
> > > > is my configuration wrong?
> > > >=20
> > > > thanks,
> > > > dan
> > > >=20
> > > >=20
> > > >=20
> > > > _______________________________________________
> > > > FormProc-developer mailing list
> > > > For...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/formproc-developer
> > > >=20
> > >=20
> > >=20
> > > _______________________________________________
> > > FormProc-developer mailing list=20
> > > For...@li...
> > > https://lists.sourceforge.net/lists/listinfo/formproc-developer
> > >=20
> >=20
> >=20
> >=20
> > _______________________________________________
> > FormProc-developer mailing list=20
> > For...@li...
> > https://lists.sourceforge.net/lists/listinfo/formproc-developer
> >=20
>=20
>=20
> _______________________________________________
> FormProc-developer mailing list
> For...@li...
> https://lists.sourceforge.net/lists/listinfo/formproc-developer
>=20
|
|
From: Anthony E. <me...@an...> - 2002-03-22 16:13:10
|
The problem is fixed now...actually I had it fixed yesterday but I
didn=92t get a chance to send out a message (even though I thought I
did...go figure).
Sincerely,
Anthony Eden
> -----Original Message-----
> From: for...@li...=20
> [mailto:for...@li...] On=20
> Behalf Of Dan Bachelder
> Sent: Friday, March 22, 2002 10:58 AM
> To: for...@li...
> Subject: RE: [FormProc-developer] REValidator
>=20
>=20
> thanks!
>=20
> On Thu, 2002-03-21 at 13:35, Anthony Eden wrote:
> > Yes, I see that there is a problem...I am troubleshooting=20
> it now and=20
> > will let you know when the fix is in the CVS.
> >=20
> > -Anthony
> >=20
> > > -----Original Message-----
> > > From: for...@li...
> > > [mailto:for...@li...] On=20
> > > Behalf Of Dan Bachelder
> > > Sent: Tuesday, March 19, 2002 3:36 PM
> > > To: FormProc Developer List
> > > Subject: [FormProc-developer] REValidator
> > >=20
> > >=20
> > > REValidator doesn't appear to be working the way it used to...
> > >=20
> > > I have the following:
> > >=20
> > > ------ formproc.xml ---------
> > >=20
> > > <shared-validator name=3D"notempty">
> > > <validator type=3D"expression">
> > > <pattern>.{1,}</pattern>
> > > <error lang=3D"en">Field must not be empty</error>
> > > </validator>
> > > </shared-validator>
> > >=20
> > > ------ userform.xml ---------
> > >=20
> > > <element name=3D"username">
> > > <validator type=3D"shared" name=3D"notempty"/>
> > > <message lang=3D"en">username must not be empty.</message>
> > > </element>
> > >=20
> > >=20
> > > ------ my log -------------
> > >=20
> > > [DEBUG]:org.formproc.validation.REValidator - Validating form
> > > data username with value of test=20
> > > [DEBUG]:org.formproc.validation.REValidator - The pattern is:=20
> > > [DEBUG]:org.formproc.validation.REValidator - Form data value=20
> > > NOT matched.
> > >=20
> > >=20
> > > so.. REValidator doesn't seem to have my expression in it...
> > > is my configuration wrong?
> > >=20
> > > thanks,
> > > dan
> > >=20
> > >=20
> > >=20
> > > _______________________________________________
> > > FormProc-developer mailing list
> > > For...@li...
> > > https://lists.sourceforge.net/lists/listinfo/formproc-developer
> > >=20
> >=20
> >=20
> > _______________________________________________
> > FormProc-developer mailing list=20
> > For...@li...
> > https://lists.sourceforge.net/lists/listinfo/formproc-developer
> >=20
>=20
>=20
>=20
> _______________________________________________
> FormProc-developer mailing list=20
> For...@li...
> https://lists.sourceforge.net/lists/listinfo/formproc-developer
>=20
|
|
From: Dan B. <da...@ch...> - 2002-03-22 15:58:24
|
thanks!
On Thu, 2002-03-21 at 13:35, Anthony Eden wrote:
> Yes, I see that there is a problem...I am troubleshooting it now and
> will let you know when the fix is in the CVS.
>
> -Anthony
>
> > -----Original Message-----
> > From: for...@li...
> > [mailto:for...@li...] On
> > Behalf Of Dan Bachelder
> > Sent: Tuesday, March 19, 2002 3:36 PM
> > To: FormProc Developer List
> > Subject: [FormProc-developer] REValidator
> >
> >
> > REValidator doesn't appear to be working the way it used to...
> >
> > I have the following:
> >
> > ------ formproc.xml ---------
> >
> > <shared-validator name="notempty">
> > <validator type="expression">
> > <pattern>.{1,}</pattern>
> > <error lang="en">Field must not be empty</error>
> > </validator>
> > </shared-validator>
> >
> > ------ userform.xml ---------
> >
> > <element name="username">
> > <validator type="shared" name="notempty"/>
> > <message lang="en">username must not be empty.</message>
> > </element>
> >
> >
> > ------ my log -------------
> >
> > [DEBUG]:org.formproc.validation.REValidator - Validating form
> > data username with value of test
> > [DEBUG]:org.formproc.validation.REValidator - The pattern is:
> > [DEBUG]:org.formproc.validation.REValidator - Form data value
> > NOT matched.
> >
> >
> > so.. REValidator doesn't seem to have my expression in it...
> > is my configuration wrong?
> >
> > thanks,
> > dan
> >
> >
> >
> > _______________________________________________
> > FormProc-developer mailing list
> > For...@li...
> > https://lists.sourceforge.net/lists/listinfo/formproc-developer
> >
>
>
> _______________________________________________
> FormProc-developer mailing list
> For...@li...
> https://lists.sourceforge.net/lists/listinfo/formproc-developer
>
|
|
From: Anthony E. <me...@an...> - 2002-03-21 18:38:13
|
Yes, I see that there is a problem...I am troubleshooting it now and
will let you know when the fix is in the CVS.
-Anthony
> -----Original Message-----
> From: for...@li...
> [mailto:for...@li...] On
> Behalf Of Dan Bachelder
> Sent: Tuesday, March 19, 2002 3:36 PM
> To: FormProc Developer List
> Subject: [FormProc-developer] REValidator
>
>
> REValidator doesn't appear to be working the way it used to...
>
> I have the following:
>
> ------ formproc.xml ---------
>
> <shared-validator name="notempty">
> <validator type="expression">
> <pattern>.{1,}</pattern>
> <error lang="en">Field must not be empty</error>
> </validator>
> </shared-validator>
>
> ------ userform.xml ---------
>
> <element name="username">
> <validator type="shared" name="notempty"/>
> <message lang="en">username must not be empty.</message>
> </element>
>
>
> ------ my log -------------
>
> [DEBUG]:org.formproc.validation.REValidator - Validating form
> data username with value of test
> [DEBUG]:org.formproc.validation.REValidator - The pattern is:
> [DEBUG]:org.formproc.validation.REValidator - Form data value
> NOT matched.
>
>
> so.. REValidator doesn't seem to have my expression in it...
> is my configuration wrong?
>
> thanks,
> dan
>
>
>
> _______________________________________________
> FormProc-developer mailing list
> For...@li...
> https://lists.sourceforge.net/lists/listinfo/formproc-developer
>
|
|
From: Anthony E. <me...@an...> - 2002-03-21 18:18:18
|
Right now error messages from shared validators can not be overridden. I will add that feature in the next release (which will be a beta release). Sincerely, Anthony Eden > -----Original Message----- > From: for...@li... > [mailto:for...@li...] On > Behalf Of Eric Kolve > Sent: Wednesday, March 20, 2002 11:14 AM > To: for...@li... > Subject: [FormProc-developer] shared-validator and error messages > > > I ran into a small problem when trying to use a different > error message for a shared-validator. I did something like: > > <shared-validator name="username"> > <validator type="class" > classname="org.formproc.example.UsernameValidator"> > <error lang="en">Username must be more than 4 characters</error> > </validator> > </shared-validator> > > <element name="username"> > <validator type="shared" name="username"> > <error lang="en">Your XXXX Username must be more than 4 > characters</error> > </validator> > <message lang="en">5 characters or more.</message> > </element> > > Basically, I want to be able to override the shared error > message. Is this possible? > > thanks, > > --eric > > _______________________________________________ > FormProc-developer mailing list > For...@li... > https://lists.sourceforge.net/lists/listinfo/formproc-developer > |
|
From: Eric K. <ek...@co...> - 2002-03-20 16:14:37
|
I ran into a small problem when trying to use a different error message
for a shared-validator. I did something like:
<shared-validator name="username">
<validator type="class"
classname="org.formproc.example.UsernameValidator">
<error lang="en">Username must be more than 4 characters</error>
</validator>
</shared-validator>
<element name="username">
<validator type="shared" name="username">
<error lang="en">Your XXXX Username must be more than 4
characters</error>
</validator>
<message lang="en">5 characters or more.</message>
</element>
Basically, I want to be able to override the shared error message. Is
this possible?
thanks,
--eric
|
2 messages has been excluded from this view by a project administrator.
