[JBoss JIRA] (RF-12781) The kitchensink-rf quickstart uses obsolete property names and values
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12781?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12781.
--------------------------------
Resolution: Done
Resolved with RF-12791
> The kitchensink-rf quickstart uses obsolete property names and values
> ----------------------------------------------------------------------
>
> Key: RF-12781
> URL: https://issues.jboss.org/browse/RF-12781
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Reporter: Sande Gilda
> Assignee: Brian Leathem
> Fix For: 4.3.1
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> The POM file currently contains:
> {code}
> <jboss.as.plugin.version>7.1.1.Final</jboss.as.plugin.version>
> {code}
> The correct name/value is:
> {code}
> <version.org.jboss.as.plugins.maven.plugin>7.3.Final</version.org.jboss.as.plugins.maven.plugin>
> {code}
> It also defines:
> {code}
> <!-- Define the version of the JBoss BOMs we want to import. The
> JBoss BOMs specify tested stacks. -->
> <jboss.bom.version>1.0.0.Final</jboss.bom.version>
> <!-- Alternatively, comment out the above line, and un-comment the
> line below to use version 1.0.2.Final-redhat-1 which is a release
> certified to work with JBoss EAP 6. It requires you have access
> to the JBoss EAP 6 maven repository. -->
> <!-- <jboss.bom.version>1.0.2.Final-redhat-1</jboss.bom.version> -->
> {code}
> That section should be defined as follows:
> {code}
> <!-- Define the version of the JBoss BOMs we want to import to specify tested stacks. -->
> <version.org.jboss.bom>1.0.4.Final</version.org.jboss.bom>
> <!-- Alternatively, comment out the above line, and un-comment the
> line below to use version 1.0.4.Final-redhat-1 which is a release certified
> to work with JBoss EAP 6. It requires you have access to the JBoss EAP 6
> maven repository. -->
> <!-- <version.org.jboss.bom>1.0.4.Final-redhat-1</version.org.jboss.bom> -->
> {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
11 years, 9 months
[JBoss JIRA] (RF-12750) extendedDataTable make facet header clickable using default sortHandle
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12750?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12750.
--------------------------------
Resolution: Done
Made the entire column header listen for the click event when builtin sorting is enabled.
> extendedDataTable make facet header clickable using default sortHandle
> ----------------------------------------------------------------------
>
> Key: RF-12750
> URL: https://issues.jboss.org/browse/RF-12750
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.0.M3
> Reporter: Marc A. Harnos
> Assignee: Brian Leathem
> Priority: Minor
> Labels: datatable, extendedDataTable, extended_datatable, extendeddatatable
> Fix For: 4.3.1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> It would be nice, if the default sort handler on an extendedDataTable would also make the facet header clickable (like the sorting arrows span).
--
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
11 years, 9 months
[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
by Tali Han (JIRA)
[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ]
Tali Han commented on RF-12765:
-------------------------------
How did you test it? What setup do you have?
> Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
> ----------------------------------------------------------------------------
>
> Key: RF-12765
> URL: https://issues.jboss.org/browse/RF-12765
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.0.M3, 4.3.0.CR2
> Environment: Linux, windows any browser Chrom, Mozilla
> Reporter: Tali Han
> Assignee: Lukáš Fryč
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Rih:Tab panel functionality is broken.
> If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again.
> Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour.
> richfaces/tabPanel/samples/dynamic-sample.xhtml
> {code}
> <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}">
> <ui:remove>
> <rich:tab header="Static">
> <p>This tab is static one.</p>
>
> <p>All of the following tabs are dynamically generated using <b>a4j:repeat</b>.</p>
> </rich:tab>
> </ui:remove>
> <a4j:repeat value="#{skinBean.skins}" var="skinName">
>
> <rich:tab header="#{skinName}" name="#{skinName}">
> <f:facet name="header">#{skinName}</f:facet>
> <i> All the controls below are just standard JSF components skinned with RichFaces: </i>
> <hr />
> <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
11 years, 9 months
[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
by Tali Han (JIRA)
[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ]
Tali Han edited comment on RF-12765 at 2/26/13 11:15 PM:
---------------------------------------------------------
Hi Lukas,
It is very strange.
We have 3 people in our group . We all can reproduce it easily. We all have slightly different versions of Linux. But we all have TOMCAT 6, we all tested it with firefox and chrome.
I can gzip my tomcat with richfaces war if you want. Where should I upload it?
Anyway let me know how I can help.
was (Author: talik):
Hi Lukas,
It is very strange.
We have 3 people in our group . We all can reproduce it. We all have slightly different versions of Linux. But we all have TOMCAT 6, we all tested it with firefox and chrome.
I can gzip my tomcat with richfaces war if you want. Where should I upload it?
Anyway let me know how I can help.
> Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
> ----------------------------------------------------------------------------
>
> Key: RF-12765
> URL: https://issues.jboss.org/browse/RF-12765
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.0.M3, 4.3.0.CR2
> Environment: Linux, windows any browser Chrom, Mozilla
> Reporter: Tali Han
> Assignee: Lukáš Fryč
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Rih:Tab panel functionality is broken.
> If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again.
> Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour.
> richfaces/tabPanel/samples/dynamic-sample.xhtml
> {code}
> <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}">
> <ui:remove>
> <rich:tab header="Static">
> <p>This tab is static one.</p>
>
> <p>All of the following tabs are dynamically generated using <b>a4j:repeat</b>.</p>
> </rich:tab>
> </ui:remove>
> <a4j:repeat value="#{skinBean.skins}" var="skinName">
>
> <rich:tab header="#{skinName}" name="#{skinName}">
> <f:facet name="header">#{skinName}</f:facet>
> <i> All the controls below are just standard JSF components skinned with RichFaces: </i>
> <hr />
> <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
11 years, 9 months
[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
by Tali Han (JIRA)
[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ]
Tali Han commented on RF-12765:
-------------------------------
Hi Lukas,
It isa very strange.
We have 3 people in our group . We all can reproduce it. We all have slightly different versions of Linux. But we all have TOMCAT 6, we all tested it with firefox and chrome.
I can gzip my tomcat with richfaces war if you want. Where should I upload it?
Anyway let me know how I can help.
> Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
> ----------------------------------------------------------------------------
>
> Key: RF-12765
> URL: https://issues.jboss.org/browse/RF-12765
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.0.M3, 4.3.0.CR2
> Environment: Linux, windows any browser Chrom, Mozilla
> Reporter: Tali Han
> Assignee: Lukáš Fryč
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Rih:Tab panel functionality is broken.
> If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again.
> Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour.
> richfaces/tabPanel/samples/dynamic-sample.xhtml
> {code}
> <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}">
> <ui:remove>
> <rich:tab header="Static">
> <p>This tab is static one.</p>
>
> <p>All of the following tabs are dynamically generated using <b>a4j:repeat</b>.</p>
> </rich:tab>
> </ui:remove>
> <a4j:repeat value="#{skinBean.skins}" var="skinName">
>
> <rich:tab header="#{skinName}" name="#{skinName}">
> <f:facet name="header">#{skinName}</f:facet>
> <i> All the controls below are just standard JSF components skinned with RichFaces: </i>
> <hr />
> <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
11 years, 9 months
[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
by Tali Han (JIRA)
[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ]
Tali Han edited comment on RF-12765 at 2/26/13 11:14 PM:
---------------------------------------------------------
Hi Lukas,
It is very strange.
We have 3 people in our group . We all can reproduce it. We all have slightly different versions of Linux. But we all have TOMCAT 6, we all tested it with firefox and chrome.
I can gzip my tomcat with richfaces war if you want. Where should I upload it?
Anyway let me know how I can help.
was (Author: talik):
Hi Lukas,
It isa very strange.
We have 3 people in our group . We all can reproduce it. We all have slightly different versions of Linux. But we all have TOMCAT 6, we all tested it with firefox and chrome.
I can gzip my tomcat with richfaces war if you want. Where should I upload it?
Anyway let me know how I can help.
> Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
> ----------------------------------------------------------------------------
>
> Key: RF-12765
> URL: https://issues.jboss.org/browse/RF-12765
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.0.M3, 4.3.0.CR2
> Environment: Linux, windows any browser Chrom, Mozilla
> Reporter: Tali Han
> Assignee: Lukáš Fryč
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Rih:Tab panel functionality is broken.
> If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again.
> Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour.
> richfaces/tabPanel/samples/dynamic-sample.xhtml
> {code}
> <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}">
> <ui:remove>
> <rich:tab header="Static">
> <p>This tab is static one.</p>
>
> <p>All of the following tabs are dynamically generated using <b>a4j:repeat</b>.</p>
> </rich:tab>
> </ui:remove>
> <a4j:repeat value="#{skinBean.skins}" var="skinName">
>
> <rich:tab header="#{skinName}" name="#{skinName}">
> <f:facet name="header">#{skinName}</f:facet>
> <i> All the controls below are just standard JSF components skinned with RichFaces: </i>
> <hr />
> <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
11 years, 9 months
[JBoss JIRA] (RF-12750) extendedDataTable make facet header clickable using default sortHandle
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12750?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-12750:
----------------------------------
Assignee: Brian Leathem
> extendedDataTable make facet header clickable using default sortHandle
> ----------------------------------------------------------------------
>
> Key: RF-12750
> URL: https://issues.jboss.org/browse/RF-12750
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.0.M3
> Reporter: Marc A. Harnos
> Assignee: Brian Leathem
> Priority: Minor
> Labels: datatable, extendedDataTable, extended_datatable, extendeddatatable
> Fix For: 4.3.1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> It would be nice, if the default sort handler on an extendedDataTable would also make the facet header clickable (like the sorting arrows span).
--
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
11 years, 9 months
[JBoss JIRA] (RF-12781) The kitchensink-rf quickstart uses obsolete property names and values
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12781?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-12781:
----------------------------------
Assignee: Brian Leathem
> The kitchensink-rf quickstart uses obsolete property names and values
> ----------------------------------------------------------------------
>
> Key: RF-12781
> URL: https://issues.jboss.org/browse/RF-12781
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Reporter: Sande Gilda
> Assignee: Brian Leathem
> Fix For: 4.3.1
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> The POM file currently contains:
> {code}
> <jboss.as.plugin.version>7.1.1.Final</jboss.as.plugin.version>
> {code}
> The correct name/value is:
> {code}
> <version.org.jboss.as.plugins.maven.plugin>7.3.Final</version.org.jboss.as.plugins.maven.plugin>
> {code}
> It also defines:
> {code}
> <!-- Define the version of the JBoss BOMs we want to import. The
> JBoss BOMs specify tested stacks. -->
> <jboss.bom.version>1.0.0.Final</jboss.bom.version>
> <!-- Alternatively, comment out the above line, and un-comment the
> line below to use version 1.0.2.Final-redhat-1 which is a release
> certified to work with JBoss EAP 6. It requires you have access
> to the JBoss EAP 6 maven repository. -->
> <!-- <jboss.bom.version>1.0.2.Final-redhat-1</jboss.bom.version> -->
> {code}
> That section should be defined as follows:
> {code}
> <!-- Define the version of the JBoss BOMs we want to import to specify tested stacks. -->
> <version.org.jboss.bom>1.0.4.Final</version.org.jboss.bom>
> <!-- Alternatively, comment out the above line, and un-comment the
> line below to use version 1.0.4.Final-redhat-1 which is a release certified
> to work with JBoss EAP 6. It requires you have access to the JBoss EAP 6
> maven repository. -->
> <!-- <version.org.jboss.bom>1.0.4.Final-redhat-1</version.org.jboss.bom> -->
> {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
11 years, 9 months