[JBoss JIRA] (RF-12523) a4j:commandButton generates duplicated context path using a resource value expression within image attribute
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12523?page=com.atlassian.jira.plugin.s... ]
Juraj Húska closed RF-12523.
----------------------------
Verified. Closing.
> a4j:commandButton generates duplicated context path using a resource value expression within image attribute
> ------------------------------------------------------------------------------------------------------------
>
> Key: RF-12523
> URL: https://issues.jboss.org/browse/RF-12523
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 4.2.2.Final, 4.3.0.M1
> Environment: Windows 7 Professional, JBoss AS 6.1.0.Final, Mojarra 2.1.7
> Reporter: Andreas Owczarek
> Assignee: Lukáš Fryč
> Priority: Minor
> Labels: testcase_provided
> Fix For: 4.3.1
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> a4j:commandButton produces an extra context path prefix for the image resource path, when it is used with the value expression {code}#{resource['library:file']}{code} for the image attribute.
> {code:xml|title=Example code}
> <a4j:commandButton image="#{resource['icons:icon.gif']}" value="#{resource['icons:icon.gif']}"/>
> {code}
> {code:xml|title=Generated Result code}
> <input type="image" alt="/com.example.my.context.path/faces/javax.faces.resource/icon.gif?ln=icons" src="/com.example.my.context.path/com.example.my.context.path/faces/javax.faces.resource/icon.gif?ln=icons" value="/com.example.my.context.path/faces/javax.faces.resource/icon.gif?ln=icons" onclick="RichFaces.ajax("j_idt76",event,{"incId":"1"} );return false;" name="j_idt76" id="j_idt76">
> {code}
> The generated code show the correct value for the expression within the generated button label, but the image could not be located correctly because of the wrong generated image resource path.
--
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, 10 months
[JBoss JIRA] (RF-12781) The kitchensink-rf quickstart uses obsolete property names and values
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12781?page=com.atlassian.jira.plugin.s... ]
Juraj Húska closed RF-12781.
----------------------------
Verified. Closing.
> 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, 10 months
[JBoss JIRA] (RF-12784) Showcase readme - update deployment from eclipse part
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12784?page=com.atlassian.jira.plugin.s... ]
Juraj Húska closed RF-12784.
----------------------------
Verified. Closing.
> Showcase readme - update deployment from eclipse part
> -----------------------------------------------------
>
> Key: RF-12784
> URL: https://issues.jboss.org/browse/RF-12784
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: doc, showcase
> Affects Versions: 4.3.0.Final, 5-Tracking
> Reporter: Juraj Húska
> Assignee: Juraj Húska
> Priority: Trivial
> Fix For: 4.3.1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The deployment of the showcase from eclipse needs to be written down in in more details, because it is not trivial:
> An user needs to be aware of:
> * select correct maven profile
> * alter the deployment assembly
> * be aware of wrong context root load in the eclipse browser
> I will send pull request for this one.
--
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, 10 months
[JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on RF-11382:
----------------------------------------------
Ján Jamrich <jjamrich(a)redhat.com> made a comment on [bug 916313|https://bugzilla.redhat.com/show_bug.cgi?id=916313]
Patch verified by job [1], manually by adding page witch code from related JIRA [2] added by jpapousek.
Steps to apply patch verified too, built metamer.war with patched version of richfaces-component-ui.jar
[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RF-Prod/job/richfac...
[2] https://issues.jboss.org/browse/RF-11382
> Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
> -------------------------------------------------------------------------------
>
> Key: RF-11382
> URL: https://issues.jboss.org/browse/RF-11382
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.Final, 4.1.0.Milestone2
> Environment: Fedora 15, Glassfish 3.1.1, CDI (Weld)
> Reporter: Frederick Kämpfer
> Assignee: Brian Leathem
> Labels: lazy-loaded
> Fix For: 4.3.0.M3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> In Richfaces 4 both datatable and extendedDatatable evaluate the value attribute even when rendered is set to false, even though it is not necessary. This makes it hard to achieve performance by trimming parts of the view tree. The built-in h:dataTable behaves correctly in that case.
> To reproduce simply try this snipplet:
> {code:xml}
> <h:form>
> <rich:dataTable value="#{myBean.property}" rendered="false">
> </rich:dataTable>
> </h:form>
> {code}
> Side note: The reason I'm posting this is, that i want to embed a rich:dataTable in a ajax loaded rich:togglePanelItem which is loaded on demand. Probably fixing the "render" problem will also make the dataTable lazy-loadable when switching to the corresponding togglePanelItem.
> I hope this is no duplicate, I only found RichFaces 3 issues mentioning this problem.
--
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, 10 months
[JBoss JIRA] (RF-11382) Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/RF-11382?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on RF-11382:
----------------------------------------------
Ján Jamrich <jjamrich(a)redhat.com> changed the Status of [bug 916313|https://bugzilla.redhat.com/show_bug.cgi?id=916313] from ON_QA to RELEASE_PENDING
> Datatable and ExtendedDatatable evaluate value attribute even if rendered=false
> -------------------------------------------------------------------------------
>
> Key: RF-11382
> URL: https://issues.jboss.org/browse/RF-11382
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.Final, 4.1.0.Milestone2
> Environment: Fedora 15, Glassfish 3.1.1, CDI (Weld)
> Reporter: Frederick Kämpfer
> Assignee: Brian Leathem
> Labels: lazy-loaded
> Fix For: 4.3.0.M3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> In Richfaces 4 both datatable and extendedDatatable evaluate the value attribute even when rendered is set to false, even though it is not necessary. This makes it hard to achieve performance by trimming parts of the view tree. The built-in h:dataTable behaves correctly in that case.
> To reproduce simply try this snipplet:
> {code:xml}
> <h:form>
> <rich:dataTable value="#{myBean.property}" rendered="false">
> </rich:dataTable>
> </h:form>
> {code}
> Side note: The reason I'm posting this is, that i want to embed a rich:dataTable in a ajax loaded rich:togglePanelItem which is loaded on demand. Probably fixing the "render" problem will also make the dataTable lazy-loadable when switching to the corresponding togglePanelItem.
> I hope this is no duplicate, I only found RichFaces 3 issues mentioning this problem.
--
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, 10 months