Will do
...
... done. Created JIRA ticket: MYFACES-2386
Regards,
Jan-Kees
2009/10/21 Matthias Wessendorf mat...@apache.org:
On Wed, Oct 21, 2009 at 12:20 PM, Jan-Kees van Andel
jankeesvanan...@gmail.com wrote:
2009/10/21 Matthias Wessendorf mat...@apache.org:
On Wed, Oct 21, 2009 at
Well, we can definitely not add a public field to the API which is not
specified. The question is only if maybe the RI added some public
field which was not specified - then this could be a spec bug.
regards,
Martin
On 10/20/09, Matthias Wessendorf mat...@apache.org wrote:
I think the question
Nope, I checked the JavaDoc (I am not looking at the code, for a
couple of reasons),
and there is nothing like that.
So, maybe there is need for such an helper, as there are already today
- as a matter
of practical use - some issues with the current spec.
Let me file an ER for this.
-Matthias
I've added those constants. Can't remember why I made them public. I
assume because they are used by the BeanValidator class.
The reason to make them static final with the static initializer block
was because it made them easy to use and also because it's very
efficient (performance wise).
Maybe
On Wed, Oct 21, 2009 at 9:36 AM, Jan-Kees van Andel
jankeesvanan...@gmail.com wrote:
I've added those constants. Can't remember why I made them public. I
assume because they are used by the BeanValidator class.
The reason to make them static final with the static initializer block
was because
2009/10/21 Matthias Wessendorf mat...@apache.org:
On Wed, Oct 21, 2009 at 9:36 AM, Jan-Kees van Andel
jankeesvanan...@gmail.com wrote:
I've added those constants. Can't remember why I made them public. I
assume because they are used by the BeanValidator class.
The reason to make them static
