svn commit: rev 56595 - struts/trunk/doc/userGuide
Author: husted Date: Thu Nov 4 06:39:48 2004 New Revision: 56595 Modified: struts/trunk/doc/userGuide/dev_validator.xml Log: Clarify which Validator configuration file is which, and why there is more than one. When refering to an object loaded by the validator element, prefer the term validator to rule or action. Modified: struts/trunk/doc/userGuide/dev_validator.xml == --- struts/trunk/doc/userGuide/dev_validator.xml(original) +++ struts/trunk/doc/userGuide/dev_validator.xmlThu Nov 4 06:39:48 2004 @@ -40,25 +40,26 @@ codeorg.apache.struts.validator.action.ValidatorForm/code instead of codeorg.apache.struts.action.ActionForm/code. Then when the codevalidate/code method is called, the action's name -attribute from the struts-config.xml is used to load the validations for +attribute from the Struts Configuration is used to load the validations for the current form. -So the form element's codename/code attribute in the -validator-rules.xml should match action element's codename/code +The form element's codename/code attribute in the +Validator configuration should match the action element's codename/code attribute. /p p -Another alternative is to use the action mapping you are currently on by -extending the ValidatorActionForm instead of the ValidatorForm. +An alternative approach is to use the action mapping path attribute. +In this case, you extend the ValidatorActionForm instead of the ValidatorForm. The ValidatorActionForm uses the action element's codepath/code -attribute from the struts-config.xml which should match the form element's -codename/code attribute in the validator-rules.xml. +attribute from the Struts configuration which should match the form element's +codename/code attribute in the Validator configuration. /p p -Then a separate action can be defined for each page in a multi-page form -and the validation rules can be associated with the action and not a page -number as in the example of a multi-page form in the validator example. +Then a separate action mapping can be defined for each page in a multi-page +form, and the validation form can be associated with the action rather than +a page number (as shown in the example of a multi-page form in the validator +example). /p /section @@ -66,12 +67,12 @@ section href=i18n name=Internationalization p -Validation rules for forms can be grouped under a codeFormSet/code -element in the validator-rules.xml file. +Each validator form is grouped within a codeFormSet/code element in +the Validator configuration file. The codeFormSet/code has language, country, and variant attributes that correspond with the codejava.util.Locale/code class. -If they are not used, the codeFormSet/code will be set to the default -locale. +If these attributes are not specified, the codeFormSet/code will be set +to the default locale. A codeFormSet/code can also have constants associated with it. On the same level as a codeFormSet/code there can be a global element which can also have constants and have validator actions that perform @@ -158,7 +159,7 @@ section href=builtin name=Standard Built In Validations p -Validator is shipped with the following set of pre-defined validation rules. +Validator ships with a set of pre-defined validators, as follows: /p ul listrongrequired/strong - mandatory field validation. Has no variables. @@ -249,7 +250,7 @@ ]]/code/pre /li listrongdate/strong - validates that a field can be converted to a Date. - This validation rule uses codejava.text.SimpleDateFormat/code to parse the date and + This validator uses codejava.text.SimpleDateFormat/code to parse the date and optionally either a codedatePattern/code or codedatePatternStrict/code variable can be used. If no pattern is specified the default short date format is assumed. The difference between using the codedatePatternStrict/code and codedatePattern/code variables @@ -440,9 +441,9 @@ a password twice for confirmation, to make sure that the values match.) In addition, there are fields in a form that may only be required if other fields have certain values. The codevalidwhen/code -validation rule is designed to handle these cases./p +validator is designed to handle these cases./p p -The codevalidwhen/code rule takes a single codevar/code field, +The codevalidwhen/code validator takes a single codevar/code field, called codetest/code. The value of this var is a boolean expression which must be true in order for the validation to
Re: JSF and highly dynamic apps (was Re: Struts-BSF, Struts-Scripting [was Re: Proposal: Javascript-to-Java object conversions]]])
On Tue, 2 Nov 2004 21:43:41 -0800, Martin Cooper [EMAIL PROTECTED] wrote: This is a really interesting statement. Perhaps I'm wrong, but I've always thought the whole point of JSF was visual components. Yet the statement above clearly indicates that JSF goes well beyond that charter, and clearly suggests that there are facets of JSF that should not be a part of that JSR. FWIW, here is IBM's take on how to build rich web applications using JSF components plus a framework for sending data back and forth: http://www-106.ibm.com/developerworks/websphere/library/techarticles/0411_hasson/0411_hasson.html?ca=dnp-344 Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FacesClient Components [Was Re: JSF and highly dynamic apps (was Re: Struts-BSF, Struts-Scripting [was Re: Proposal: Javascript-to-Java object conversions]]])]
Now that looks pretty cool! It's fee-based, though, right? Anyone taken a look at it? cheers, David |-+ | | Craig McClanahan | | | [EMAIL PROTECTED]| | | om | | || | | 11/04/2004 12:50 | | | PM | | | Please respond to| | | Struts | | | Developers List | | || |-+ ---| | | | To: Struts Developers List [EMAIL PROTECTED], Martin Cooper [EMAIL PROTECTED] | | cc: | | Subject: Re: JSF and highly dynamic apps (was Re: Struts-BSF, Struts-Scripting[was Re: Proposal: | |Javascript-to-Java object conversions]]]) | ---| On Tue, 2 Nov 2004 21:43:41 -0800, Martin Cooper [EMAIL PROTECTED] wrote: This is a really interesting statement. Perhaps I'm wrong, but I've always thought the whole point of JSF was visual components. Yet the statement above clearly indicates that JSF goes well beyond that charter, and clearly suggests that there are facets of JSF that should not be a part of that JSR. FWIW, here is IBM's take on how to build rich web applications using JSF components plus a framework for sending data back and forth: http://www-106.ibm.com/developerworks/websphere/library/techarticles/0411_hasson/0411_hasson.html?ca=dnp-344 Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
subversion checkout for anon
Is there a wiki post on how to do subversion check out for anon? .V - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: subversion checkout for anon
At 5:29 PM -0600 11/4/04, Vic Cekvenich wrote: Is there a wiki post on how to do subversion check out for anon? There's this: http://www.apache.org/dev/version-control.html#anon-svn Anything else is getting into Subversion details which would be client specific. That doesn't mean they couldn't go in the Wiki, of course. The repository URL for Struts is: http://svn.apache.org/repos/asf/struts/trunk/ Joe -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn back; I'll know I'm in the wrong place. - Carlos Santana
Re: subversion checkout for anon
http://www.apache.org/dev/version-control.html That should get ya going - scroll down a bit and you should see it, Vic. Enjoy, Eddie - Original Message - From: Vic Cekvenich [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, November 04, 2004 5:29 PM Subject: subversion checkout for anon Is there a wiki post on how to do subversion check out for anon? .V - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0445-1, 11/03/2004 Tested on: 11/4/2004 9:52:00 PM avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
a suggestion
Hi, We are using struts as the framework of a heavy loaded website for several years. Only recently I've seen the struts resource page showing a list of sites using struts, and I was wondering if you would like to add our website to it. Best regards, and _well_done_ on the job you're doing, Mickey. -- http://www.fetchbook.info/ www.FetchBook.Info Find the lowest price - Compare more then a hundred book stores in a click.
Struts Sub-Projects
Perhaps this has already been discussed, but I couldn't find anything about it How will we organize Struts subprojects in the repository? As I understand it, Struts subprojects are projects that are intimately associated with Struts, yet have their own release cycle. The prime example being struts-faces. If so, why is struts-faces located in /trunk/ and therefore branched and tagged along with Struts core? Shouldn't it have its own trunk/branches/tags triad for its own release cycles? In a particular project in my day job, we have two main components that have their own release cycles. In subversion, we give them the following organization: server/ trunk/ branches/ tags/ client/ trunk/ branches/ tags/ This allows each component to branch and tag without affecting the other. I would think a similiar organization would be practical for Struts to allow sub-projects like struts-faces and struts-flow to manage themselves. I'd recommend (if it hasn't already been discussed and rejected) we adopt a similar pattern with core, struts-faces, struts-flow, and struts-bsf as root directories, each with their own branches/tags/trunk directories. Don - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
