Codebase list libcommons-validator-java / c5fcbff
* New upstream release. * New uploaders: Varun Hiremath and Kumar Appaiah, removed Wolfgang Baer * Use upstream's conf directory for configuration and DTDs. * Use a custom ant.properties to avoid downloads. * Use DEB_UPSTREAM_VERSION in rules instead of versions in rules for symlinking. * debian/control: + Add rhino to Build-Depends-Indep and Depends. + Add XS-Vcs-{Svn, Browser} headers. * debian/compat: switch to 5 * Remove debian/patches and remove RELEASE-NOTES.txt in debian/rules. * Add debian/orig-tar.sh to remove CRLF line terminators from upstream files. * debian/rules: implement get-orig-source * debian/watch: switch to version 3 and call debian/orig-tar.sh Varun Hiremath 16 years ago
14 changed file(s) with 70 addition(s) and 1176 deletion(s). Raw diff Collapse all Expand all
00 build.sysclasspath=only
11 compile.target=1.3
2 conf.home=debian/conf/share
2 dojo_custom_rhino.jar=/usr/share/java/js.jar
3 commons-beanutils.jar=/usr/share/java/commons-beanutils.jar
4 commons-digester.jar=/usr/share/java/commons-digester.jar
5 commons-logging.jar=/usr/share/java/commons-logging.jar
6 oro.jar=/usr/share/java/oro.jar
7 junit.jar=/usr/share/java/junit.jar
8 xerces.jar=/usr/share/java/xercesImpl.jar
0 libcommons-validator-java (1:1.3.1-1) unstable; urgency=low
1
2 [ Kumar Appaiah ]
3 * New upstream release.
4 * New uploaders: Varun Hiremath and Kumar Appaiah, removed Wolfgang Baer
5 * Use upstream's conf directory for configuration and DTDs.
6 * Use a custom ant.properties to avoid downloads.
7 * Use DEB_UPSTREAM_VERSION in rules instead of versions in rules for symlinking.
8
9 [ Varun Hiremath ]
10 * debian/control:
11 + Add rhino to Build-Depends-Indep and Depends.
12 + Add XS-Vcs-{Svn, Browser} headers.
13 * debian/compat: switch to 5
14 * Remove debian/patches and remove RELEASE-NOTES.txt in debian/rules.
15 * Add debian/orig-tar.sh to remove CRLF line terminators from upstream files.
16 * debian/rules: implement get-orig-source
17 * debian/watch: switch to version 3 and call debian/orig-tar.sh
18
19 -- Varun Hiremath <varunhiremath@gmail.com> Sat, 15 Sep 2007 23:14:16 +0530
20
021 libcommons-validator-java (1:1.1.4a-1) unstable; urgency=low
122
223 * build with java-gcj-compat-dev
+0
-5
debian/conf/share/MANIFEST.MF less more
0 Extension-Name: @package@
1 Specification-Vendor: Apache Software Foundation
2 Specification-Version: 1.0
3 Implementation-Vendor: Apache Software Foundation
4 Implementation-Version: @version@
+0
-131
debian/conf/share/ValidatorCheckStyle.xml less more
0 <?xml version="1.0"?>
1 <!DOCTYPE module PUBLIC
2 "-//Puppy Crawl//DTD Check Configuration 1.1//EN"
3 "http://www.puppycrawl.com/dtds/configuration_1_1.dtd">
4
5
6 <!--
7
8 These checks still need to be Voted on for Validator, but
9 at least serve to cut down on some of the noise.
10
11
12 A Checkstyle configuration that checks against the recommendations
13 in Joshua Bloch, Effective Java (highliy recommended read!)
14
15 This file does NOT duplicate the checks for whitespace settings,
16 placement of curly braces, etc. Only the rules that are explicitly
17 mentioned in the book are enforced.
18
19 Currently the amount of rules that can be automatically checked by
20 Checkstyle is not very large, but adding more checks of this quality
21 is a high priority goal for the development team.
22
23 -->
24
25 <module name="Checker">
26
27 <module name="TreeWalker">
28
29 <!-- Item 4 - Avoid creating duplicate objects -->
30 <module name="IllegalInstantiation">
31 <property name="classes" value="java.lang.Boolean, java.lang.String"/>
32 </module>
33
34 <!-- Item 6 - Avoid finalizers -->
35 <!-- this will not find violations that contain linebreaks -->
36 <module name="GenericIllegalRegexp">
37 <property name="format"
38 value="((public)|(protected))\s+void\s+finalize\(\s*\)"/>
39 </module>
40
41 <!-- Item 8 - Always override hashCode when you override equals -->
42 <module name="EqualsHashCode"/>
43
44 <!-- Item 12 - Make all fields private -->
45 <module name="VisibilityModifier"/>
46
47 <!-- Item 15 - Design and document for inheritance or else prohibit it -->
48 <!-- the module actually implements a very strict rule, it would be
49 interesting to know whether Joshua meant what checkstyle implements.
50 We feel this implementation is well suited as a warning,
51 i.e. if you get error messages from this check you should be
52 able to name a good reason to implement your code the way you do it,
53 especially if you are designing a library and not an application. -->
54 <module name="DesignForExtension">
55 <property name="severity" value="warning"/>
56 </module>
57
58 <!-- Item 17 - Use interfaces only to define types -->
59 <module name="InterfaceIsType"/>
60
61 <!-- Item 25 - Design method signatures carefully -->
62 <!-- Avoid long parameter lists -->
63 <module name="ParameterNumber">
64 <property name="max" value="3"/>
65 </module>
66
67 <!-- Item 26 - Use overloading judiciously -->
68 <!-- rfe #659735 -->
69
70 <!-- Item 27 - Return zero-length array, not nulls -->
71 <!-- no rfe yet -->
72
73 <!-- Item 28 - Write doc comments for all exposed API elements -->
74 <module name="JavadocType">
75 <property name="scope" value="protected"/>
76 </module>
77 <module name="JavadocMethod"> <!-- also covers Item 44 -->
78 <property name="scope" value="protected"/>
79 </module>
80 <module name="JavadocVariable">
81 <property name="scope" value="protected"/>
82 </module>
83
84 <!-- Item 29 - Minimize the scope of local variables -->
85 <!-- no rfe yet -->
86
87
88 <!-- Item 38 - Adhere to generally accepted naming conventions -->
89 <module name="PackageName">
90 <!-- no uppercase letters, between 2 and 10 characters -->
91 <property name="format" value="^[a-z]+(\.[a-z][a-z0-9]{1,9})*$"/>
92 </module>
93 <module name="TypeName"/>
94 <module name="ConstantName"/>
95 <module name="LocalFinalVariableName"/>
96 <module name="LocalVariableName"/>
97 <module name="MemberName"/>
98 <module name="MethodName"/>
99 <module name="ParameterName"/>
100 <module name="StaticVariableName"/>
101
102 <!-- Item 47 - Don't ignore exceptions -->
103 <module name="EmptyBlock">
104 <property name="tokens" value="LITERAL_CATCH"/>
105 <!-- require a comment, change to stmt to require a statement -->
106 <property name="option" value="text"/>
107 </module>
108
109 <!-- Item 50 - Never invoke wait outside a loop -->
110 <!-- rfe #712798 -->
111
112 <!-- Item 57 - Provide a readResolve method when necessary -->
113 <!-- no rfe yet -->
114
115 <!-- don't allow tabs -->
116 <module name="TabCharacter"/>
117
118 <!-- enforce License Header -->
119 <module name="Header">
120 <property name="headerFile" value="LICENSE.txt"/>
121 <!-- Skip over CVS header variables. -->
122 <property name="ignoreLines" value="2,3,4,5"/>
123 </module>
124
125 </module>
126
127 <!-- enforce package documentation -->
128 <module name="PackageHtml"/>
129
130 </module>
+0
-246
debian/conf/share/validator_1_0.dtd less more
0 <!--
1 DTD for the Validator Rules Configuration File, Version 1.0
2
3 To allow for XML validation of your rules configuration
4 file, include the following DOCTYPE element at the beginning (after
5 the "xml" declaration):
6
7 <!DOCTYPE form-validation PUBLIC
8 "-//Apache Software Foundation//DTD Commons Validator Rules Configuration 1.0//EN"
9 "http://jakarta.apache.org/commons/dtds/validator_1_0.dtd">
10
11 Id: validator_1_0.dtd,v 1.4 2002/10/23 01:32:01 turner Exp
12 -->
13
14
15 <!-- =================================================== Top Level Elements -->
16
17
18 <!--
19 The "form-validation" element is the root of the configuration file
20 hierarchy, and contains nested elements for all of the other
21 configuration settings.
22 -->
23 <!ELEMENT form-validation (global*, formset*)>
24
25
26 <!--
27 The elements defined here are all global and must be nested within a
28 "global" element.
29 -->
30 <!ELEMENT global (validator*, constant*)>
31
32
33 <!--
34 The "validator" element defines what validators objects can be used with
35 the fields referenced by the formset elements. The validator element can
36 accept 4 properties: name, classname, method, methodparams, msg, depends,
37 and jsFunctionName.
38 -->
39 <!ELEMENT validator (javascript?)>
40 <!ATTLIST validator name CDATA #REQUIRED
41 classname CDATA #REQUIRED
42 method CDATA #REQUIRED
43 methodParams CDATA #REQUIRED
44 msg CDATA #REQUIRED
45 depends CDATA #IMPLIED
46 jsFunctionName CDATA #IMPLIED >
47
48
49 <!--
50 The "javascript" element defines a JavaScript that can be used to perform
51 client-side validators.
52 -->
53 <!ELEMENT javascript (#PCDATA)>
54
55
56 <!--
57 The "constant" element defines a static value that can be used as
58 replacement parameters within "field" elements. The "constant-name" and
59 "constant-value" elements define the constant's reference id and replacement
60 value.
61 -->
62 <!ELEMENT constant (constant-name, constant-value)>
63 <!ELEMENT constant-name (#PCDATA)>
64 <!ELEMENT constant-value (#PCDATA)>
65
66
67 <!--
68 The "formset" element defines a set of forms for a locale. Formsets for
69 specific locales can override only those fields that change. The
70 localization is properly scoped, so that a formset can override just the
71 language, or just the country, or both.
72 -->
73 <!ELEMENT formset (constant*, form+)>
74 <!ATTLIST formset language CDATA #IMPLIED
75 country CDATA #IMPLIED >
76
77
78 <!--
79 The "form" element defines a set of fields to be validated. The name
80 corresponds to the identifer the application assigns to the form.
81 -->
82 <!ELEMENT form (field+ )>
83 <!ATTLIST form name CDATA #REQUIRED>
84
85
86 <!--
87 The "field" element defines the properties to be validated. In a
88 web application, a field would also correspond to a control on
89 a HTML form. To validate the properties, the validator works through
90 a JavaBean representation. The field element can accept up to 4
91 attributes:
92
93 property The property on the JavaBean corresponding to this
94 field element.
95
96 depends The comma-delimited list of validators to apply against
97 this field. For the field to succeed, all the
98 validators must succeed.
99
100 page The JavaBean corresponding to this form may include
101 a page property. Only fields with a "page" attribute
102 value that is equal to or less than the page property
103 on the form JavaBean are processed. This is useful when
104 using a "wizard" approach to completing a large form,
105 to ensure that a page is not skipped.
106 [0]
107
108 indexedListProperty
109 The "indexedListProperty" is the method name that will
110 return an array or a Collection used to retrieve the
111 list and then loop through the list performing the
112 validations for this field.
113
114 -->
115 <!ELEMENT field (msg|arg0|arg1|arg2|arg3|var)*>
116 <!ATTLIST field property CDATA #REQUIRED
117 depends CDATA #IMPLIED
118 page CDATA #IMPLIED
119 indexedListProperty CDATA #IMPLIED >
120
121
122 <!--
123 The "msg" element defines a custom message key to use when one of the
124 validators for this field fails. Each validator has a default message
125 property that is used when a corresonding field msg is not specified.
126 Each validator applied to a field may have its own msg element.
127 The msg element accepts up to three attributes.
128
129 name The name of the validator corresponding to this msg.
130
131 key The key that will return the message template from a
132 resource bundle.
133
134 resource If set to "false", the key is taken to be a literal
135 value rather than a bundle key.
136 [true]
137 -->
138 <!ELEMENT msg EMPTY>
139 <!ATTLIST msg name CDATA #IMPLIED
140 key CDATA #IMPLIED
141 resource CDATA #IMPLIED >
142
143
144 <!--
145 The "arg0" element defines the first replacement value to use with the
146 message template for this validator or this field.
147 The arg0 element accepts up to three attributes.
148
149 name The name of the validator corresponding to this msg.
150
151 key The key that will return the message template from a
152 resource bundle.
153
154 resource If set to "false", the key is taken to be a literal
155 value rather than a bundle key.
156 [true]
157 -->
158 <!ELEMENT arg0 EMPTY>
159 <!ATTLIST arg0 name CDATA #IMPLIED
160 key CDATA #IMPLIED
161 resource CDATA #IMPLIED >
162
163
164 <!--
165 The "arg1" element defines the second replacement value to use with the
166 message template for this validator or this field.
167 The arg1 element accepts up to three attributes.
168
169 name The name of the validator corresponding to this msg.
170
171 key The key that will return the message template from a
172 resource bundle.
173
174 resource If set to "false", the key is taken to be a literal
175 value rather than a bundle key.
176 [true]
177 -->
178 <!ELEMENT arg1 EMPTY>
179 <!ATTLIST arg1 name CDATA #IMPLIED
180 key CDATA #IMPLIED
181 resource CDATA #IMPLIED >
182
183
184 <!--
185 The "arg2" element defines the third replacement value to use with the
186 message template for this validator or this field.
187 The arg2 element accepts up to three attributes.
188
189 name The name of the validator corresponding to this msg.
190
191 key The key that will return the message template from a
192 resource bundle.
193
194 resource If set to "false", the key is taken to be a literal
195 value rather than a bundle key.
196 [true]
197 -->
198 <!ELEMENT arg2 EMPTY>
199 <!ATTLIST arg2 name CDATA #IMPLIED
200 key CDATA #IMPLIED
201 resource CDATA #IMPLIED >
202
203 <!--
204 The "arg3" element defines the fourth replacement value to use with the
205 message template for this validator or this field.
206 The arg0 element accepts up to three attributes.
207
208 name The name of the validator corresponding to this msg.
209
210 key The key that will return the message template from a
211 resource bundle.
212
213 resource If set to "false", the key is taken to be a literal
214 value rather than a bundle key.
215 [true]
216 -->
217 <!ELEMENT arg3 EMPTY>
218 <!ATTLIST arg3 name CDATA #IMPLIED
219 key CDATA #IMPLIED
220 resource CDATA #IMPLIED >
221
222
223 <!--
224 The "var" element can set parameters that a field may need to pass to
225 one of its validators, such as the minimum and maximum values in a
226 range validation. These parameters may also be referenced by one of the
227 arg? elements using a shell syntax: ${var:var-name}.
228 -->
229 <!ELEMENT var (var-name, var-value)>
230
231
232
233 <!--
234 The name of the var parameter to provide to a field's validators.
235 -->
236 <!ELEMENT var-name (#PCDATA)>
237
238
239
240 <!--
241 The value of the var parameter to provide to a field's validators.
242 -->
243 <!ELEMENT var-value (#PCDATA)>
244
245 <!-- eof -->
+0
-245
debian/conf/share/validator_1_0_1.dtd less more
0 <!--
1 DTD for the Validator Rules Configuration File, Version 1.0.1
2
3 To allow for XML validation of your rules configuration
4 file, include the following DOCTYPE element at the beginning (after
5 the "xml" declaration):
6
7 <!DOCTYPE form-validation PUBLIC
8 "-//Apache Software Foundation//DTD Commons Validator Rules Configuration 1.0.1//EN"
9 "http://jakarta.apache.org/commons/dtds/validator_1_0_1.dtd">
10
11 Id: validator_1_0_1.dtd,v 1.3 2003/03/15 23:07:06 dgraham Exp
12 -->
13
14
15 <!-- =================================================== Top Level Elements -->
16
17
18 <!--
19 The "form-validation" element is the root of the configuration file
20 hierarchy, and contains nested elements for all of the other
21 configuration settings.
22 -->
23 <!ELEMENT form-validation (global*, formset*)>
24
25
26 <!--
27 The elements defined here are all global and must be nested within a
28 "global" element.
29 -->
30 <!ELEMENT global (validator*, constant*)>
31
32
33 <!--
34 The "validator" element defines what validator objects can be used with
35 the fields referenced by the formset elements.
36 -->
37 <!ELEMENT validator (javascript?)>
38 <!ATTLIST validator name CDATA #REQUIRED
39 classname CDATA #REQUIRED
40 method CDATA #REQUIRED
41 methodParams CDATA #REQUIRED
42 msg CDATA #REQUIRED
43 depends CDATA #IMPLIED
44 jsFunctionName CDATA #IMPLIED >
45
46
47 <!--
48 The "javascript" element defines a JavaScript that can be used to perform
49 client-side validators.
50 -->
51 <!ELEMENT javascript (#PCDATA)>
52
53
54 <!--
55 The "constant" element defines a static value that can be used as
56 replacement parameters within "field" elements. The "constant-name" and
57 "constant-value" elements define the constant's reference id and replacement
58 value.
59 -->
60 <!ELEMENT constant (constant-name, constant-value)>
61 <!ELEMENT constant-name (#PCDATA)>
62 <!ELEMENT constant-value (#PCDATA)>
63
64
65 <!--
66 The "formset" element defines a set of forms for a locale. Formsets for
67 specific locales can override only those fields that change. The
68 localization is properly scoped, so that a formset can override just the
69 language, or just the country, or both.
70 -->
71 <!ELEMENT formset (constant*, form+)>
72 <!ATTLIST formset language CDATA #IMPLIED
73 country CDATA #IMPLIED
74 variant CDATA #IMPLIED >
75
76
77 <!--
78 The "form" element defines a set of fields to be validated. The name
79 corresponds to the identifer the application assigns to the form.
80 -->
81 <!ELEMENT form (field+ )>
82 <!ATTLIST form name CDATA #REQUIRED>
83
84
85 <!--
86 The "field" element defines the properties to be validated. In a
87 web application, a field would also correspond to a control on
88 a HTML form. To validate the properties, the validator works through
89 a JavaBean representation. The field element can accept up to 4
90 attributes:
91
92 property The property on the JavaBean corresponding to this
93 field element.
94
95 depends The comma-delimited list of validators to apply against
96 this field. For the field to succeed, all the
97 validators must succeed.
98
99 page The JavaBean corresponding to this form may include
100 a page property. Only fields with a "page" attribute
101 value that is equal to or less than the page property
102 on the form JavaBean are processed. This is useful when
103 using a "wizard" approach to completing a large form,
104 to ensure that a page is not skipped.
105 [0]
106
107 indexedListProperty
108 The "indexedListProperty" is the method name that will
109 return an array or a Collection used to retrieve the
110 list and then loop through the list performing the
111 validations for this field.
112
113 -->
114 <!ELEMENT field (msg|arg0|arg1|arg2|arg3|var)*>
115 <!ATTLIST field property CDATA #REQUIRED
116 depends CDATA #IMPLIED
117 page CDATA #IMPLIED
118 indexedListProperty CDATA #IMPLIED >
119
120
121 <!--
122 The "msg" element defines a custom message key to use when one of the
123 validators for this field fails. Each validator has a default message
124 property that is used when a corresonding field msg is not specified.
125 Each validator applied to a field may have its own msg element.
126 The msg element accepts up to three attributes.
127
128 name The name of the validator corresponding to this msg.
129
130 key The key that will return the message template from a
131 resource bundle.
132
133 resource If set to "false", the key is taken to be a literal
134 value rather than a bundle key.
135 [true]
136 -->
137 <!ELEMENT msg EMPTY>
138 <!ATTLIST msg name CDATA #IMPLIED
139 key CDATA #IMPLIED
140 resource CDATA #IMPLIED >
141
142
143 <!--
144 The "arg0" element defines the first replacement value to use with the
145 message template for this validator or this field.
146 The arg0 element accepts up to three attributes.
147
148 name The name of the validator corresponding to this msg.
149
150 key The key that will return the message template from a
151 resource bundle.
152
153 resource If set to "false", the key is taken to be a literal
154 value rather than a bundle key.
155 [true]
156 -->
157 <!ELEMENT arg0 EMPTY>
158 <!ATTLIST arg0 name CDATA #IMPLIED
159 key CDATA #IMPLIED
160 resource CDATA #IMPLIED >
161
162
163 <!--
164 The "arg1" element defines the second replacement value to use with the
165 message template for this validator or this field.
166 The arg1 element accepts up to three attributes.
167
168 name The name of the validator corresponding to this msg.
169
170 key The key that will return the message template from a
171 resource bundle.
172
173 resource If set to "false", the key is taken to be a literal
174 value rather than a bundle key.
175 [true]
176 -->
177 <!ELEMENT arg1 EMPTY>
178 <!ATTLIST arg1 name CDATA #IMPLIED
179 key CDATA #IMPLIED
180 resource CDATA #IMPLIED >
181
182
183 <!--
184 The "arg2" element defines the third replacement value to use with the
185 message template for this validator or this field.
186 The arg2 element accepts up to three attributes.
187
188 name The name of the validator corresponding to this msg.
189
190 key The key that will return the message template from a
191 resource bundle.
192
193 resource If set to "false", the key is taken to be a literal
194 value rather than a bundle key.
195 [true]
196 -->
197 <!ELEMENT arg2 EMPTY>
198 <!ATTLIST arg2 name CDATA #IMPLIED
199 key CDATA #IMPLIED
200 resource CDATA #IMPLIED >
201
202 <!--
203 The "arg3" element defines the fourth replacement value to use with the
204 message template for this validator or this field.
205 The arg0 element accepts up to three attributes.
206
207 name The name of the validator corresponding to this msg.
208
209 key The key that will return the message template from a
210 resource bundle.
211
212 resource If set to "false", the key is taken to be a literal
213 value rather than a bundle key.
214 [true]
215 -->
216 <!ELEMENT arg3 EMPTY>
217 <!ATTLIST arg3 name CDATA #IMPLIED
218 key CDATA #IMPLIED
219 resource CDATA #IMPLIED >
220
221
222 <!--
223 The "var" element can set parameters that a field may need to pass to
224 one of its validators, such as the minimum and maximum values in a
225 range validation. These parameters may also be referenced by one of the
226 arg? elements using a shell syntax: ${var:var-name}.
227 -->
228 <!ELEMENT var (var-name, var-value)>
229
230
231
232 <!--
233 The name of the var parameter to provide to a field's validators.
234 -->
235 <!ELEMENT var-name (#PCDATA)>
236
237
238
239 <!--
240 The value of the var parameter to provide to a field's validators.
241 -->
242 <!ELEMENT var-value (#PCDATA)>
243
244 <!-- eof -->
+0
-292
debian/conf/share/validator_1_1.dtd less more
0 <!--
1 DTD for the Validator Rules Configuration File, Version 1.1
2
3 To allow for XML validation of your rules configuration
4 file, include the following DOCTYPE element at the beginning (after
5 the "xml" declaration):
6
7 <!DOCTYPE form-validation PUBLIC
8 "-//Apache Software Foundation//DTD Commons Validator Rules Configuration 1.1//EN"
9 "http://jakarta.apache.org/commons/dtds/validator_1_1.dtd">
10
11 Id: validator_1_1.dtd,v 1.5 2003/08/11 23:50:31 dgraham Exp
12 -->
13
14
15
16 <!--
17 The "form-validation" element is the root of the configuration file
18 hierarchy, and contains nested elements for all of the other
19 configuration settings.
20 -->
21 <!ELEMENT form-validation (global*, formset*)>
22
23
24 <!--
25 The elements defined here are all global and must be nested within a
26 "global" element.
27 -->
28 <!ELEMENT global (validator*, constant*)>
29
30
31 <!--
32 The "validator" element defines what validator objects can be used with
33 the fields referenced by the formset elements.
34 -->
35 <!ELEMENT validator (javascript?)>
36 <!ATTLIST validator name CDATA #REQUIRED>
37 <!ATTLIST validator classname CDATA #REQUIRED>
38 <!ATTLIST validator method CDATA #REQUIRED>
39 <!ATTLIST validator methodParams CDATA #REQUIRED>
40 <!ATTLIST validator msg CDATA #REQUIRED>
41 <!ATTLIST validator depends CDATA #IMPLIED>
42 <!ATTLIST validator jsFunctionName CDATA #IMPLIED>
43 <!ATTLIST validator jsFunction CDATA #IMPLIED>
44
45
46 <!--
47 The "javascript" element defines a JavaScript that can be used to perform
48 client-side validators.
49 -->
50 <!ELEMENT javascript (#PCDATA)>
51
52
53 <!--
54 The "constant" element defines a static value that can be used as
55 replacement parameters within "field" elements. The "constant-name" and
56 "constant-value" elements define the constant's reference id and replacement
57 value.
58 -->
59 <!ELEMENT constant (constant-name, constant-value)>
60 <!ELEMENT constant-name (#PCDATA)>
61 <!ELEMENT constant-value (#PCDATA)>
62
63
64 <!--
65 The "formset" element defines a set of forms for a locale. Formsets for
66 specific locales can override only those fields that change. The
67 localization is properly scoped, so that a formset can override just the
68 language, or just the country, or both.
69 -->
70 <!ELEMENT formset (constant*, form+)>
71 <!ATTLIST formset language CDATA #IMPLIED>
72 <!ATTLIST formset country CDATA #IMPLIED>
73 <!ATTLIST formset variant CDATA #IMPLIED>
74
75
76 <!--
77 The "form" element defines a set of fields to be validated. The name
78 corresponds to the identifer the application assigns to the form.
79 -->
80 <!ELEMENT form (field+)>
81 <!ATTLIST form name CDATA #REQUIRED>
82
83
84 <!--
85 The "field" element defines the properties to be validated. In a
86 web application, a field would also correspond to a control on
87 a HTML form. To validate the properties, the validator works through
88 a JavaBean representation. The field element accepts these
89 attributes:
90
91 property The property on the JavaBean corresponding to this
92 field element.
93
94 depends The comma-delimited list of validators to apply against
95 this field. For the field to succeed, all the
96 validators must succeed.
97
98 page The JavaBean corresponding to this form may include
99 a page property. Only fields with a "page" attribute
100 value that is equal to or less than the page property
101 on the form JavaBean are processed. This is useful when
102 using a "wizard" approach to completing a large form,
103 to ensure that a page is not skipped.
104 [0]
105
106 indexedListProperty
107 The "indexedListProperty" is the method name that will
108 return an array or a Collection used to retrieve the
109 list and then loop through the list performing the
110 validations for this field.
111
112 -->
113 <!ELEMENT field (msg|arg|arg0|arg1|arg2|arg3|var)*>
114 <!ATTLIST field property CDATA #REQUIRED>
115 <!ATTLIST field depends CDATA #IMPLIED>
116 <!ATTLIST field page CDATA #IMPLIED>
117 <!ATTLIST field indexedListProperty CDATA #IMPLIED>
118
119
120 <!--
121 The "msg" element defines a custom message key to use when one of the
122 validators for this field fails. Each validator has a default message
123 property that is used when a corresonding field msg is not specified.
124 Each validator applied to a field may have its own msg element.
125 The msg element accepts these attributes.
126
127 name The name of the validator corresponding to this msg.
128
129 bundle The resource bundle name that the key should be resolved in.
130
131 key The key that will return the message template from a
132 resource bundle.
133
134 resource If set to "false", the key is taken to be a literal
135 value rather than a bundle key.
136 [true]
137 -->
138 <!ELEMENT msg EMPTY>
139 <!ATTLIST msg key CDATA #REQUIRED>
140 <!ATTLIST msg name CDATA #REQUIRED>
141 <!ATTLIST msg bundle CDATA #IMPLIED>
142 <!ATTLIST msg resource CDATA #IMPLIED>
143
144
145
146 <!--
147 The "arg" element defines a replacement value to use with the
148 message template for this validator or this field.
149 The arg element accepts these attributes.
150
151 name The name of the validator corresponding to this msg.
152 If not supplied, this argument will be used in the given
153 position for every validator.
154
155 bundle The resource bundle name that the key should be resolved in.
156
157 key The key that will return the message template from a
158 resource bundle.
159
160 resource If set to "false", the key is taken to be a literal
161 value rather than a bundle key.
162 [true]
163
164 position The position of this replacement parameter in the message.
165 For example, position="0" will set the first argument.
166 [0]
167 -->
168 <!ELEMENT arg EMPTY>
169 <!ATTLIST arg key CDATA #REQUIRED>
170 <!ATTLIST arg bundle CDATA #IMPLIED>
171 <!ATTLIST arg name CDATA #IMPLIED>
172 <!ATTLIST arg resource CDATA #IMPLIED>
173 <!ATTLIST arg position CDATA #IMPLIED>
174
175
176
177 <!--
178
179 DEPRECATED Use <arg position="0"/> instead.
180
181 The "arg0" element defines the first replacement value to use with the
182 message template for this validator or this field.
183 The arg0 element accepts these attributes.
184
185 name The name of the validator corresponding to this msg.
186
187 key The key that will return the message template from a
188 resource bundle.
189
190 resource If set to "false", the key is taken to be a literal
191 value rather than a bundle key.
192 [true]
193 -->
194 <!ELEMENT arg0 EMPTY>
195 <!ATTLIST arg0 name CDATA #IMPLIED>
196 <!ATTLIST arg0 key CDATA #IMPLIED>
197 <!ATTLIST arg0 resource CDATA #IMPLIED>
198
199
200 <!--
201
202 DEPRECATED Use <arg position="1"/> instead.
203
204 The "arg1" element defines the second replacement value to use with the
205 message template for this validator or this field.
206 The arg1 element accepts these attributes.
207
208 name The name of the validator corresponding to this msg.
209
210 key The key that will return the message template from a
211 resource bundle.
212
213 resource If set to "false", the key is taken to be a literal
214 value rather than a bundle key.
215 [true]
216 -->
217 <!ELEMENT arg1 EMPTY>
218 <!ATTLIST arg1 name CDATA #IMPLIED>
219 <!ATTLIST arg1 key CDATA #IMPLIED>
220 <!ATTLIST arg1 resource CDATA #IMPLIED>
221
222
223 <!--
224
225 DEPRECATED Use <arg position="2"/> instead.
226
227 The "arg2" element defines the third replacement value to use with the
228 message template for this validator or this field.
229 The arg2 element accepts these attributes.
230
231 name The name of the validator corresponding to this msg.
232
233 key The key that will return the message template from a
234 resource bundle.
235
236 resource If set to "false", the key is taken to be a literal
237 value rather than a bundle key.
238 [true]
239 -->
240 <!ELEMENT arg2 EMPTY>
241 <!ATTLIST arg2 name CDATA #IMPLIED>
242 <!ATTLIST arg2 key CDATA #IMPLIED>
243 <!ATTLIST arg2 resource CDATA #IMPLIED>
244
245
246 <!--
247
248 DEPRECATED Use <arg position="3"/> instead.
249
250 The "arg3" element defines the fourth replacement value to use with the
251 message template for this validator or this field.
252 The arg0 element accepts these attributes.
253
254 name The name of the validator corresponding to this msg.
255
256 key The key that will return the message template from a
257 resource bundle.
258
259 resource If set to "false", the key is taken to be a literal
260 value rather than a bundle key.
261 [true]
262 -->
263 <!ELEMENT arg3 EMPTY>
264 <!ATTLIST arg3 name CDATA #IMPLIED>
265 <!ATTLIST arg3 key CDATA #IMPLIED>
266 <!ATTLIST arg3 resource CDATA #IMPLIED>
267
268
269 <!--
270 The "var" element can set parameters that a field may need to pass to
271 one of its validators, such as the minimum and maximum values in a
272 range validation. These parameters may also be referenced by one of the
273 arg? elements using a shell syntax: ${var:var-name}.
274 -->
275 <!ELEMENT var (var-name, var-value)>
276
277
278
279 <!--
280 The name of the var parameter to provide to a field's validators.
281 -->
282 <!ELEMENT var-name (#PCDATA)>
283
284
285
286 <!--
287 The value of the var parameter to provide to a field's validators.
288 -->
289 <!ELEMENT var-value (#PCDATA)>
290
291
+0
-226
debian/conf/share/validator_1_2_0.dtd less more
0 <!--
1 DTD for the Validator Rules Configuration File, Version 1.2.0
2
3 To allow for XML validation of your rules configuration
4 file, include the following DOCTYPE element at the beginning (after
5 the "xml" declaration):
6
7 <!DOCTYPE form-validation PUBLIC
8 "-//Apache Software Foundation//DTD Commons Validator Rules Configuration 1.2.0//EN"
9 "http://jakarta.apache.org/commons/dtds/validator_1_2_0.dtd">
10
11 Id: validator_1_2_0.dtd,v 1.8 2004/11/12 16:02:52 niallp Exp
12 -->
13
14
15
16 <!--
17 The "form-validation" element is the root of the configuration file
18 hierarchy, and contains nested elements for all of the other
19 configuration settings.
20 -->
21 <!ELEMENT form-validation (global*, formset*)>
22
23
24 <!--
25 The elements defined here are all global and must be nested within a
26 "global" element.
27 -->
28 <!ELEMENT global (validator*, constant*)>
29
30
31 <!--
32 Defines what validator objects can be used with
33 the fields referenced by the formset elements.
34 elements:
35 validator Defines a new validatior
36 javascript The javascript source code for client side validation.
37 attributes:
38 name The name of this validation
39 classname The java class name that handles server side validation
40 method The java method that handles server side validation
41 methodParams The java class types passed to the serverside method
42 msg a generic message key to use when this validator fails.
43 It can be overridden by the 'msg' element for a specific field.
44 depends The comma-delimited list of validator that are called before this validator.
45 For this validation to succeed, all the listed validators must succeed.
46 jsFunctionName The name of the javascript function which returns all fields of a certain type.
47 jsFunction The name of the javascript function which is passed the form for validation.
48
49 -->
50 <!ELEMENT validator (javascript?)>
51 <!ATTLIST validator name CDATA #REQUIRED>
52 <!ATTLIST validator classname CDATA #REQUIRED>
53 <!ATTLIST validator method CDATA #REQUIRED>
54 <!ATTLIST validator methodParams CDATA #REQUIRED>
55 <!ATTLIST validator msg CDATA #REQUIRED>
56 <!ATTLIST validator depends CDATA #IMPLIED>
57 <!ATTLIST validator jsFunctionName CDATA #IMPLIED>
58 <!ATTLIST validator jsFunction CDATA #IMPLIED>
59
60
61
62 <!--
63 Defines a JavaScript that can be used to perform
64 client-side validators.
65 -->
66 <!ELEMENT javascript (#PCDATA)>
67
68
69 <!--
70 Defines a static value that can be used as
71 replacement parameters within "field" elements. The "constant-name" and
72 "constant-value" elements define the constant's reference id and replacement
73 value.
74 -->
75 <!ELEMENT constant (constant-name, constant-value)>
76 <!ELEMENT constant-name (#PCDATA)>
77 <!ELEMENT constant-value (#PCDATA)>
78
79
80 <!--
81 Defines a set of forms for a locale. Formsets for
82 specific locales can override only those fields that change. The
83 localization is properly scoped, so that a formset can override just the
84 language, or just the country, or both.
85 -->
86 <!ELEMENT formset (constant*, form+)>
87 <!ATTLIST formset language CDATA #IMPLIED>
88 <!ATTLIST formset country CDATA #IMPLIED>
89 <!ATTLIST formset variant CDATA #IMPLIED>
90
91
92 <!--
93 Defines a set of fields to be validated. The name
94 corresponds to the identifier the application assigns to the form.
95 -->
96 <!ELEMENT form (field+)>
97 <!ATTLIST form name CDATA #REQUIRED>
98 <!ATTLIST form extends CDATA #IMPLIED>
99
100
101
102 <!--
103 Defines the properties to be validated. In a
104 web application, a field would also correspond to a control on
105 a HTML form. To validate the properties, the validator works through
106 a JavaBean representation. The field element accepts these
107 attributes:
108
109 property The property on the JavaBean corresponding to this
110 field element.
111
112 depends The comma-delimited list of validators to apply against
113 this field. For the field to succeed, all the
114 validators must succeed.
115
116 page The JavaBean corresponding to this form may include
117 a page property. Only fields with a "page" attribute
118 value that is equal to or less than the page property
119 on the form JavaBean are processed. This is useful when
120 using a "wizard" approach to completing a large form,
121 to ensure that a page is not skipped.
122 [0]
123
124 indexedListProperty
125 The "indexedListProperty" is the method name that will
126 return an array or a Collection used to retrieve the
127 list and then loop through the list performing the
128 validations for this field.
129
130 -->
131 <!ELEMENT field (msg|arg|var)*>
132 <!ATTLIST field property CDATA #REQUIRED>
133 <!ATTLIST field depends CDATA #IMPLIED>
134 <!ATTLIST field page CDATA #IMPLIED>
135 <!ATTLIST field indexedListProperty CDATA #IMPLIED>
136
137
138 <!--
139 Defines a custom message key to use when one of the
140 validators for this field fails. Each validator has a default message
141 property that is used when a corresponding field msg is not specified.
142 Each validator applied to a field may have its own msg element.
143 The msg element accepts these attributes.
144
145 name The name of the validator corresponding to this msg.
146
147 bundle The resource bundle name that the key should be resolved in.
148
149 key The key that will return the message template from a
150 resource bundle.
151
152 resource If set to "false", the key is taken to be a literal
153 value rather than a bundle key.
154 [true]
155 -->
156 <!ELEMENT msg EMPTY>
157 <!ATTLIST msg key CDATA #REQUIRED>
158 <!ATTLIST msg name CDATA #REQUIRED>
159 <!ATTLIST msg bundle CDATA #IMPLIED>
160 <!ATTLIST msg resource CDATA #IMPLIED>
161
162
163
164 <!--
165 Defines a replacement value to use with the
166 message template for this validator or this field.
167 The arg element accepts these attributes.
168
169 name The name of the validator corresponding to this msg.
170 If not supplied, this argument will be used in the given
171 position for every validator.
172
173 bundle The resource bundle name that the key should be resolved in.
174
175 key The key that will return the message template from a
176 resource bundle.
177
178 resource If set to "false", the key is taken to be a literal
179 value rather than a bundle key.
180 [true]
181
182 position The position of this replacement parameter in the message.
183 For example, position="0" will set the first argument.
184
185 N.B. Since 1.2.0 position is ignored for 'default' arguments
186 (i.e. those with no 'name' supplied) - it is calculated
187 automatically from the order the arguments are added in.
188 For 'overriden' arguments (i.e. those with a 'name')
189 it is optional. If 'position' is not supplied it will
190 use the position of the 'default' argument it follows.
191 -->
192 <!ELEMENT arg EMPTY>
193 <!ATTLIST arg key CDATA #REQUIRED>
194 <!ATTLIST arg bundle CDATA #IMPLIED>
195 <!ATTLIST arg name CDATA #IMPLIED>
196 <!ATTLIST arg resource CDATA #IMPLIED>
197 <!ATTLIST arg position CDATA #IMPLIED>
198
199 <!--
200 The "var" element can set parameters that a field may need to pass to
201 one of its validators, such as the minimum and maximum values in a
202 range validation. These parameters may also be referenced by one of the
203 arg? elements using a shell syntax: ${var:var-name}.
204 -->
205 <!ELEMENT var (var-name, var-value, var-jstype?)>
206
207
208
209 <!--
210 The name of the var parameter to provide to a field's validators.
211 -->
212 <!ELEMENT var-name (#PCDATA)>
213
214
215
216 <!--
217 The value of the var parameter to provide to a field's validators.
218 -->
219 <!ELEMENT var-value (#PCDATA)>
220
221 <!--
222 The javascript type. Possible Values [int|string|regexp]
223 -->
224 <!ELEMENT var-jstype (#PCDATA)>
225
11 Section: libs
22 Priority: optional
33 Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
4 Uploaders: Arnaud Vandyck <avdyk@debian.org>, Wolfgang Baer <WBaer@gmx.de>
5 Build-Depends: debhelper (>= 4.2.30), cdbs
6 Build-Depends-Indep: java-gcj-compat-dev, ant, junit (>= 3.8.1), libcommons-beanutils-java (>= 1.5), libcommons-collections-java (>= 2.1), libcommons-digester-java (>= 1.4), libcommons-logging-java (>= 1.0.3), liboro-java (>= 2.0.6), sgml-base
4 Uploaders: Arnaud Vandyck <avdyk@debian.org>, Kumar Appaiah <akumar@ee.iitm.ac.in>, Varun Hiremath <varunhiremath@gmail.com>
5 Build-Depends: debhelper (>= 5), cdbs
6 Build-Depends-Indep: java-gcj-compat-dev, ant, junit (>= 3.8.1), libcommons-beanutils-java (>= 1.5), libcommons-collections-java (>= 2.1), libcommons-digester-java (>= 1.4), libcommons-logging-java (>= 1.0.3), liboro-java (>= 2.0.6), sgml-base, rhino
77 Standards-Version: 3.7.2
8 XS-Vcs-Svn: svn://svn.debian.org/svn/pkg-java/trunk/libcommons-validator-java
9 XS-Vcs-Browser: http://svn.debian.org/wsvn/pkg-java/trunk/libcommons-validator-java
810
911 Package: libcommons-validator-java
1012 Architecture: all
11 Depends: kaffe | java1-runtime | java2-runtime, libcommons-beanutils-java (>= 1.5), libcommons-collections-java (>= 2.1), libcommons-digester-java (>= 1.4), libcommons-logging-java (>= 1.0.3), liboro-java (>= 2.0.6), sgml-base
13 Depends: kaffe | java1-runtime | java2-runtime, libcommons-beanutils-java (>= 1.5), libcommons-collections-java (>= 2.1), libcommons-digester-java (>= 1.4), libcommons-logging-java (>= 1.0.3), liboro-java (>= 2.0.6), sgml-base, rhino
1214 Description: ease and speed development and maintenance of validation rules
1315 The Commons Validator is a basic validation framework
1416 that lets you define validation rules for a JavaBean
1820 keeps them abstracted from JavaBean you are validating.
1921 .
2022 This is a part of the Apache Jakarta Project.
21 Home: <http://jakarta.apache.org/commons/validator/>
23 .
24 Homepage: http://jakarta.apache.org/commons/validator/
0 #!/bin/sh -e
1
2 # called by uscan with '--upstream-version' <version> <file>
3 UDIR=commons-validator-$2-src
4 DDIR=libcommons-validator-java-$2
5
6 # Remove ^M CRLF line terminators
7 tar -z -x -f $3
8 mv $UDIR $DDIR
9 (cd $DDIR; find -type f|xargs perl -pi -e 's/\r$//g')
10 GZIP=--best tar -c -z -f $3 $DDIR
11 rm -rf $DDIR $UDIR
12
13 # move to directory 'tarballs'
14 if [ -r .svn/deb-layout ]; then
15 . .svn/deb-layout
16 mv $3 $origDir
17 echo "moved $3 to $origDir"
18 fi
19
20 exit 0
+0
-13
debian/patches/01_dont_copy_RELEASE-NOTES.patch less more
0 --- build.xml.orig 2006-07-31 14:01:00.000000000 +0000
1 +++ build.xml 2006-07-31 14:01:40.000000000 +0000
2 @@ -266,8 +266,8 @@
3 <mkdir dir="${dist.home}"/>
4 <copy file="LICENSE.txt"
5 todir="${dist.home}"/>
6 - <copy file="RELEASE-NOTES.readme"
7 - todir="${dist.home}"/>
8 + <!-- copy file="RELEASE-NOTES.readme"
9 + todir="${dist.home}"/ -->
10 <mkdir dir="${build.home}/classes/META-INF"/>
11 <copy file="LICENSE.txt"
12 tofile="${build.home}/classes/META-INF/LICENSE.txt"/>
55
66 include /usr/share/cdbs/1/rules/debhelper.mk
77 include /usr/share/cdbs/1/class/ant.mk
8 include /usr/share/cdbs/1/rules/simple-patchsys.mk
98
10 JAVA_HOME := /usr/lib/jvm/java-gcj
9 JAVA_HOME := /usr/lib/jvm/java-gcj
1110 DEB_JARS := junit commons-beanutils commons-collections commons-digester commons-logging oro
1211 DEB_ANT_BUILD_TARGET := dist
1312
1514 DEB_INSTALL_DOCS_ALL := NOTICE.txt dist/docs/*
1615
1716 LIBRARY=commons-validator
18 VERSION=1.1.4
1917
2018 clean::
21 # -rm dist/${LIBRARY}*.jar dist/commons-validator_1_0_1.dtd
22 -rm debian/install debian/links debian/sgmlcatalogs
19 $(RM) debian/install debian/links debian/sgmlcatalogs
2320
2421 install/lib${LIBRARY}-java::
25 mv dist/${LIBRARY}.jar dist/${LIBRARY}-${VERSION}.jar
26 cp debian/conf/share/*.dtd dist/
27 echo "dist/${LIBRARY}-${VERSION}.jar usr/share/java" > debian/install
22 cp conf/share/*.dtd dist/
23 $(RM) dist/RELEASE-NOTES.txt
24 echo "dist/${LIBRARY}-${DEB_UPSTREAM_VERSION}.jar usr/share/java" > debian/install
2825 echo "dist/*.dtd usr/share/sgml/apache/jakarta/validator" >> debian/install
29 echo "usr/share/java/${LIBRARY}-${VERSION}.jar usr/share/java/${LIBRARY}.jar" > debian/links
26 echo "usr/share/java/${LIBRARY}-${DEB_UPSTREAM_VERSION}.jar usr/share/java/${LIBRARY}.jar" > debian/links
3027 echo "debian/commons-validator_1_0_1.cat /usr/share/sgml/apache/jakarta/validator/catalog" > debian/sgmlcatalogs
28
29 get-orig-source:
30 -uscan --upstream-version 0 --rename
0 version=2
1 http://www.apache.org/dist/jakarta/commons/validator/source/commons-validator-(.*)-src\.tar\.gz debian uupdate
0 version=3
1 http://www.apache.org/dist/jakarta/commons/validator/source/ \
2 commons-validator-(.*)-src\.tar\.gz debian debian/orig-tar.sh