[JBoss JIRA] (RF-13093) extendedDataTable column resizing and reordering not working on transient (stateless) views
by Salvo Isaja (JIRA)
[ https://issues.jboss.org/browse/RF-13093?page=com.atlassian.jira.plugin.s... ]
Salvo Isaja commented on RF-13093:
----------------------------------
Here is a workaround that works on RichFaces 4.3.x and JSF 2.1 (tested on RichFaces 4.3.4 on GlassFish 3.1.2.2 with Mojarra 2.1.23).
Include the following JavaScript after the standard jsf.js:
{code}
var origJsfAjaxResponse = jsf.ajax.response;
jsf.ajax.response = function response(request, context) {
var xml = request.responseXML;
var pr = xml.getElementsByTagName("partial-response")[0];
if (pr.children.length === 0) {
$(pr).append('<changes><update id="javax.faces.ViewState">stateless</update></changes>');
}
return origJsfAjaxResponse(request, context);
};
{code}
If an empty partial-response is received, it just adds an update of the stateless ViewState as it would happen with non-transient views. I've tested it as is, but I suppose the "name" attribute would be more appropriate than "id", depending on how the JSF implementations lays out the ViewState hidden.
This is not specific to rich:extendedDataTable but works around any case the server returns an empty partial-response.
> extendedDataTable column resizing and reordering not working on transient (stateless) views
> -------------------------------------------------------------------------------------------
>
> Key: RF-13093
> URL: https://issues.jboss.org/browse/RF-13093
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.2
> Environment: GlassFish 3.1.2.2 with Mojarra 2.1.23
> Reporter: Salvo Isaja
> Labels: jsf22
> Fix For: 5.0.0.Alpha2
>
>
> When turning on transient (stateless) views in recent Mojarra versions (as per JSF 2.2 specification, to my best understanding), using request scoped backing beans, javax.faces.ViewState becomes the constant "stateless". Column resizing and reordering in extendedDataTable causes an Ajax request to the server, but in this case an invalid response is sent, containing only:
> {code:xml}
> <?xml version='1.0' encoding='UTF-8'?>
> <partial-response></partial-response>
> {code}
> This causes an exception in {{jsf.js}} because the partial-response element has no children and no further JavaScript processing happens in the view until the page is reloaded. In the non-transient view case, I see a {{change}} element updating only the ViewState is returned, instead.
> Other features seem to work pretty well in stateless mode, by the way.
> Thanks
--
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, 7 months
[JBoss JIRA] (RF-13052) popupPanel: @visualOptions does not work
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13052?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13052:
---------------------------------
We have decided to hide those attributes since they can't work now and it would be risky to just remove the functionality.
We will open the issues for re-incorporating this functionality, given that nobody requests re-incorporating it, we will wait for a feature request.
> popupPanel: @visualOptions does not work
> ----------------------------------------
>
> Key: RF-13052
> URL: https://issues.jboss.org/browse/RF-13052
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 5.0.0.Alpha1
> Environment: RichFaces 5.0.0-SNAPSHOT
> Reporter: Jiří Štefek
> Assignee: Lukáš Fryč
> Fix For: 4.3.4, 5-Tracking
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> Setting @visualOptions doesn't work. Tried both settings from https://issues.jboss.org/browse/RF-2464 or https://issues.jboss.org/browse/RF-5239
> e.g.: 'left:1px'
> OR
> Is this attribute a leftover from older versions of RF (RF-3) and was replaced by attributes @*width, @*height and @style* ?
> ALSO UPDATE VDL-DOC in both cases.
--
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, 7 months
[JBoss JIRA] (RF-13107) rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13107:
----------------------------------
Assignee: Lukáš Fryč (was: Brian Leathem)
> rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: RF-13107
> URL: https://issues.jboss.org/browse/RF-13107
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Assignee: Lukáš Fryč
> Fix For: 4.3.4
>
> Attachments: bug_reproducer.zip, reproducer_ajax.zip, rf13107ajax.png
>
> Original Estimate: 1 hour, 30 minutes
> Remaining Estimate: 1 hour, 30 minutes
>
> We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
> Note that:
> 1) switchType must be set to server to ensure the A's rich:message is really not on the page.
> 2) button in B must re-render only content of B
> This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
> Please find the enclosed reproducer.
> Snipper:
> {code:xml}
> <h:form>
> <rich:tabPanel switchType="server">
> <rich:tab>
> <h:inputText id="surname" value="#{richBean.surname}">
> <f:validateLength minimum="10"/>
> </h:inputText>
> <rich:message for="surname"/>
> </rich:tab>
> <rich:tab>
> <h:panelGroup id="content">
> <h:inputText id="name" value="#{richBean.name}">
> <f:validateLength minimum="6"/>
> </h:inputText>
> <rich:message for="name"/>
> </h:panelGroup>
> <a4j:commandButton value="Submit" execute="content" render="content" />
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> {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, 7 months
[JBoss JIRA] (RF-13107) rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13107:
----------------------------------
Assignee: Brian Leathem (was: Lukáš Fryč)
> rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: RF-13107
> URL: https://issues.jboss.org/browse/RF-13107
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Attachments: bug_reproducer.zip, reproducer_ajax.zip, rf13107ajax.png
>
> Original Estimate: 1 hour, 30 minutes
> Remaining Estimate: 1 hour, 30 minutes
>
> We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
> Note that:
> 1) switchType must be set to server to ensure the A's rich:message is really not on the page.
> 2) button in B must re-render only content of B
> This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
> Please find the enclosed reproducer.
> Snipper:
> {code:xml}
> <h:form>
> <rich:tabPanel switchType="server">
> <rich:tab>
> <h:inputText id="surname" value="#{richBean.surname}">
> <f:validateLength minimum="10"/>
> </h:inputText>
> <rich:message for="surname"/>
> </rich:tab>
> <rich:tab>
> <h:panelGroup id="content">
> <h:inputText id="name" value="#{richBean.name}">
> <f:validateLength minimum="6"/>
> </h:inputText>
> <rich:message for="name"/>
> </h:panelGroup>
> <a4j:commandButton value="Submit" execute="content" render="content" />
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> {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, 7 months
[JBoss JIRA] (RF-13139) popupPanel duplicated if double clicking links for opening popup
by Valiantsin Shukaila (JIRA)
Valiantsin Shukaila created RF-13139:
----------------------------------------
Summary: popupPanel duplicated if double clicking links for opening popup
Key: RF-13139
URL: https://issues.jboss.org/browse/RF-13139
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: component-panels-layout-themes
Affects Versions: 4.3.1
Environment: tomcat 7, Richfaces 4.3.1.Final, Spring, JSF Mojarra 2.2.0
Reporter: Valiantsin Shukaila
If you create a link/button/jsFunction that should render popup panel and open it after that and will try to double click this link the two instances of the same popup panel will appear. And you will be able to close only one of them. The other will remain on the page forever.
--
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, 7 months
[JBoss JIRA] (RF-13107) rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč reassigned RF-13107:
-------------------------------
Assignee: Lukáš Fryč
> rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: RF-13107
> URL: https://issues.jboss.org/browse/RF-13107
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Assignee: Lukáš Fryč
> Fix For: 4.3.4
>
> Attachments: bug_reproducer.zip, reproducer_ajax.zip, rf13107ajax.png
>
> Original Estimate: 1 hour, 30 minutes
> Remaining Estimate: 1 hour, 30 minutes
>
> We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
> Note that:
> 1) switchType must be set to server to ensure the A's rich:message is really not on the page.
> 2) button in B must re-render only content of B
> This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
> Please find the enclosed reproducer.
> Snipper:
> {code:xml}
> <h:form>
> <rich:tabPanel switchType="server">
> <rich:tab>
> <h:inputText id="surname" value="#{richBean.surname}">
> <f:validateLength minimum="10"/>
> </h:inputText>
> <rich:message for="surname"/>
> </rich:tab>
> <rich:tab>
> <h:panelGroup id="content">
> <h:inputText id="name" value="#{richBean.name}">
> <f:validateLength minimum="6"/>
> </h:inputText>
> <rich:message for="name"/>
> </h:panelGroup>
> <a4j:commandButton value="Submit" execute="content" render="content" />
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> {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, 7 months
[JBoss JIRA] (RF-13107) rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč edited comment on RF-13107 at 8/15/13 10:08 AM:
-----------------------------------------------------------
Interesting part is here: RenderVisitContext is extended visit context which visits all components which are {{ajaxRendered}}.
We should REJECT visiting of subtrees which are not active: there is a interface for switchable panels called [{{boolean AbstractTogglePanelItemInterface#shouldProcess();}}|https://github.com/ri...].
It's [implemented by AbstractTab|https://github.com/richfaces/richfaces/blob/5.0.0.Alpha1/fram...].
I suggest to generalize this shouldProcess method to {{ActivableComponent}} or {{SwitchableComponent}} interface
----
Note that we can't use {{isRendered}}, because the component is marked as {{rendered=true}} event though it's not active.
was (Author: lfryc):
Interesting part is here: RenderVisitContext is extended visit context which visits all components which are {{ajaxRendered}}.
We should REJECT visiting of subtrees which are not active: there is a interface for switchable panels called [{{boolean AbstractTogglePanelItemInterface#shouldProcess();}}|https://github.com/ri...].
It's [implemented by AbstractTab|https://github.com/richfaces/richfaces/blob/5.0.0.Alpha1/fram...].
I suggest to generalize this shouldProcess method to {{ActivableComponent}} or {{SwitchableComponent}} interface
> rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: RF-13107
> URL: https://issues.jboss.org/browse/RF-13107
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Fix For: 4.3.4
>
> Attachments: bug_reproducer.zip, reproducer_ajax.zip, rf13107ajax.png
>
> Original Estimate: 1 hour, 30 minutes
> Remaining Estimate: 1 hour, 30 minutes
>
> We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
> Note that:
> 1) switchType must be set to server to ensure the A's rich:message is really not on the page.
> 2) button in B must re-render only content of B
> This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
> Please find the enclosed reproducer.
> Snipper:
> {code:xml}
> <h:form>
> <rich:tabPanel switchType="server">
> <rich:tab>
> <h:inputText id="surname" value="#{richBean.surname}">
> <f:validateLength minimum="10"/>
> </h:inputText>
> <rich:message for="surname"/>
> </rich:tab>
> <rich:tab>
> <h:panelGroup id="content">
> <h:inputText id="name" value="#{richBean.name}">
> <f:validateLength minimum="6"/>
> </h:inputText>
> <rich:message for="name"/>
> </h:panelGroup>
> <a4j:commandButton value="Submit" execute="content" render="content" />
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> {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, 7 months
[JBoss JIRA] (RF-13107) rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13107:
---------------------------------
Interesting part is here: RenderVisitContext is extended visit context which visits all components which are {{ajaxRendered}}.
We should REJECT visiting of subtrees which are not active: there is a interface for switchable panels called [{{boolean AbstractTogglePanelItemInterface#shouldProcess();}}|https://github.com/ri...].
It's [implemented by AbstractTab|https://github.com/richfaces/richfaces/blob/5.0.0.Alpha1/fram...].
I suggest to generalize this shouldProcess method to {{ActivableComponent}} or {{SwitchableComponent}} interface
> rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: RF-13107
> URL: https://issues.jboss.org/browse/RF-13107
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Fix For: 4.3.4
>
> Attachments: bug_reproducer.zip, reproducer_ajax.zip, rf13107ajax.png
>
> Original Estimate: 1 hour, 30 minutes
> Remaining Estimate: 1 hour, 30 minutes
>
> We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
> Note that:
> 1) switchType must be set to server to ensure the A's rich:message is really not on the page.
> 2) button in B must re-render only content of B
> This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
> Please find the enclosed reproducer.
> Snipper:
> {code:xml}
> <h:form>
> <rich:tabPanel switchType="server">
> <rich:tab>
> <h:inputText id="surname" value="#{richBean.surname}">
> <f:validateLength minimum="10"/>
> </h:inputText>
> <rich:message for="surname"/>
> </rich:tab>
> <rich:tab>
> <h:panelGroup id="content">
> <h:inputText id="name" value="#{richBean.name}">
> <f:validateLength minimum="6"/>
> </h:inputText>
> <rich:message for="name"/>
> </h:panelGroup>
> <a4j:commandButton value="Submit" execute="content" render="content" />
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> {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, 7 months
[JBoss JIRA] (RF-11469) autocomplete method does not resolve bean if ui:included
by Carlos Lambert (JIRA)
[ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.s... ]
Carlos Lambert commented on RF-11469:
-------------------------------------
Try to create the code below in any place in your code. I place it in my footer.xhtml. It's worked for me.
<h:selectOneMenu rendered="false" >
<f:ajax />
</h:selectOneMenu>
> autocomplete method does not resolve bean if ui:included
> --------------------------------------------------------
>
> Key: RF-11469
> URL: https://issues.jboss.org/browse/RF-11469
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.0.0.Final
> Reporter: u j
> Assignee: Lukáš Fryč
> Priority: Minor
> Fix For: 4.3.4, 5-Tracking
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> A bean parameter in the autocomplete method is not resolved if the rich:autocomplete is part of a ui:include.
> {code}
> <ui:include src="/searchlocation.xhtml">
> <ui:param name="bean" value="#{searchBean}" />
> </ui:include>
> {code}
> searchlocation.xhtml contains:
> {code}
> <rich:autocomplete id="cityName" mode="ajax" value="#{bean.cityName}" autocompleteMethod="#{bean.suggestCities}" />
> {code}
> The value binding works, but the binding in the autocompleteMethod gives:
> {code}
> 15:26:15,809 SEVERE [org.richfaces.log.Renderkit] (ajp-127.0.0.1-127.0.0.1-8009-1) Target Unreachable, identifier 'bean' resolved to null: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null
> at org.apache.el.parser.AstValue.getTarget(AstValue.java:75) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.parser.AstValue.invoke(AstValue.java:183) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.richfaces.renderkit.AutocompleteRendererBase.getItems(AutocompleteRendererBase.java:105) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeItems(AutocompleteRendererBase.java:160) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeMetaComponent(AutocompleteRendererBase.java:271) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> {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, 7 months
[JBoss JIRA] (RF-13109) a4j:push transaction flood
by nathan dennis (JIRA)
[ https://issues.jboss.org/browse/RF-13109?page=com.atlassian.jira.plugin.s... ]
nathan dennis closed RF-13109.
------------------------------
Resolution: Rejected
problem caused by mod_jk
> a4j:push transaction flood
> ---------------------------
>
> Key: RF-13109
> URL: https://issues.jboss.org/browse/RF-13109
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.2.2.Final, 4.2.3.Final, 4.3.1
> Environment: CHROME,Jboss 7.1.1.Final, Jboss 7.1.3.Final, CentoOS6.X, Windows 7
> Reporter: nathan dennis
> Labels: a4j:push, richfaces, waiting_on_user
> Attachments: a4jPushFlood.tar.gz
>
>
> long poll doesnt refresh at the 30 second mark. After 5 minutes, Chrome goes into meltdown, sending a transaction back to the server approx. ever 8 ms causing DOS and browser lock after about 3 seconds.
> Firefox on the other hand returns a cancelled transaction, exits abnormally, and goes back to behaving as expected with the appearance that it is working correctly.
> This took me forever to find out why this was happening as I couldn't replicate it with the showcase code... or the test project i built specifically for figuring this out. In the end I was removing one component at a time until it started working.
> The cause of the issue is found in the jboss-web.xml file. For years, I have ran apache in front of my jboss installations. I would specify root context to / and map the domain straight to it using a virtual host in the jboss server config file (regardless of the version). AJP in front and away you go. a4j:push will crash if this context is mapped to / instead of /foo.
> I'm going to attempt to attach the sample project to recreate this with. Map the alias from jboss-web.xml to a virtual server in your standalone.xml file and start it up. navigate to the consumer link at the top of the app. turn on your developer tools and wait for the chaos. at the five minute mark you are going to see death and destruction.
--
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, 7 months