-
Notifications
You must be signed in to change notification settings - Fork 19
Component / Message Association #6
Comments
Reported by rogerk |
Was assigned to rogerk |
@edburns said: |
@edburns said: |
rogerk said: |
rogerk said:
SECTION: Modified FilesM jsf-api/build.xml
A jsf-ri/systest/web/converter04.jsp
|
rogerk said: |
File: issue-6.zip.gz |
rogerk said:
SECTION: Modified FilesM jsf-api/build.xml A jsf-ri/systest/web/converter04.jsp For final EG discussion on this issue: |
rogerk said: |
File: issue-6.zip.gz |
rogerk said: |
rogerk said: |
File: issue-6.zip.gz |
@edburns said: {1} is the placeholder for "label" value here: '' {0} '' must be a Ok. RK> M jsf-api/doc/input-attrs.xml Don't check this in. Jayashri has CVS removed it. *-attrs.xml files RK> M jsf-api/doc/input-props.xml I don't like the description.
How about: A localized user presentable name for this component that can be used in messages relating to that component.RK> M jsf-api/doc/standard-html-renderkit.xml Did you edit this file directly? You have to edit the shr-base.xml one, RK> M jsf-api/src/javax/faces/convert/BigDecimalConverter.java The javadoc for the DECIMAL appears to have a parameter list ordering I know you copied and pasted the method
into every class because there was no better place to put it, RK> M jsf-api/src/javax/faces/convert/BigIntegerConverter.java
RK> M jsf-api/src/javax/faces/convert/BooleanConverter.java
RK> M jsf-api/src/javax/faces/convert/ByteConverter.java
RK> M jsf-api/src/javax/faces/convert/DateTimeConverter.java
RK> M jsf-api/src/javax/faces/validator/DoubleRangeValidator.java
RK> M jsf-api/src/javax/faces/validator/LengthValidator.java
RK> M jsf-api/src/javax/faces/validator/LongRangeValidator.java Ok. RK> M jsf-api/src/javax/faces/validator/Validator.java Ok. RK> M jsf-ri/src/javax/faces/Messages.properties
Please produce another change-bundle. Thanks, Ed |
@edburns said: |
rogerk said:
A jsf-ri/systest/web/converter04.jsp
|
rogerk said: |
File: issue-6.zip.gz |
@edburns said: |
rogerk said: |
@edburns said: |
@edburns said: |
Marked as fixed on Thursday, March 4th 2010, 6:09:25 am |
@manfredriem said: |
This issue was imported from java.net JIRA JAVASERVERFACES_SPEC_PUBLIC-6 |
A previous version of the RI incorporated the cryptic clientId in messages (for
example, validation messages) as an attempt to show which component the message
was associated with. We need to come up with a better way of doing this. More
information from the archives:
The proper way involves adding a new property to our components that
describes the "name"/"prompt"/"label" etc. that can be incorporated
into validation messages but can still be translated, user-readable
text. Doing so is obviously an API change, but there's no way to
add this feature correctly without extending the JSF API.
– Adam
Environment
Operating System: All
Platform: All
Affected Versions
[1.2]
The text was updated successfully, but these errors were encountered: