[JBoss JIRA] (RF-13025) MemoryLeak: SerializedViewCollection filled with org.richfaces.renderkit.ResourceLibraryRenderer
by Michael Heinen (JIRA)
Michael Heinen created RF-13025:
-----------------------------------
Summary: 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.3.2, 4.2.2.Final
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
Attachments: Dump20Clicks.jpg
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-13024) Kitchenksink archetype - can not built generated project - missing atmosphere version
by Juraj Húska (JIRA)
Juraj Húska created RF-13024:
--------------------------------
Summary: 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
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-13023) a4j:queue Functionality gets lost after Submit (with disabled PARTIAL_STATE_SAVING)
by Marco Goetz (JIRA)
[ https://issues.jboss.org/browse/RF-13023?page=com.atlassian.jira.plugin.s... ]
Marco Goetz updated RF-13023:
-----------------------------
Description:
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}
was:
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>
Notation Comment
{noformat}
preformatted piece of text
so *no* further _formatting_ is done here
{noformat} Makes a preformatted block of text with no syntax highlighting. All the optional parameters of {panel} macro are valid for {noformat} too.
nopanel: Embraces a block of text within a fully customizable panel. The optional parameters you can define are the following ones:
Example:
preformatted piece of text so *no* further _formatting_ is done here
{panel}Some text{
{panel:title=My Title}Some text with a title{
{panel:title=My Title| borderStyle=dashed| borderColor=#ccc| titleBGColor=#F7D6C1| bgColor=#FFFFCE}
a block of text surrounded with a *panel*
yet _another_ line
{panel} Embraces a block of text within a fully customizable panel. The optional parameters you can define are the following ones:
title: Title of the panel
borderStyle: The style of the border this panel uses (solid, dashed and other valid CSS border styles)
borderColor: The color of the border this panel uses
borderWidth: The width of the border this panel uses
bgColor: The background color of this panel
titleBGColor: The background color of the title section of this panel
Example:
My Title
a block of text surrounded with a panel
yet another line
{code:title=Bar.java|borderStyle=solid}
// Some comments here
public String getFoo()
{
return foo;
}
{code}
{code:xml}
<test>
<another tag="attribute"/>
</test>
{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:
<context-param>
<param-name>javax.faces.PARTIAL_STATE_SAVING</param-name>
<param-value>false</param-value>
</context-param>
> 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
>
> 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-13023) a4j:queue Functionality gets lost after Submit (with disabled PARTIAL_STATE_SAVING)
by Marco Goetz (JIRA)
[ https://issues.jboss.org/browse/RF-13023?page=com.atlassian.jira.plugin.s... ]
Marco Goetz updated RF-13023:
-----------------------------
Description:
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}
was:
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}
> 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
>
> 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-13023) a4j:queue Functionality gets lost after Submit (with disabled PARTIAL_STATE_SAVING)
by Marco Goetz (JIRA)
[ https://issues.jboss.org/browse/RF-13023?page=com.atlassian.jira.plugin.s... ]
Marco Goetz updated RF-13023:
-----------------------------
Description:
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>
Notation Comment
{noformat}
preformatted piece of text
so *no* further _formatting_ is done here
{noformat} Makes a preformatted block of text with no syntax highlighting. All the optional parameters of {panel} macro are valid for {noformat} too.
nopanel: Embraces a block of text within a fully customizable panel. The optional parameters you can define are the following ones:
Example:
preformatted piece of text so *no* further _formatting_ is done here
{panel}Some text{
{panel:title=My Title}Some text with a title{
{panel:title=My Title| borderStyle=dashed| borderColor=#ccc| titleBGColor=#F7D6C1| bgColor=#FFFFCE}
a block of text surrounded with a *panel*
yet _another_ line
{panel} Embraces a block of text within a fully customizable panel. The optional parameters you can define are the following ones:
title: Title of the panel
borderStyle: The style of the border this panel uses (solid, dashed and other valid CSS border styles)
borderColor: The color of the border this panel uses
borderWidth: The width of the border this panel uses
bgColor: The background color of this panel
titleBGColor: The background color of the title section of this panel
Example:
My Title
a block of text surrounded with a panel
yet another line
{code:title=Bar.java|borderStyle=solid}
// Some comments here
public String getFoo()
{
return foo;
}
{code}
{code:xml}
<test>
<another tag="attribute"/>
</test>
{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:
<context-param>
<param-name>javax.faces.PARTIAL_STATE_SAVING</param-name>
<param-value>false</param-value>
</context-param>
was:
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.
<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>
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:
<context-param>
<param-name>javax.faces.PARTIAL_STATE_SAVING</param-name>
<param-value>false</param-value>
</context-param>
> 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
>
> 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>
> Notation Comment
> {noformat}
> preformatted piece of text
> so *no* further _formatting_ is done here
> {noformat} Makes a preformatted block of text with no syntax highlighting. All the optional parameters of {panel} macro are valid for {noformat} too.
> nopanel: Embraces a block of text within a fully customizable panel. The optional parameters you can define are the following ones:
> Example:
> preformatted piece of text so *no* further _formatting_ is done here
> {panel}Some text{
> {panel:title=My Title}Some text with a title{
> {panel:title=My Title| borderStyle=dashed| borderColor=#ccc| titleBGColor=#F7D6C1| bgColor=#FFFFCE}
> a block of text surrounded with a *panel*
> yet _another_ line
> {panel} Embraces a block of text within a fully customizable panel. The optional parameters you can define are the following ones:
> title: Title of the panel
> borderStyle: The style of the border this panel uses (solid, dashed and other valid CSS border styles)
> borderColor: The color of the border this panel uses
> borderWidth: The width of the border this panel uses
> bgColor: The background color of this panel
> titleBGColor: The background color of the title section of this panel
> Example:
> My Title
> a block of text surrounded with a panel
> yet another line
> {code:title=Bar.java|borderStyle=solid}
> // Some comments here
> public String getFoo()
> {
> return foo;
> }
> {code}
> {code:xml}
> <test>
> <another tag="attribute"/>
> </test>
> {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:
> <context-param>
> <param-name>javax.faces.PARTIAL_STATE_SAVING</param-name>
> <param-value>false</param-value>
> </context-param>
--
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 Marco Goetz (JIRA)
Marco Goetz created RF-13023:
--------------------------------
Summary: 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
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.
<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>
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:
<context-param>
<param-name>javax.faces.PARTIAL_STATE_SAVING</param-name>
<param-value>false</param-value>
</context-param>
--
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 Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13018?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak reassigned RF-13018:
----------------------------------
Assignee: Jiří Štefek (was: Pavol Pitonak)
Jiri, please verify
> 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: Jiří Štefek
>
> 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