[JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to version 15.0
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13247:
-------------------------------
Sprint: RichFaces 4.3.5 Sprint 1
> Upgrade the RichFaces guava dependency to version 15.0
> ------------------------------------------------------
>
> Key: RF-13247
> URL: https://issues.jboss.org/browse/RF-13247
> Project: RichFaces
> Issue Type: Component Upgrade
> Security Level: Public(Everyone can see)
> Components: third-party
> Reporter: Jeremy Landis
> Priority: Minor
> Fix For: 4.3.5
>
>
> Upgrading to guava 15 from 14.0.1 causes this richfaces error. I have not looked into this further but wanted to put it out there as an issue.
> Caused by: java.lang.IllegalAccessError: tried to access method com.google.common.collect.MapMaker.makeComputingMap(Lcom/google/common/base/Function;)Ljava/util/concurrent/ConcurrentMap; from class org.richfaces.resource.ResourceLibraryFactoryImpl
--
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, 4 months
[JBoss JIRA] (RF-13390) Region fails to render after ajax request
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13390?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13390:
-------------------------------
Fix Version/s: (was: 4.3.5)
> Region fails to render after ajax request
> -----------------------------------------
>
> Key: RF-13390
> URL: https://issues.jboss.org/browse/RF-13390
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0
> Wildfly 8.0.0.Beta2-SNAPSHOT
> Mojarra 2.2.4-jbossorg-1 20131017-1524
> Reporter: Cody Lerum
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> When
> {code}
> <r:region>
> <h:inputText>
> <r:ajax execute="@this" render="@region" />
> </h:inputText>
> </r:region>
> {code}
> A partial response seems to be generated with the correct content but the dom is not updated
--
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, 4 months
[JBoss JIRA] (RF-13093) extendedDataTable column resizing and reordering not working on transient (stateless) views
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13093?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13093:
-------------------------------
Fix Version/s: (was: 4.3.5)
> 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.Alpha3
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> 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, 4 months