[JBoss JIRA] Created: (RF-10959) Attribute groups doesn't work in graphValidator
by Jan Jamrich (JIRA)
Attribute groups doesn't work in graphValidator
-----------------------------------------------
Key: RF-10959
URL: https://issues.jboss.org/browse/RF-10959
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: cdk, component
Affects Versions: 4.1.0.Milestone1
Environment: RichFaces 4.1.0-SNAPSHOT r.22442
Metamer 4.1.0-SNAPSHOT r.22441
Mojarra 2.0.4-b09
Apache Tomcat 6.0.29
Java(TM) SE Runtime Environment 1.6.0_19-b04 @ Linux
Chrome 12.0.718.0 @ Linux i686
Reporter: Jan Jamrich
Set attribute groups to existing group (fully qualified class (interface) name) cause no validation performed or in other cases is completely ignored.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (RF-10954) rich:graphValidator doesn't work with rich:messages globalOnly="true"
by Juergen Zimmermann (JIRA)
rich:graphValidator doesn't work with rich:messages globalOnly="true"
---------------------------------------------------------------------
Key: RF-10954
URL: https://issues.jboss.org/browse/RF-10954
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-validators
Affects Versions: 4.0.0.Final
Reporter: Juergen Zimmermann
The following tags are only working when I omit globalOnly="true". I'll attach 2 screenshots to illustrate the issue.
{{monospaced}}
<h:form id="createKundeForm">
<rich:graphValidator id="kundeValidator" value="#{kv.neuerPrivatkunde}" groups="de.swe2.kundenverwaltung.domain.PasswordGroup">
<rich:messages id="fehlermeldungPassword" globalOnly="true" />
<p/>
<h:panelGrid id="createKundeTabelle" columns="3">
<h:outputLabel id="nachnameLabel" for="nachname" value="#{msgKv['createPrivatkunde.nachname']}"/>
<h:inputText id="nachname" value="#{kv.neuerPrivatkunde.nachname}">
<rich:validator/>
</h:inputText>
<rich:messages id="fehlermeldungenNachname" for="nachname"/>
...
{{monospaced}}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (RF-8338) Some RichFaces components strip white space
by Brian Chicos (JIRA)
Some RichFaces components strip white space
-------------------------------------------
Key: RF-8338
URL: https://jira.jboss.org/jira/browse/RF-8338
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-output
Environment: RichFaces 3.3.1 libraries w/ JBOSS EAP 4.3
Reporter: Brian Chicos
Fix For: 3.3.1
RichFaces seems to be stripping out extra white space in data before sending it to the browser. I see this for data being displayed in both the rich:dataTable and rich:suggestionbox components. If there is data that has multiple spaces next to each other (ex: this data) it will get returned with a single space (ex: this data). This creates a problem especially on the rich:suggestionbox component. If the data being searched on has 2 spaces and the rich:suggestionbox returns the data with one space then the search will fail when the value is selected from the suggestionbox and the user then attempts to run the search. It seems that RichFaces should send back the data from the server without altering it and let the browser decide how to display it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (RF-10951) Dynamically created components lose CSS/JavaScript on POSTback
by Richard Kennard (JIRA)
Dynamically created components lose CSS/JavaScript on POSTback
--------------------------------------------------------------
Key: RF-10951
URL: https://issues.jboss.org/browse/RF-10951
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.0.Final
Reporter: Richard Kennard
Attachments: RichFacesDynamicComponentTest.zip
Hi guys,
First, thanks for a great release in RichFaces 4!
I have come across (what I think is) a bug and have put together a small test app that reproduces it. RichFaces components that are creating dynamically (programmatically) using...
application.createComponent( context, componentType, rendererType )
...do not automatically re-inject their CSS/JavaScript resources following a POSTback. For example, if an incorrect value is entered into a field and a validation error occurs, no programmatically created RichFaces components work when redisplayed. In fact, they may not redisplay at all (having lost their CSS).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (RF-10859) a4j:repeat broken
by wojtek k (JIRA)
a4j:repeat broken
-----------------
Key: RF-10859
URL: https://issues.jboss.org/browse/RF-10859
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 4.0.0.Final
Environment: Tomcat 6.0.32, Tomcat 7.0.11, myfaces -2.0.4, richfaces 4.0.0.Final
Reporter: wojtek k
Priority: Critical
Fix For: 4.0.1.Milestone1
<h:body>
<h:form id="test_form">
<h:messages/>
<a4j:repeat value="#{dataBean.listDataItems}" var="item">
<a4j:repeat value="#{item.list}" var="inner">
<h:inputText id="test_input" value="#{inner.status}">
</h:inputText>
<br/>
</a4j:repeat>
</a4j:repeat>
<h:commandLink value="submit" />
<br/>
<a4j:commandLink value="ajax request" render="test_form" />
</h:form>
</h:body>
listDataItems -> 2 element List
#{item.list} -> 2 element List
#{inner} -> simple class with setter and getter status.
fill inputs and click "ajax request" or "submit".
2 first inputs after submit are not updated on server side
Replace a4j:repeat with ui:repeat and it works
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (RF-10712) processUpload vs. processFileUpload - naming conventions
by Martin Kočí (JIRA)
processUpload vs. processFileUpload - naming conventions
--------------------------------------------------------
Key: RF-10712
URL: https://issues.jboss.org/browse/RF-10712
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: compatibility
Affects Versions: 4.0.0.CR1
Environment: richfaces 4.0.X branch
Reporter: Martin Kočí
Priority: Optional
method org.richfaces.event.FileUploadListener.processUpload(FileUploadEvent) should be
FileUploadListener.processFileUpload - with the "File" word in the middle.
The unspecified JSF convention is:
* logical name ("FileUpload")
* listener: logical name + "Listener" ("FileUploadListener")
* event: logical name + "Event" ("FileUploadEvent")
* method "process" + logical name ("processFileUpload")
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months