[JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to version 15.0
by Cody Lerum (JIRA)
[ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.s... ]
Cody Lerum commented on RF-13247:
---------------------------------
Wildfly is currently on 15
> 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
> Assignee: Brian Leathem
> Priority: Minor
> Fix For: 5-Tracking
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> 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
10 years, 11 months
[JBoss JIRA] (RF-13278) Add support for a 'headers' meta-component to the rich:tabPanel
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13278:
------------------------------------
Thanks for the review Lukas. Your commit is sensible.
Having thought about this issue over the break, and speaking about it with @lfryc today I've come to the following conclusions:
# The tabPanel headers should be visited in the walk of the component tree, because they are visible on the page
# Having a tabPanel@header{s} meta-component would still be useful (despite 1)
# The @active item should be the default value of the tabPanel, but should be overridden when a user sets the render attribute of the tabPanel
We will address 1) in 4.3, however 2) and 3) will be included in 4.5/5.0.
> Add support for a 'headers' meta-component to the rich:tabPanel
> ---------------------------------------------------------------
>
> Key: RF-13278
> URL: https://issues.jboss.org/browse/RF-13278
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.3.4
> Environment: java 7,
> tomcat 7, JBoss AS,
> mojarra, myfaces
> chrome, firefox
> Reporter: Alexey Shakov
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha3
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html"
> xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j"
> xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en">
> <h:head>
> </h:head>
> <h:body>
>
> <a4j:log hotkey="M" mode="popup" />
> <h:form id="form" prependId="false">
> <rich:tabPanel id="tabPanel">
> <rich:tab header="tab 1">
> <a4j:commandLink value="click me" action="#{testBean.put('clicks',testBean.clicks + 1)}" render="label" execute="@this" />
> </rich:tab>
> <rich:tab>
> <f:facet name="header">
> <h:outputText id="label" value="#{testBean.clicks} clicks" />
> </f:facet>
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> </h:body>
> </html>
> {code}
> testBean is a simple session-scoped HashMap.
--
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
10 years, 11 months
[JBoss JIRA] (RF-9306) ComponentControl can't control DataScroller nested in iteration component
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-9306?page=com.atlassian.jira.plugin.sy... ]
Jiří Štefek resolved RF-9306.
-----------------------------
Fix Version/s: (was: 5-Future)
Resolution: Out of Date
Works in latest 5.X Metamer
> ComponentControl can't control DataScroller nested in iteration component
> -------------------------------------------------------------------------
>
> Key: RF-9306
> URL: https://issues.jboss.org/browse/RF-9306
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-misc
> Affects Versions: 4.0.0.Milestone3
> Environment: * RichFaces Core Implementation by JBoss, a division of Red Hat, Inc., version v.4.0.0-SNAPSHOT SVN r.19085
> * Metamer: RichFaces Testing Application by JBoss, a division of Red Hat, Inc., version 4.0.0-SNAPSHOT SVN r. 19087
> * Java(TM) SE Runtime Environment 1.6.0_20-b02
> * Linux 2.6.31-22-generic
> * Mojarra 2.0.2-FCS
> * Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 Ubuntu/9.10 (karmic) Firefox/3.6.8
> Reporter: Lukáš Fryč
>
> Works great for h:dataTable and ui:repeat,
> but not for a4j:repeat or rich:dataTable.
--
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
10 years, 11 months
[JBoss JIRA] (RF-13278) Add support for a 'headers' meta-component to the rich:tabPanel
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13278:
---------------------------------
Hey Brian, I made one correction to the branch, could you please review?
https://github.com/richfaces/richfaces/commit/54935637cb5c100bc2529c9e5d2...
Otherwise it looks fine.
----
My 0.02$ to naming:
should the meta component be:
1) tabPanel's {{header}} (that contains headers of all tabs)
2) tabPanel's {{headers}}
I would align naming with table's {{header}}, but it's personal preference.
> Add support for a 'headers' meta-component to the rich:tabPanel
> ---------------------------------------------------------------
>
> Key: RF-13278
> URL: https://issues.jboss.org/browse/RF-13278
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.3.4
> Environment: java 7,
> tomcat 7, JBoss AS,
> mojarra, myfaces
> chrome, firefox
> Reporter: Alexey Shakov
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha3
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html"
> xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j"
> xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en">
> <h:head>
> </h:head>
> <h:body>
>
> <a4j:log hotkey="M" mode="popup" />
> <h:form id="form" prependId="false">
> <rich:tabPanel id="tabPanel">
> <rich:tab header="tab 1">
> <a4j:commandLink value="click me" action="#{testBean.put('clicks',testBean.clicks + 1)}" render="label" execute="@this" />
> </rich:tab>
> <rich:tab>
> <f:facet name="header">
> <h:outputText id="label" value="#{testBean.clicks} clicks" />
> </f:facet>
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> </h:body>
> </html>
> {code}
> testBean is a simple session-scoped HashMap.
--
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
10 years, 11 months