[JBoss JIRA] (RF-13024) Kitchenksink archetype - can not built generated project - missing atmosphere version
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13024?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13024:
-------------------------------
Sprint: 5.0.0.Alpha1
> Kitchenksink archetype - can not built generated project - missing atmosphere version
> -------------------------------------------------------------------------------------
>
> Key: RF-13024
> URL: https://issues.jboss.org/browse/RF-13024
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: archetype, build/distribution
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Priority: Blocker
> Fix For: 5.0.0.Alpha1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The project generated from _kitchensink_ archetype can not be built, because there is missing version for {{org.atmosphere:atmosphere-runtime:jar}}.
> The {{atmosphere}} was removed from {{bom}} and the {{push-depchain}} was introduced. It needs to be introduced in the kitchensink as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (RF-13021) Simpleapp archetype does not work on Tomcat
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13021?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13021:
-------------------------------
Original Estimate: 1 hour
Remaining Estimate: 1 hour
> Simpleapp archetype does not work on Tomcat
> -------------------------------------------
>
> Key: RF-13021
> URL: https://issues.jboss.org/browse/RF-13021
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: archetype
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Assignee: Lukáš Fryč
> Priority: Blocker
> Fix For: 5.0.0.Alpha1
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> The simple app archetype does not work on Tomcats. It works on JBoss AS.
> The only notable error is this one from server log:
> {code}
> INFO: validateJarFile(/home/jhuska/workspace_jbossToolsTesting/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/rf500Alpha1testingMvn/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class
> May 27, 2013 5:37:13 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
> INFO: validateJarFile(/home/jhuska/workspace_jbossToolsTesting/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/rf500Alpha1testingMvn/WEB-INF/lib/servlet-api-2.5.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
> {code}
> The issue IMHO relates to RF-12998, which was already solved for showcase.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (RF-13023) a4j:queue Functionality gets lost after Submit (with disabled PARTIAL_STATE_SAVING)
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13023?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13023:
-------------------------------
Labels: myfaces partial_state_saving (was: )
> a4j:queue Functionality gets lost after Submit (with disabled PARTIAL_STATE_SAVING)
> -----------------------------------------------------------------------------------
>
> Key: RF-13023
> URL: https://issues.jboss.org/browse/RF-13023
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.2
> Environment: MyFaces 2.1.11
> Richfaces 4.3.2.Final.
> Reproducible with Chrome, FF, IE10
> Reporter: Marco Goetz
> Labels: myfaces, partial_state_saving
>
> I have noticed that the requestDelay settings or the whole a4j:queue is not working after a page submit.
> When I open the view the requestDelay works fine and 4 seconds after a keyup event in the input field, an ajax request is processed.
> But when I press the commandButton the queue functionality is lost and ajax requests are performed immediately without a delay.
>
> {code:xml}
> <h:body>
> <h:form id="form">
> <h:commandButton value="Button" />
> <a4j:queue requestDelay="4000"/>
> <h:inputText>
> <a4j:ajax event="keyup" ></a4j:ajax>
> </h:inputText>
> </h:form>
> </h:body>
> {code}
>
> The same problem exists when I use <a4j:attachQueue>
> I found out that this issue is related with PARTIAL_STATE_SAVING context parameter in the web.xml.
> I need to disable this paramter otherwise some views won't work correctly.
> If this paramter is enabled the a4j:queue works like it should.
> My web.xml:
> {code:xml}
> <context-param>
> <param-name>javax.faces.PARTIAL_STATE_SAVING</param-name>
> <param-value>false</param-value>
> </context-param>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (RF-13025) MemoryLeak: SerializedViewCollection filled with org.richfaces.renderkit.ResourceLibraryRenderer
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13025?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13025:
-------------------------------
Fix Version/s: 5.0.0.Alpha2
> MemoryLeak: SerializedViewCollection filled with org.richfaces.renderkit.ResourceLibraryRenderer
> ------------------------------------------------------------------------------------------------
>
> Key: RF-13025
> URL: https://issues.jboss.org/browse/RF-13025
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 4.2.2.Final, 4.3.2
> Environment: Richfaces 4.2.2 (happens also with Richfaces 4.3.2)
> myfaces 2.1.10 (happens also with 2.1.11)
> Tomcat 6.0.36
> Reporter: Michael Heinen
> Fix For: 5.0.0.Alpha2
>
> Attachments: Dump20Clicks.jpg, Dump2Clicks.jpg, zSessionLeak.war
>
>
> The SerializedViewCollection grows in my application with every ajax call.
> A new reference to a "org.richfaces.renderkit.ResourceLibraryRenderer" is added each time.
> This happens only if the page contains a <a4j:ajax> tag.
> Without any <a4j:ajax> tag the SerializedViewCollection doesn't grow!
> A sample application will be attached as well as screenshots with the heap dumps.
> The Heapdumps are also available.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (RF-13023) a4j:queue Functionality gets lost after Submit (with disabled PARTIAL_STATE_SAVING)
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13023?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13023:
-------------------------------
Fix Version/s: 5-Tracking
> a4j:queue Functionality gets lost after Submit (with disabled PARTIAL_STATE_SAVING)
> -----------------------------------------------------------------------------------
>
> Key: RF-13023
> URL: https://issues.jboss.org/browse/RF-13023
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.2
> Environment: MyFaces 2.1.11
> Richfaces 4.3.2.Final.
> Reproducible with Chrome, FF, IE10
> Reporter: Marco Goetz
> Labels: myfaces, partial_state_saving
> Fix For: 5-Tracking
>
>
> I have noticed that the requestDelay settings or the whole a4j:queue is not working after a page submit.
> When I open the view the requestDelay works fine and 4 seconds after a keyup event in the input field, an ajax request is processed.
> But when I press the commandButton the queue functionality is lost and ajax requests are performed immediately without a delay.
>
> {code:xml}
> <h:body>
> <h:form id="form">
> <h:commandButton value="Button" />
> <a4j:queue requestDelay="4000"/>
> <h:inputText>
> <a4j:ajax event="keyup" ></a4j:ajax>
> </h:inputText>
> </h:form>
> </h:body>
> {code}
>
> The same problem exists when I use <a4j:attachQueue>
> I found out that this issue is related with PARTIAL_STATE_SAVING context parameter in the web.xml.
> I need to disable this paramter otherwise some views won't work correctly.
> If this paramter is enabled the a4j:queue works like it should.
> My web.xml:
> {code:xml}
> <context-param>
> <param-name>javax.faces.PARTIAL_STATE_SAVING</param-name>
> <param-value>false</param-value>
> </context-param>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (RF-13018) a4j:commandButton wrong actions performed
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13018?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13018:
-------------------------------
Workaround Description: Don't use type='button'
> a4j:commandButton wrong actions performed
> -----------------------------------------
>
> Key: RF-13018
> URL: https://issues.jboss.org/browse/RF-13018
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.2.3.Final, 4.3.2
> Environment: Server: Fedora 17, Jboss AS 7.1.1.Final, Jboss EAP 6.1.0.Beta, Java 1.7.0_15
> Browsers: Chrome 26 and Chrome 27 on (Linux & Windows 7), Firefox 20.0 (Linux & Windows 7), IE 9
> Reporter: Rob Hare
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
> Attachments: RF-13018.zip
>
>
> When an a4j commponent (a4j:commandButton, a4j:jsFunction) is activated, actions of other a4j:commandButtons on the page with type=button will be fired.
> For example, pressing either button in the following code will cause both richBean.function1() and richBean.function2() actions.
> {noformat}
> <h:form id="testForm">
> <a4j:commandButton id="button1" type="button" value="Button 1"
> action="#{richBean.function1}" />
> <a4j:commandButton id="button2" type="button" value="Button 2"
> action="#{richBean.function2}" />
> </h:form>
> {noformat}
> Note, if one of the a4j:commandButton is marked immediate, then only one action (possibly the wrong action) will be performed and block others. For instance if an a4j:jsFunction action was being triggered, the a4j:commandButton action may occur making appear that the a4j:jsFunction failed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (RF-13018) a4j:commandButton wrong actions performed
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13018?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13018:
-------------------------------
Fix Version/s: 5.0.0.Alpha2
> a4j:commandButton wrong actions performed
> -----------------------------------------
>
> Key: RF-13018
> URL: https://issues.jboss.org/browse/RF-13018
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.2.3.Final, 4.3.2
> Environment: Server: Fedora 17, Jboss AS 7.1.1.Final, Jboss EAP 6.1.0.Beta, Java 1.7.0_15
> Browsers: Chrome 26 and Chrome 27 on (Linux & Windows 7), Firefox 20.0 (Linux & Windows 7), IE 9
> Reporter: Rob Hare
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
> Attachments: RF-13018.zip
>
>
> When an a4j commponent (a4j:commandButton, a4j:jsFunction) is activated, actions of other a4j:commandButtons on the page with type=button will be fired.
> For example, pressing either button in the following code will cause both richBean.function1() and richBean.function2() actions.
> {noformat}
> <h:form id="testForm">
> <a4j:commandButton id="button1" type="button" value="Button 1"
> action="#{richBean.function1}" />
> <a4j:commandButton id="button2" type="button" value="Button 2"
> action="#{richBean.function2}" />
> </h:form>
> {noformat}
> Note, if one of the a4j:commandButton is marked immediate, then only one action (possibly the wrong action) will be performed and block others. For instance if an a4j:jsFunction action was being triggered, the a4j:commandButton action may occur making appear that the a4j:jsFunction failed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (RF-13028) Warning when deploying showcase - SelectLabelValueValidator class not present
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13028?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč reassigned RF-13028:
-------------------------------
Assignee: Lukáš Fryč
> Warning when deploying showcase - SelectLabelValueValidator class not present
> -----------------------------------------------------------------------------
>
> Key: RF-13028
> URL: https://issues.jboss.org/browse/RF-13028
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: regression, showcase
> Affects Versions: 5.0.0.Alpha1
> Environment: JBoss AS 7.1.1.Final
> Reporter: Juraj Húska
> Assignee: Lukáš Fryč
> Priority: Minor
> Fix For: 5.0.0.Alpha1
>
>
> There is following warning when deploying showcase:
> {code}
> 11:54:45,575 WARNING [org.richfaces.log.Config] (MSC service thread 1-4) Found JavaScript function definition for class org.richfaces.validator.SelectLabelValueValidator, but that class is not presented
> {code}
> The reason is changed package for {{SelectLabelValueValidator}}.
> The new one is: {{org.richfaces.ui.select.select}}
> The demos for {{select components}} seems to work correctly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (RF-13028) Warning when deploying showcase - SelectLabelValueValidator class not present
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13028?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13028:
-------------------------------
Fix Version/s: 5.0.0.Alpha1
> Warning when deploying showcase - SelectLabelValueValidator class not present
> -----------------------------------------------------------------------------
>
> Key: RF-13028
> URL: https://issues.jboss.org/browse/RF-13028
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: regression, showcase
> Affects Versions: 5.0.0.Alpha1
> Environment: JBoss AS 7.1.1.Final
> Reporter: Juraj Húska
> Priority: Minor
> Fix For: 5.0.0.Alpha1
>
>
> There is following warning when deploying showcase:
> {code}
> 11:54:45,575 WARNING [org.richfaces.log.Config] (MSC service thread 1-4) Found JavaScript function definition for class org.richfaces.validator.SelectLabelValueValidator, but that class is not presented
> {code}
> The reason is changed package for {{SelectLabelValueValidator}}.
> The new one is: {{org.richfaces.ui.select.select}}
> The demos for {{select components}} seems to work correctly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (RF-13019) Placeholder disappears after form reset
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13019?page=com.atlassian.jira.plugin.s... ]
Michal Petrov reassigned RF-13019:
----------------------------------
Assignee: Michal Petrov
> Placeholder disappears after form reset
> ---------------------------------------
>
> Key: RF-13019
> URL: https://issues.jboss.org/browse/RF-13019
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.2
> Reporter: Atanu Mukherjee
> Assignee: Michal Petrov
> Fix For: 5-Tracking
>
>
> I have the following code inside a form -
> {code}
> <h:inputText id="userName" styleClass="span6" >
> <f:validateLength maximum="255"/>
> <rich:placeholder value="ID / Username" />
> </h:inputText>
> {code}
> The placeholder value disappears if I reset the form. Comes back up after I click the control and tab out.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months