October 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13225) RF5 build fails to render optimized resources

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-13225?page=com.atlassian.jira.plugin.s... ] Michal Petrov updated RF-13225: ------------------------------- Description: The improvements for 4.5.x along with resource handling improvements introduced several issues: * framework/pom.xml resource optimization {code} <execution> <id>static-resources</id> <phase>process-classes</phase> <goals> <goal>java</goal> </goals> <configuration> <arguments> <argument>--classpathDir</argument> <argument>${project.build.outputDirectory}</argument> <argument>--output</argument> <argument>${optimized.resources.directory}/Static/</argument> <argument>--prefix</argument> <argument>${optimized.resources.prefix}/Static/</argument> <argument>--mapping</argument <argument>${optimized.resources.mapping}/Static.properties</argument> <argument>--skins</argument> <argument>${optimized.resources.skins}</argument> <argument>--excludeFile</argument> <argument>^javax.faces</argument> <argument>excludeFile</argument> <argument>^org.richfaces.ui.images.*</argument> {code} {panel} the exclusion exists for classes like {{org/richfaces/ui/images/BaseGradient.java}} which end up being rendered as images, with the change to image resources in RF5 this exclusion causes the resource handling to fail {panel} * CSS rendering from *.ecss {code} #{richSkin.imageUrl('inputBackgroundImage.png')} {code} {panel} the imageUrl method doesn't return the proper path, e.g. {{../org.richfaces.ui.images/gradientA.png}} (proper) instead of {{%skin%/org.richfaces.ui.images/gradientA.png}} (current) {panel} was: The improvements for 4.5.x along with resource handling improvements introduced several issues: * framework/pom.xml resource optimization {code} <execution> <id>static-resources</id> <phase>process-classes</phase> <goals> <goal>java</goal> </goals> <configuration> <arguments> <argument>--classpathDir</argument> <argument>${project.build.outputDirectory}</argument> <argument>--output</argument> <argument>${optimized.resources.directory}/Static/</argument> <argument>--prefix</argument> <argument>${optimized.resources.prefix}/Static/</argument> <argument>--mapping</argument <argument>${optimized.resources.mapping}/Static.properties</argument> <argument>--skins</argument> <argument>${optimized.resources.skins}</argument> <argument>--excludeFile</argument> <argument>^javax.faces</argument> <argument>excludeFile</argument> <argument>^org.richfaces.ui.images.*</argument> {code} {panel} the exclusion exists for classes like {{org/richfaces/ui/images/BaseGradient.java}} which end up being rendered as images, with the change to image resources in RF5 this exclusion causes the resource handling to fail {panel} * CSS rendering from *.ecss {code} #{richSkin.imageUrl('inputBackgroundImage.png')} {code} {panel} the imageUrl method doesn't return the proper path, e.g. {{../org.richfaces.ui.images/gradientA.png}} (proper) instead of {{../org.richfaces.ui.images/gradientA.png}} (current) {panel} > RF5 build fails to render optimized resources > --------------------------------------------- > > Key: RF-13225 > URL: https://issues.jboss.org/browse/RF-13225 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha2 > Reporter: Michal Petrov > Fix For: 5.0.0.Alpha2 > > > The improvements for 4.5.x along with resource handling improvements introduced several issues: > * framework/pom.xml resource optimization > {code} > <execution> > <id>static-resources</id> > <phase>process-classes</phase> > <goals> > <goal>java</goal> > </goals> > <configuration> > <arguments> > <argument>--classpathDir</argument> > <argument>${project.build.outputDirectory}</argument> > <argument>--output</argument> > <argument>${optimized.resources.directory}/Static/</argument> > <argument>--prefix</argument> > <argument>${optimized.resources.prefix}/Static/</argument> > <argument>--mapping</argument > <argument>${optimized.resources.mapping}/Static.properties</argument> > <argument>--skins</argument> > <argument>${optimized.resources.skins}</argument> > <argument>--excludeFile</argument> > <argument>^javax.faces</argument> > <argument>excludeFile</argument> > <argument>^org.richfaces.ui.images.*</argument> > {code} > {panel} > the exclusion exists for classes like {{org/richfaces/ui/images/BaseGradient.java}} which end up being rendered as images, with the change to image resources in RF5 this exclusion causes the resource handling to fail > {panel} > * CSS rendering from *.ecss > {code} > #{richSkin.imageUrl('inputBackgroundImage.png')} > {code} > {panel} > the imageUrl method doesn't return the proper path, e.g. {{../org.richfaces.ui.images/gradientA.png}} (proper) instead of {{%skin%/org.richfaces.ui.images/gradientA.png}} (current) > {panel} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13225) RF5 build fails to render optimized resources

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13225?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13225: ------------------------------- Description: The improvements for 4.5.x along with resource handling improvements introduced several issues: * framework/pom.xml resource optimization {code} <execution> <id>static-resources</id> <phase>process-classes</phase> <goals> <goal>java</goal> </goals> <configuration> <arguments> <argument>--classpathDir</argument> <argument>${project.build.outputDirectory}</argument> <argument>--output</argument> <argument>${optimized.resources.directory}/Static/</argument> <argument>--prefix</argument> <argument>${optimized.resources.prefix}/Static/</argument> <argument>--mapping</argument <argument>${optimized.resources.mapping}/Static.properties</argument> <argument>--skins</argument> <argument>${optimized.resources.skins}</argument> <argument>--excludeFile</argument> <argument>^javax.faces</argument> <argument>excludeFile</argument> <argument>^org.richfaces.ui.images.*</argument> {code} {panel} the exclusion exists for classes like {{org/richfaces/ui/images/BaseGradient.java}} which end up being rendered as images, with the change to image resources in RF5 this exclusion causes the resource handling to fail {panel} * CSS rendering from *.ecss {code} #{richSkin.imageUrl('inputBackgroundImage.png')} {code} {panel} the imageUrl method doesn't return the proper path, e.g. {{../org.richfaces.ui.images/gradientA.png}} (proper) instead of {{%skin%/org.richfaces.ui.images/gradientA.png}} (current) {panel} was: The improvements for 4.5.x along with resource handling improvements introduced several issues: * framework/pom.xml resource optimization {code} <execution> <id>static-resources</id> <phase>process-classes</phase> <goals> <goal>java</goal> </goals> <configuration> <arguments> <argument>--classpathDir</argument> <argument>${project.build.outputDirectory}</argument> <argument>--output</argument> <argument>${optimized.resources.directory}/Static/</argument> <argument>--prefix</argument> <argument>${optimized.resources.prefix}/Static/</argument> <argument>--mapping</argument <argument>${optimized.resources.mapping}/Static.properties</argument> <argument>--skins</argument> <argument>${optimized.resources.skins}</argument> <argument>--excludeFile</argument> <argument>^javax.faces</argument> <argument>excludeFile</argument> <argument>^org.richfaces.ui.images.*</argument> {code} {panel} the exclusion exists for classes like {{org/richfaces/ui/images/BaseGradient.java}} which end up being rendered as images, with the change to image resources in RF5 this exclusion causes the resource handling to fail {panel} * CSS rendering from *.ecss {code} #{richSkin.imageUrl('inputBackgroundImage.png')} {code} {panel} the imageUrl method doesn't return the proper path, e.g. {{../org.richfaces.ui.images/gradientA.png}} (proper) instead of {{%skin%/org.richfaces.ui.images/gradientA.png}} (current) {panel} > RF5 build fails to render optimized resources > --------------------------------------------- > > Key: RF-13225 > URL: https://issues.jboss.org/browse/RF-13225 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha2 > Reporter: Michal Petrov > Fix For: 5.0.0.Alpha2 > > > The improvements for 4.5.x along with resource handling improvements introduced several issues: > * framework/pom.xml resource optimization > {code} > <execution> > <id>static-resources</id> > <phase>process-classes</phase> > <goals> > <goal>java</goal> > </goals> > <configuration> > <arguments> > <argument>--classpathDir</argument> > <argument>${project.build.outputDirectory}</argument> > <argument>--output</argument> > <argument>${optimized.resources.directory}/Static/</argument> > <argument>--prefix</argument> > <argument>${optimized.resources.prefix}/Static/</argument> > <argument>--mapping</argument > <argument>${optimized.resources.mapping}/Static.properties</argument> > <argument>--skins</argument> > <argument>${optimized.resources.skins}</argument> > <argument>--excludeFile</argument> > <argument>^javax.faces</argument> > <argument>excludeFile</argument> > <argument>^org.richfaces.ui.images.*</argument> > {code} > {panel} > the exclusion exists for classes like {{org/richfaces/ui/images/BaseGradient.java}} which end up being rendered as images, with the change to image resources in RF5 this exclusion causes the resource handling to fail > {panel} > * CSS rendering from *.ecss > {code} > #{richSkin.imageUrl('inputBackgroundImage.png')} > {code} > {panel} > the imageUrl method doesn't return the proper path, e.g. > {{../org.richfaces.ui.images/gradientA.png}} (proper) > instead of > {{%skin%/org.richfaces.ui.images/gradientA.png}} (current) > {panel} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13255) Autocomplete - cachedAjax isn't implemented

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13255?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13255: ---------------------------- Sprint: 5.0.0.Alpha2 - Sprint 2 > Autocomplete - cachedAjax isn't implemented > ------------------------------------------- > > Key: RF-13255 > URL: https://issues.jboss.org/browse/RF-13255 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha2 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13255) Autocomplete - cachedAjax isn't implemented

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13255: ------------------------------- Summary: Autocomplete - cachedAjax isn't implemented Key: RF-13255 URL: https://issues.jboss.org/browse/RF-13255 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 5.0.0.Alpha2 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 5.0.0.Alpha2 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13238) Components' images have wrong path

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-13238?page=com.atlassian.jira.plugin.s... ] Michal Petrov commented on RF-13238: ------------------------------------ 13225 rather, there is some issue with resource path translation in RF 5 > Components' images have wrong path > ---------------------------------- > > Key: RF-13238 > URL: https://issues.jboss.org/browse/RF-13238 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha1 > Environment: RichFaces 5.0.0.Alpha1 > all browsers > Reporter: Pavol Pitonak > Priority: Critical > Fix For: 5.0.0.Alpha2 > > > # git clone https://github.com/ppitonak/richrates.git > # mvn clean package > # deploy to WildFly 8.0.0.Alpha4 > # open http://localhost:8080/richrates/faces/calculator.xhtml > # check browser console > result: > * you can see 4 similar errors: > {quote} > GET http://localhost:8080/richrates/org.richfaces.resources/javax.faces.resou... 400 (Bad Request) > {quote} > * %skin% should be probably replaced with skin name -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13254) Images in online Component Reference are missing

by Pavol Pitonak (JIRA)

Pavol Pitonak created RF-13254: ---------------------------------- Summary: Images in online Component Reference are missing Key: RF-13254 URL: https://issues.jboss.org/browse/RF-13254 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: doc Affects Versions: 5.0.0.Alpha1 Reporter: Pavol Pitonak Images in Component Reference are missing, see e.g. http://docs.jboss.org/richfaces/nightly_5_0_X/Component_Reference/en-US/h... -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13193) Rename the resource library to account for RF 4/5 resource overlap

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-13193?page=com.atlassian.jira.plugin.s... ] Michal Petrov commented on RF-13193: ------------------------------------ What do we mean by resource library? The {{org.richfaces}} folder under {{META-INF/resources}}? There should be no conflicts/overlaps. Conflicts occur with filenames since the mapping rules are defined as "take any *.css and put it here" and disregard the filepath so renaming won't help there. > Rename the resource library to account for RF 4/5 resource overlap > ------------------------------------------------------------------ > > Key: RF-13193 > URL: https://issues.jboss.org/browse/RF-13193 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: resource handling > Reporter: Brian Leathem > Assignee: Michal Petrov > Priority: Critical > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Rename the RichFaces resource library name to something like: _org.richfaces.ui_, or _org.richfaces.widgets_. This will allow RF 4 and RF 5 components to co-exist when resource names overlap. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13184) Autocomplete: ajax completely broken when attribute layout is set

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13184?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-13184: ------------------------------------ In this case we should remove this attribute from the component and from documentation and document this change in a migration guide. > Autocomplete: ajax completely broken when attribute layout is set > ----------------------------------------------------------------- > > Key: RF-13184 > URL: https://issues.jboss.org/browse/RF-13184 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Mojarra 2.1.19 > JBoss AS 7.2.0.Final-redhat-8 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 29.0.1547.65 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 5.0.0.Alpha2 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > # (change event from "change" to "blur" in autocomplete.xhtml when RF-13180 is not resolved) > # set layout=div in autocomplete.xhtml > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl... > # type "a" into input > result: > * ajax request is fired > * status in page's header shows "ERROR" -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13246) Richfaces 4.3.4 ajax fails on ie8 packed.js cannot find console.

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13246?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak reassigned RF-13246: ---------------------------------- Assignee: Jiří Štefek (was: Pavol Pitonak) > Richfaces 4.3.4 ajax fails on ie8 packed.js cannot find console. > ---------------------------------------------------------------- > > Key: RF-13246 > URL: https://issues.jboss.org/browse/RF-13246 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Jeremy Landis > Assignee: Jiří Štefek > > After upgrading to richfaces 4.3.4 using jsf 2.1.26, ajax has stopped working in IE8. I have been able to verify non issue in firefox and IE11. The issue affects specialized ajax calls within a page as well as overall ajax page areas. It further affects extended data grids where it will not allow next page logic to work. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13184) Autocomplete: ajax completely broken when attribute layout is set

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13184?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13184: --------------------------------- The thing is that the layout attribute is no longer need to be implemented, since the widget itself detects what layout you have chosen and renderer decides what layout will be used based on the chosen markup - if you use columns, you will get table layout; otherwise you use list layout. > Autocomplete: ajax completely broken when attribute layout is set > ----------------------------------------------------------------- > > Key: RF-13184 > URL: https://issues.jboss.org/browse/RF-13184 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, regression > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Mojarra 2.1.19 > JBoss AS 7.2.0.Final-redhat-8 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 29.0.1547.65 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 5.0.0.Alpha2 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > # (change event from "change" to "blur" in autocomplete.xhtml when RF-13180 is not resolved) > # set layout=div in autocomplete.xhtml > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl... > # type "a" into input > result: > * ajax request is fired > * status in page's header shows "ERROR" -- 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, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues October 2013