[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:
----------------------------------------------
Jan Papousek <jpapouse(a)redhat.com> changed the Status of [bug 916314|https://bugzilla.redhat.com/show_bug.cgi?id=916314] from ON_QA to VERIFIED
> 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
12 years, 11 months
[JBoss JIRA] (RF-12842) Allow CSS files with resource EL to be packed
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12842?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč edited comment on RF-12842 at 3/14/13 5:46 AM:
----------------------------------------------------------
See discussion in the pull request.
was (Author: lfryc):
See discussion in pull request.
> Allow CSS files with resource EL to be packed
> ---------------------------------------------
>
> Key: RF-12842
> URL: https://issues.jboss.org/browse/RF-12842
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: cdk
> Affects Versions: 4.3.1
> Reporter: Bernard Labno
>
> I want to package all my custom css files together with RF css files into single css file.
> I'm using maven-richfaces-resources-plugin for that.
> The problem is that css files with resource EL (i.e. #{resource['image.png']}) are excluded from packaging.
> The reason was RF-10474, but as discussed with Lukas Fryc, resource EL could be allowed.
--
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, 11 months
[JBoss JIRA] (RF-12842) Allow CSS files with resource EL to be packed
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12842?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-12842:
---------------------------------
See discussion in pull request.
> Allow CSS files with resource EL to be packed
> ---------------------------------------------
>
> Key: RF-12842
> URL: https://issues.jboss.org/browse/RF-12842
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: cdk
> Affects Versions: 4.3.1
> Reporter: Bernard Labno
>
> I want to package all my custom css files together with RF css files into single css file.
> I'm using maven-richfaces-resources-plugin for that.
> The problem is that css files with resource EL (i.e. #{resource['image.png']}) are excluded from packaging.
> The reason was RF-10474, but as discussed with Lukas Fryc, resource EL could be allowed.
--
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, 11 months
[JBoss JIRA] (RF-12806) Remote configuration in the arquillian.xml file should be commented - See JDF-215 for details
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12806?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12806.
--------------------------------
Assignee: Brian Leathem
Fix Version/s: 4.3.1
(was: 5.0.0.M2)
(was: 4.3.2)
Resolution: Done
This will be available in the 4.3.1.Final-1 release of the kitchensink archetype.
> Remote configuration in the arquillian.xml file should be commented - See JDF-215 for details
> ---------------------------------------------------------------------------------------------
>
> Key: RF-12806
> URL: https://issues.jboss.org/browse/RF-12806
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Reporter: Sande Gilda
> Assignee: Brian Leathem
> Fix For: 4.3.1
>
>
> The kitchensink-rf arquillian.xml file contains a configuration for jbossHome
> This should be commented out. All the remote configuration in the arquillian files should look like the following:
> <!-- Example configuration for a remote JBoss Enterprise Application Platform 6 or AS 7 instance -->
> <container qualifier="jboss" default="true">
> <!-- By default, arquillian will use the JBOSS_HOME environment variable. Alternatively, the configuration below can be uncommented. -->
> <!--<configuration> -->
> <!--<property name="jbossHome">/path/to/jboss/as</property> -->
> <!--</configuration> -->
> </container>
> You can copy and paste from the bean-validation arquillian.xml file.
--
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, 11 months
[JBoss JIRA] (RF-12809) Richfaces-related examples should use -with-richfaces BOM
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12809?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12809:
------------------------------------
Why would we do this? Why not just consume the RichFaces BOM directly? using [jboss-javaee-6.0-with-richfaces|https://github.com/jboss-jdf/jboss-bom/bl...], which imports the richfaces bom and jboss-javaee-6.0 simply adds more confusin IMO.
On top of that, we have yet one more place to manage the version increment, which [jboss-bom-parent|https://github.com/jboss-jdf/jboss-bom/blob/master/pom.x...] currently pins at 4.2.0.Final - a very old release.
I prefer leaving the RichFaces BOM in the examples directly, as it is most clear to those trying to understand the examples.
> Richfaces-related examples should use -with-richfaces BOM
> ---------------------------------------------------------
>
> Key: RF-12809
> URL: https://issues.jboss.org/browse/RF-12809
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Reporter: Tomas Repel
> Fix For: 4.3.2, 5.0.0.M2
>
>
> There is jboss-javaee-6.0-with-richfaces BOM, I think this should be used instead of richfaces-bom in case that jboss-javaee-6.0 BOM is required as well. This holds for helloworld-rf, kitchensink-rf and richfaces-validation. In case of helloworld-rf it is sufficient the dependencyManagement section to contain only -with-richfaces BOM, the jboss-javaee-6.0 BOM can be removed completely.
--
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, 11 months