[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
13 years, 6 months
[JBoss JIRA] Deleted: (RF-10975) FileUpload integration issue with Tomahawk20
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-10975?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč deleted RF-10975:
----------------------------
> FileUpload integration issue with Tomahawk20
> --------------------------------------------
>
> Key: RF-10975
> URL: https://issues.jboss.org/browse/RF-10975
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: RichFaces 4.1.0-SNAPSHOT r.22477
> Mojarra 2.0.4-b09
> Apache Tomcat 6.0.29
> OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux
> Chrome 11.0.696.57 @ Linux i686
> Reporter: Lukáš Fryč
>
> Add following dependency to Metamer,
> {code:XML}
> <dependency>
> <groupId>org.apache.myfaces.tomahawk</groupId>
> <artifactId>tomahawk20</artifactId>
> <version>1.1.10</version>
> <type>jar</type>
> <scope>runtime</scope>
> </dependency>
> {code}
> You can see following in the server log:
> {code}
> WARNING: JSF1091: No mime type could be found for file fileUploadProgress. To resolve this, add a mime-type mapping to the applications web.xml.
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] Created: (RF-10975) FileUpload integration issue with Tomahawk20
by Lukáš Fryč (JIRA)
FileUpload integration issue with Tomahawk20
--------------------------------------------
Key: RF-10975
URL: https://issues.jboss.org/browse/RF-10975
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: compatibility
Affects Versions: 4.0.0.Final
Environment: RichFaces 4.1.0-SNAPSHOT r.22477
Mojarra 2.0.4-b09
Apache Tomcat 6.0.29
OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux
Chrome 11.0.696.57 @ Linux i686
Reporter: Lukáš Fryč
Add following dependency to Metamer,
{code:XML}
<dependency>
<groupId>org.apache.myfaces.tomahawk</groupId>
<artifactId>tomahawk20</artifactId>
<version>1.1.10</version>
<type>jar</type>
<scope>runtime</scope>
</dependency>
{code}
You can see following in the server log:
{code}
WARNING: JSF1091: No mime type could be found for file fileUploadProgress. To resolve this, add a mime-type mapping to the applications web.xml.
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 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
13 years, 6 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
13 years, 7 months
[JBoss JIRA] Created: (RF-10467) richfaces-showcase: Client Side Disabling works only for first request
by Lukas Fryc (JIRA)
richfaces-showcase: Client Side Disabling works only for first request
----------------------------------------------------------------------
Key: RF-10467
URL: https://issues.jboss.org/browse/RF-10467
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: examples, showcase
Affects Versions: 4.0.0.Milestone6
Environment: apache-tomcat-7.0.6
OpenJDK Runtime Environment (IcedTea6 1.9.5) (6b20-1.9.5-0ubuntu1~10.04.1)
Chrome / Firefox 3.6.13
Reporter: Lukas Fryc
1. open rich:calendar - Client Side Styling/Disablement
2. open calendar by clicking on icon
3. click on some date
4. open calendar again
5. click on some date
FAIL: no date is clickable and no styling/disablement applied
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months