From issues at jboss.org Fri Aug 1 02:56:29 2014 From: issues at jboss.org (Thomas Amrhein (JIRA)) Date: Fri, 1 Aug 2014 02:56:29 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13753) Upgrade Atmosphore to 2.2.0 In-Reply-To: References: Message-ID: Thomas Amrhein created RF-13753: ----------------------------------- Summary: Upgrade Atmosphore to 2.2.0 Key: RF-13753 URL: https://issues.jboss.org/browse/RF-13753 Project: RichFaces Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 5.0.0.Alpha3, 4.3.7 Reporter: Thomas Amrhein Upgrade Atmosphere from 1.0.18 to 2.2.0. Reason: Many bugfixes, improved compatibility to many servers, ... For us: Also upgrade in 4.3.x is required. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 02:56:29 2014 From: issues at jboss.org (Thomas Amrhein (JIRA)) Date: Fri, 1 Aug 2014 02:56:29 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13753) Upgrade Atmosphere to 2.2.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Amrhein updated RF-13753: -------------------------------- Summary: Upgrade Atmosphere to 2.2.0 (was: Upgrade Atmosphore to 2.2.0) > Upgrade Atmosphere to 2.2.0 > --------------------------- > > Key: RF-13753 > URL: https://issues.jboss.org/browse/RF-13753 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.3.7, 5.0.0.Alpha3 > Reporter: Thomas Amrhein > > Upgrade Atmosphere from 1.0.18 to 2.2.0. > Reason: Many bugfixes, improved compatibility to many servers, ... > For us: Also upgrade in 4.3.x is required. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 04:10:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 1 Aug 2014 04:10:29 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13746) Some of RichFaces 4.5.0.Alpha3 artifacts are missing in Maven Central In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13746. ---------------------------- Verified. Closing. > Some of RichFaces 4.5.0.Alpha3 artifacts are missing in Maven Central > --------------------------------------------------------------------- > > Key: RF-13746 > URL: https://issues.jboss.org/browse/RF-13746 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Michal Petrov > Priority: Blocker > Fix For: 4.5.0.Beta1 > > > An 4.5.0.Alpha3 RF application can not be built only with artifacts from Maven Central. > [Following|http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.richfaces%22%20AND%20v%3A%224.5.0.Alpha3%22] artifacts are available there. > There is not e.g. {{org.richfaces:richfaces-components-parent:pom:4.5.0.Alpha3}}. > Similar problem raised for {{5.0.0.Alpha2}} and was resolved. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 05:16:36 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 1 Aug 2014 05:16:36 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12744) Make the test suite log less verbose In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RF-12744: ------------------------------- Fix Version/s: 4.5-Tracking (was: 5-Tracking) > Make the test suite log less verbose > ------------------------------------ > > Key: RF-12744 > URL: https://issues.jboss.org/browse/RF-12744 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: tests - functional , tests - unit > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Assignee: Pavol Pitonak > Labels: rf5-build > Fix For: 4.5-Tracking > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > We could add logging.properties which will filter out unnecessary output (e.g. JSF container startup logging). > We should also remove any unnecessary System.out/logging from tests. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 04:48:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 4 Aug 2014 04:48:29 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13754) Showcase - remove dependencies for JMS push example In-Reply-To: References: Message-ID: Juraj H?ska created RF-13754: -------------------------------- Summary: Showcase - remove dependencies for JMS push example Key: RF-13754 URL: https://issues.jboss.org/browse/RF-13754 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.5.0.Alpha3 Reporter: Juraj H?ska The JMS example is not used anymore in the Showcase. But there are still dependencies needed to run it on AS 7 and AS 6. The problem is that particularly, dependency: {code:xml} org.jboss.as jboss-as-controller-client provided {code} is blocking start of Wildfly 8.1.Final when running integration tests. Because 4.5.x will not run on AS 7 and below anymore, and because JMS example is deprecated in Showcase (we are using instead Push examples) I would remove these dependencies altogether. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 04:52:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 4 Aug 2014 04:52:29 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13754) Showcase - remove dependencies for JMS push example In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990067#comment-12990067 ] Juraj H?ska commented on RF-13754: ---------------------------------- If you agree with this I would incorporate fix for this in the work for moving showcase tests into showcase repository itself ? > Showcase - remove dependencies for JMS push example > --------------------------------------------------- > > Key: RF-13754 > URL: https://issues.jboss.org/browse/RF-13754 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > > The JMS example is not used anymore in the Showcase. But there are still dependencies needed to run it on AS 7 and AS 6. > The problem is that particularly, dependency: > {code:xml} > > org.jboss.as > jboss-as-controller-client > provided > > {code} > is blocking start of Wildfly 8.1.Final when running integration tests. > Because 4.5.x will not run on AS 7 and below anymore, and because JMS example is deprecated in Showcase (we are using instead Push examples) I would remove these dependencies altogether. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 05:20:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 4 Aug 2014 05:20:30 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12950) Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska reassigned RF-12950: -------------------------------- Assignee: Juraj H?ska (was: Martin Tomasek) > Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests > ------------------------------------------------------------------------------------------------------ > > Key: RF-12950 > URL: https://issues.jboss.org/browse/RF-12950 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Luk?? Fry? > Assignee: Juraj H?ska > Fix For: 4.5.0.Beta1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Smoke tests should verify that basic showcase functionality works as expected. > Full showcase test suite can be moved into RF5 repository then. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 05:22:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 4 Aug 2014 05:22:29 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12950) Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990080#comment-12990080 ] Juraj H?ska commented on RF-12950: ---------------------------------- Running integration-tests profile from within showcase folder is blocked by RF-13754. I started with removing the dependency which causes this. I will also introduce deployment and then handover to [~mtomasek] for further migration. > Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests > ------------------------------------------------------------------------------------------------------ > > Key: RF-12950 > URL: https://issues.jboss.org/browse/RF-12950 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Luk?? Fry? > Assignee: Juraj H?ska > Fix For: 4.5.0.Beta1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Smoke tests should verify that basic showcase functionality works as expected. > Full showcase test suite can be moved into RF5 repository then. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 07:10:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 4 Aug 2014 07:10:30 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12950) Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990111#comment-12990111 ] Juraj H?ska commented on RF-12950: ---------------------------------- I have pushed the changes into this branch: https://github.com/richfaces/richfaces/tree/RF-12950 I added there one dummy test. Test can be run in the same way as integration tests from {{core}}, {{rich}} or {a4j}} package. They should follow the same naming conventions. > Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests > ------------------------------------------------------------------------------------------------------ > > Key: RF-12950 > URL: https://issues.jboss.org/browse/RF-12950 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Luk?? Fry? > Assignee: Juraj H?ska > Fix For: 4.5.0.Beta1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Smoke tests should verify that basic showcase functionality works as expected. > Full showcase test suite can be moved into RF5 repository then. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 07:10:30 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 4 Aug 2014 07:10:30 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12950) Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990111#comment-12990111 ] Juraj H?ska edited comment on RF-12950 at 8/4/14 7:09 AM: ---------------------------------------------------------- I have pushed the changes into this branch: https://github.com/richfaces/richfaces/tree/RF-12950 I added there one dummy test. Test can be run in the same way as integration tests from {{core}}, {{rich}} or {{a4j}} package. They should follow the same naming conventions. was (Author: jhuska): I have pushed the changes into this branch: https://github.com/richfaces/richfaces/tree/RF-12950 I added there one dummy test. Test can be run in the same way as integration tests from {{core}}, {{rich}} or {a4j}} package. They should follow the same naming conventions. > Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests > ------------------------------------------------------------------------------------------------------ > > Key: RF-12950 > URL: https://issues.jboss.org/browse/RF-12950 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Luk?? Fry? > Assignee: Juraj H?ska > Fix For: 4.5.0.Beta1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Smoke tests should verify that basic showcase functionality works as expected. > Full showcase test suite can be moved into RF5 repository then. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 07:10:31 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 4 Aug 2014 07:10:31 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12950) Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-12950: ----------------------------- Assignee: Martin Tomasek (was: Juraj H?ska) > Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests > ------------------------------------------------------------------------------------------------------ > > Key: RF-12950 > URL: https://issues.jboss.org/browse/RF-12950 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Luk?? Fry? > Assignee: Martin Tomasek > Fix For: 4.5.0.Beta1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Smoke tests should verify that basic showcase functionality works as expected. > Full showcase test suite can be moved into RF5 repository then. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 08:30:30 2014 From: issues at jboss.org (=?UTF-8?Q?Jon=C3=A1=C5=A1_Trantina_=28JIRA=29?=) Date: Mon, 4 Aug 2014 08:30:30 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13755) FileUpload JS API - removing files In-Reply-To: References: Message-ID: Jon?? Trantina created RF-13755: ----------------------------------- Summary: FileUpload JS API - removing files Key: RF-13755 URL: https://issues.jboss.org/browse/RF-13755 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.3.5 Reporter: Jon?? Trantina There should be some JS API for fileUpload component letting user remove some or all files via JS. Something like __removeAllFiles but public and supported. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 09:00:34 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Mon, 4 Aug 2014 09:00:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13756) Upgrade jquery.mousewheel.js to 3.1.12 In-Reply-To: References: Message-ID: Michal Petrov created RF-13756: ---------------------------------- Summary: Upgrade jquery.mousewheel.js to 3.1.12 Key: RF-13756 URL: https://issues.jboss.org/browse/RF-13756 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.5.0.Alpha3 Reporter: Michal Petrov Fix For: 4.5.0.Beta1 The current version (3.0.4) is built around {{mousewheel}} event which is no longer supported by Firefox, this affects inputNumberSpinner/Slider and charts (those have the mousewheel code included in jquery.flot.navigate.js). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 09:48:29 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Mon, 4 Aug 2014 09:48:29 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13757) Showcase with MyFaces contains javax.faces JAR In-Reply-To: References: Message-ID: Matej Novotny created RF-13757: ---------------------------------- Summary: Showcase with MyFaces contains javax.faces JAR Key: RF-13757 URL: https://issues.jboss.org/browse/RF-13757 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: examples, showcase Affects Versions: 4.5.0.Alpha3 Environment: RF 4.5.x with MyFaces Any browser Tomcat (7 or 8) Reporter: Matej Novotny When building a Showcase with MyFaces (e.g. {{-Pmyfaces}}) the WAR file which is created contains {{javax.faces-2.2.6.jar}}. This should IMHO be excluded as it is a standard JSF implementation which should be replaced by MyFaces impl. Please see steps to reproduce. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 10:07:38 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Mon, 4 Aug 2014 10:07:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13758) RF 4.5 with MyFaces, CSS not loaded In-Reply-To: References: Message-ID: Matej Novotny created RF-13758: ---------------------------------- Summary: RF 4.5 with MyFaces, CSS not loaded Key: RF-13758 URL: https://issues.jboss.org/browse/RF-13758 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5.0.Alpha3 Reporter: Matej Novotny Priority: Critical When you use MyFaces as JSF implementation, RF fail to get CSS files hence the components are displayed as plain text. I tried this (among others) with simpleapp which I modified by adding a simple rich:panel. With Mojarra the css for panel was received and panel was displayed correctly. Then I modified pom.xml to use MyFaces. The app can be deployed but the panel is just a plain text and page contains no css for styling. This can be reproduced with Metamer/simpleapp/showcase. Please see steps to reproduce for reproducers with Metamer and simpleapp. Showcase reproducer is more complicated due to RF-13757. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 10:21:39 2014 From: issues at jboss.org (Pavel Slegr (JIRA)) Date: Mon, 4 Aug 2014 10:21:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13759) Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0 In-Reply-To: References: Message-ID: Pavel Slegr created RF-13759: -------------------------------- Summary: Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0 Key: RF-13759 URL: https://issues.jboss.org/browse/RF-13759 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: cdk, component, core Affects Versions: 4.5.0.Alpha3 Reporter: Pavel Slegr Fix For: 4.5.0.Beta1 both cdk and richfaces projects use different jboss-parent versions (9,12) EAP-6.3.0 which will be underlying base for RF-4.5.0 uses as latest supported jboss-parent version 11. Please unify into jboss-parent 11 NOTE: updating cdk version into jboss-parent 11, will need a maintenance (update for deprecated code) in cdk/maven-plugin/src/main/java/org/richfaces/builder/mojo These classes use deprecated api such as {code} @parameter expression="${executedProject}"" {code} which doesn't work with maven-plugin-plugin 3.1 and leads into {code} [WARNING] The syntax [WARNING] @parameter expression="${property}" [WARNING] is deprecated, please use [WARNING] @parameter property="property" [WARNING] instead. {code} Some other additional changes may be also needed. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 10:21:50 2014 From: issues at jboss.org (Pavel Slegr (JIRA)) Date: Mon, 4 Aug 2014 10:21:50 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13759) Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Slegr updated RF-13759: ----------------------------- Assignee: Brian Leathem > Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0 > ----------------------------------------------------------------------------- > > Key: RF-13759 > URL: https://issues.jboss.org/browse/RF-13759 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: cdk, component, core > Affects Versions: 4.5.0.Alpha3 > Reporter: Pavel Slegr > Assignee: Brian Leathem > Fix For: 4.5.0.Beta1 > > > both cdk and richfaces projects use different jboss-parent versions (9,12) > EAP-6.3.0 which will be underlying base for RF-4.5.0 uses as latest supported jboss-parent version 11. > Please unify into jboss-parent 11 > NOTE: updating cdk version into jboss-parent 11, will need a maintenance (update for deprecated code) in cdk/maven-plugin/src/main/java/org/richfaces/builder/mojo > These classes use deprecated api such as > {code} > @parameter expression="${executedProject}"" > {code} > which doesn't work with maven-plugin-plugin 3.1 and leads into > {code} > [WARNING] The syntax > [WARNING] @parameter expression="${property}" > [WARNING] is deprecated, please use > [WARNING] @parameter property="property" > [WARNING] instead. > {code} > Some other additional changes may be also needed. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 03:28:30 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 5 Aug 2014 03:28:30 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13758) RF 4.5 with MyFaces, CSS not loaded In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov reassigned RF-13758: ---------------------------------- Assignee: Michal Petrov > RF 4.5 with MyFaces, CSS not loaded > ----------------------------------- > > Key: RF-13758 > URL: https://issues.jboss.org/browse/RF-13758 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Matej Novotny > Assignee: Michal Petrov > Priority: Critical > > When you use MyFaces as JSF implementation, RF fail to get CSS files hence the components are displayed as plain text. > I tried this (among others) with simpleapp which I modified by adding a simple rich:panel. With Mojarra the css for panel was received and panel was displayed correctly. Then I modified pom.xml to use MyFaces. The app can be deployed but the panel is just a plain text and page contains no css for styling. > This can be reproduced with Metamer/simpleapp/showcase. > Please see steps to reproduce for reproducers with Metamer and simpleapp. > Showcase reproducer is more complicated due to RF-13757. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 07:02:30 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Tue, 5 Aug 2014 07:02:30 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13739) Placeholder in collapsibleSubTable template In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990365#comment-12990365 ] Matej Novotny commented on RF-13739: ------------------------------------ [~michpetrov] should I create a dedicated sample like Brian suggested? If so, could you give me some more details on what exactly should such sample contain? I am not sure I am following you in this issue. > Placeholder in collapsibleSubTable template > ------------------------------------------- > > Key: RF-13739 > URL: https://issues.jboss.org/browse/RF-13739 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.5.0.Alpha3 > Environment: RichFaces 4.5.0-SNAPSHOT > Metamer 4.5.0-SNAPSHOT > Mojarra 2.2.6-jbossorg-4 > JBoss AS 8.1.0.Final > Java(TM) SE Runtime Environment 1.7.0_25-b15 @ Linux > Firefox 30.0 @ Linux x86_64 > Reporter: Matej Novotny > Assignee: Michal Petrov > Labels: needs-qe > Fix For: 4.5.0.Beta1 > > > Placeholder selector set to empty string ({{selector=""}}) does not work when nested inside richCollapsibleSubTable template. The expected result is that all inputs will contains the placeholder text, however none of them does. If you set selector to a specific ID, the test succeeds. > This only happens when you attach the placeholder to {{