[JBoss JIRA] (RF-13019) Placeholder disappears after form reset
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13019?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13019:
-------------------------------
Description:
I have the following code inside a form -
{code}
<h:inputText id="userName" styleClass="span6" >
<f:validateLength maximum="255"/>
<rich:placeholder value="ID / Username" />
</h:inputText>
{code}
The placeholder value disappears if I reset the form. Comes back up after I click the control and tab out.
was:
I have the following code inside a form -
<h:inputText id="userName" styleClass="span6" >
<f:validateLength maximum="255"/>
<rich:placeholder value="ID / Username" />
</h:inputText>
The placeholder value disappears if I reset the form. Comes back up after I click the control and tab out.
> Placeholder disappears after form reset
> ---------------------------------------
>
> Key: RF-13019
> URL: https://issues.jboss.org/browse/RF-13019
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.2
> Reporter: Atanu Mukherjee
>
> I have the following code inside a form -
> {code}
> <h:inputText id="userName" styleClass="span6" >
> <f:validateLength maximum="255"/>
> <rich:placeholder value="ID / Username" />
> </h:inputText>
> {code}
> The placeholder value disappears if I reset the form. Comes back up after I click the control and tab out.
--
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, 10 months
[JBoss JIRA] (RF-13017) richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13017?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13017:
-------------------------------
Fix Version/s: 4.3.3
> richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible
> -------------------------------------------------------
>
> Key: RF-13017
> URL: https://issues.jboss.org/browse/RF-13017
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 4.3.2
> Reporter: Himanshu Bhardwaj
> Fix For: 4.3.3
>
>
> In the bom of RichFaces, the version of JSF-API being used is
> {code}
> <version.com.sun.faces.jsf-api>2.1.0</version.com.sun.faces.jsf-api>
> {code}
>
> but the version of JSF-IMPL put in use is:
> {code}
> <version.org.jboss.javax.faces.jsf-impl>2.1.19-jbossorg-1</version.org.jboss.javax.faces.jsf-impl>
> {code}
>
> Both the version don't seem to go together. Got the following stack-trace:
>
> {code}
> SEVERE: ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
> at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
> at com.sun.faces.config.InitFacesContext.cleanupInitMaps(InitFacesContext.java:281)
> at com.sun.faces.config.InitFacesContext.<init>(InitFacesContext.java:107)
> at com.sun.faces.config.FacesInitializer.onStartup(FacesInitializer.java:115)
> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5274)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> ... 11 more
>
>
> May 21, 2013 11:30:43 AM org.apache.catalina.startup.HostConfig deployWAR
> SEVERE: Error deploying web application archive F:\DevTools\apache-tomcat-7.0.34\webapps\abc.war
> java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
> at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> {code}
>
> I had to manually delete the 2.1.0 jsf-api jar from the war file and copy 2.1.19, with this I was able to bypass this 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, 10 months
[JBoss JIRA] (RF-13017) richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13017?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13017:
-------------------------------
Steps to Reproduce:
Build tool - Maven
AS - Tomcat 7
Java - JDK 7
Create a simple webapp which includes Richfaces-4.3.2.Final and try to deploy it in tomcat , it fails.
The way to import Richfaces is using bom-import:
{code}
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.richfaces</groupId>
<artifactId>richfaces-bom</artifactId>
<version>4.3.2.Final</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<!-- Richfaces dependencies -->
<dependency>
<groupId>org.richfaces.ui</groupId>
<artifactId>richfaces-components-ui</artifactId>
</dependency>
<dependency>
<groupId>org.richfaces.core</groupId>
<artifactId>richfaces-core-impl</artifactId>
</dependency>
<!-- Richfaces dependencies Ends here -->
</dependencies>
{code}
was:
Build tool - Maven
AS - Tomcat 7
Java - JDK 7
Create a simple webapp which includes Richfaces-4.3.2.Final and try to deploy it in tomcat , it fails.
The way to import Richfaces is using bom-import:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.richfaces</groupId>
<artifactId>richfaces-bom</artifactId>
<version>4.3.2.Final</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<!-- Richfaces dependencies -->
<dependency>
<groupId>org.richfaces.ui</groupId>
<artifactId>richfaces-components-ui</artifactId>
</dependency>
<dependency>
<groupId>org.richfaces.core</groupId>
<artifactId>richfaces-core-impl</artifactId>
</dependency>
<!-- Richfaces dependencies Ends here -->
</dependencies>
> richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible
> -------------------------------------------------------
>
> Key: RF-13017
> URL: https://issues.jboss.org/browse/RF-13017
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 4.3.2
> Reporter: Himanshu Bhardwaj
>
> In the bom of RichFaces, the version of JSF-API being used is
>
> <version.com.sun.faces.jsf-api>2.1.0</version.com.sun.faces.jsf-api>
>
> but the version of JSF-IMPL put in use is:
>
> <version.org.jboss.javax.faces.jsf-impl>2.1.19-jbossorg-1</version.org.jboss.javax.faces.jsf-impl>
>
> Both the version don't seem to go together. Got the following stack-trace:
>
> SEVERE: ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
> at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
> at com.sun.faces.config.InitFacesContext.cleanupInitMaps(InitFacesContext.java:281)
> at com.sun.faces.config.InitFacesContext.<init>(InitFacesContext.java:107)
> at com.sun.faces.config.FacesInitializer.onStartup(FacesInitializer.java:115)
> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5274)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> ... 11 more
>
>
> May 21, 2013 11:30:43 AM org.apache.catalina.startup.HostConfig deployWAR
> SEVERE: Error deploying web application archive F:\DevTools\apache-tomcat-7.0.34\webapps\abc.war
> java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
> at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
>
> I had to manually delete the 2.1.0 jsf-api jar from the war file and copy 2.1.19, with this I was able to bypass this 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, 10 months
[JBoss JIRA] (RF-13017) richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13017?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13017:
-------------------------------
Description:
In the bom of RichFaces, the version of JSF-API being used is
{code}
<version.com.sun.faces.jsf-api>2.1.0</version.com.sun.faces.jsf-api>
{code}
but the version of JSF-IMPL put in use is:
{code}
<version.org.jboss.javax.faces.jsf-impl>2.1.19-jbossorg-1</version.org.jboss.javax.faces.jsf-impl>
{code}
Both the version don't seem to go together. Got the following stack-trace:
{code}
SEVERE: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
at com.sun.faces.config.InitFacesContext.cleanupInitMaps(InitFacesContext.java:281)
at com.sun.faces.config.InitFacesContext.<init>(InitFacesContext.java:107)
at com.sun.faces.config.FacesInitializer.onStartup(FacesInitializer.java:115)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5274)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 11 more
May 21, 2013 11:30:43 AM org.apache.catalina.startup.HostConfig deployWAR
SEVERE: Error deploying web application archive F:\DevTools\apache-tomcat-7.0.34\webapps\abc.war
java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
{code}
I had to manually delete the 2.1.0 jsf-api jar from the war file and copy 2.1.19, with this I was able to bypass this error.
was:
In the bom of RichFaces, the version of JSF-API being used is
<version.com.sun.faces.jsf-api>2.1.0</version.com.sun.faces.jsf-api>
but the version of JSF-IMPL put in use is:
<version.org.jboss.javax.faces.jsf-impl>2.1.19-jbossorg-1</version.org.jboss.javax.faces.jsf-impl>
Both the version don't seem to go together. Got the following stack-trace:
SEVERE: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
at com.sun.faces.config.InitFacesContext.cleanupInitMaps(InitFacesContext.java:281)
at com.sun.faces.config.InitFacesContext.<init>(InitFacesContext.java:107)
at com.sun.faces.config.FacesInitializer.onStartup(FacesInitializer.java:115)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5274)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 11 more
May 21, 2013 11:30:43 AM org.apache.catalina.startup.HostConfig deployWAR
SEVERE: Error deploying web application archive F:\DevTools\apache-tomcat-7.0.34\webapps\abc.war
java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
I had to manually delete the 2.1.0 jsf-api jar from the war file and copy 2.1.19, with this I was able to bypass this error.
> richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible
> -------------------------------------------------------
>
> Key: RF-13017
> URL: https://issues.jboss.org/browse/RF-13017
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 4.3.2
> Reporter: Himanshu Bhardwaj
>
> In the bom of RichFaces, the version of JSF-API being used is
> {code}
> <version.com.sun.faces.jsf-api>2.1.0</version.com.sun.faces.jsf-api>
> {code}
>
> but the version of JSF-IMPL put in use is:
> {code}
> <version.org.jboss.javax.faces.jsf-impl>2.1.19-jbossorg-1</version.org.jboss.javax.faces.jsf-impl>
> {code}
>
> Both the version don't seem to go together. Got the following stack-trace:
>
> {code}
> SEVERE: ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
> at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
> at com.sun.faces.config.InitFacesContext.cleanupInitMaps(InitFacesContext.java:281)
> at com.sun.faces.config.InitFacesContext.<init>(InitFacesContext.java:107)
> at com.sun.faces.config.FacesInitializer.onStartup(FacesInitializer.java:115)
> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5274)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> ... 11 more
>
>
> May 21, 2013 11:30:43 AM org.apache.catalina.startup.HostConfig deployWAR
> SEVERE: Error deploying web application archive F:\DevTools\apache-tomcat-7.0.34\webapps\abc.war
> java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]]
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977)
> at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> {code}
>
> I had to manually delete the 2.1.0 jsf-api jar from the war file and copy 2.1.19, with this I was able to bypass this 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, 10 months
[JBoss JIRA] (RF-13010) Popup panel inside popup panel: button not rendered in IE10
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13010?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13010:
------------------------------------
I would have expected this to have been resolved with RF-12958. I'll look into it.
> Popup panel inside popup panel: button not rendered in IE10
> -----------------------------------------------------------
>
> Key: RF-13010
> URL: https://issues.jboss.org/browse/RF-13010
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.3.2, 5.0.0.Alpha1
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.13
> EAP 6.0.1
> Java(TM) SE Runtime Environment 1.6.0_32-b05 @ Linux
> works in Chrome 27.0.1453.93 @ Linux x86_64
> broken in IE10 @ Win 8, IE9 @ Win 7
> Reporter: Pavol Pitonak
> Labels: regression
> Fix For: 4.3.3, 5.0.0.Alpha1
>
> Attachments: buttonInPopupPanel.png
>
>
> # deploy Metamer and open http://192.168.122.1:8080/metamer/faces/components/richPopupPanel/simple....
> # change template to "Rich Popup Panel"
> # click the "Call the popup" button
> result:
> * the is a button between paragraph and link inside popup panel in Chrome/Firefox
> * the button is missing in IE 10
> * it might be related to RF-12850 or RF-12958
> * worked fine in 4.3.1.Final
--
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, 10 months
[JBoss JIRA] (RF-13009) drag and drop inside collapsible subtable causes assertion error
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13009?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13009:
-------------------------------
Fix Version/s: 5-Tracking
(was: 5.0.0.Alpha1)
> drag and drop inside collapsible subtable causes assertion error
> ----------------------------------------------------------------
>
> Key: RF-13009
> URL: https://issues.jboss.org/browse/RF-13009
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-drag/drop, component-tables
> Affects Versions: 4.3.2, 5.0.0.Alpha1
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> JBoss Application Server: Weld Integration 7.1.1.Final
> JBoss AS 7.1.1.Final
> Java(TM) SE Runtime Environment 1.7.0_17-b02 @ Linux
> Chrome 26.0.1410.63 @ Linux x86_64
> Reporter: Jan Papousek
> Fix For: 5-Tracking
>
>
> The issue is probably caused by this assertion: https://github.com/richfaces/richfaces/blob/master/framework/src/main/jav...
> Here is the stack trace:
> {code}
> Daemon Thread [http-localhost-127.0.0.1-8080-1] (Suspended (breakpoint at line 880 in UIDataAdaptor))
> UICollapsibleSubTable(UIDataAdaptor).getIterationState() line: 880
> UICollapsibleSubTable(AbstractCollapsibleSubTable).getIterationState() line: 151
> SavedState.<init>(IterationStateHolder) line: 62
> UIDataTable(UIDataAdaptor).saveChildState(FacesContext, UIComponent) line: 309
> UIDataTable(UIDataAdaptor).saveChildState(FacesContext) line: 290
> UIDataTable(UIDataAdaptor).setRowKey(FacesContext, Object) line: 266
> UIDataTable(UIDataAdaptor).invokeOnComponent(FacesContext, String, ContextCallback) line: 1074
> HtmlForm(UIComponent).invokeOnComponent(FacesContext, String, ContextCallback) line: 1426
> HtmlForm(UIComponentBase).invokeOnComponent(FacesContext, String, ContextCallback) line: 669
> HtmlPanelGroup(UIComponent).invokeOnComponent(FacesContext, String, ContextCallback) line: 1426
> HtmlPanelGroup(UIComponentBase).invokeOnComponent(FacesContext, String, ContextCallback) line: 669
> UIOutput(UIComponent).invokeOnComponent(FacesContext, String, ContextCallback) line: 1426
> UIOutput(UIComponentBase).invokeOnComponent(FacesContext, String, ContextCallback) line: 669
> UIViewRoot(UIComponent).invokeOnComponent(FacesContext, String, ContextCallback) line: 1426
> UIViewRoot(UIComponentBase).invokeOnComponent(FacesContext, String, ContextCallback) line: 669
> DropTargetRenderer.doDecode(FacesContext, UIComponent) line: 86
> DropTargetRenderer(RendererBase).decode(FacesContext, UIComponent) line: 81
> UIDropTarget(UIComponentBase).decode(FacesContext) line: 787
> UIDropTarget(UIComponentBase).processDecodes(FacesContext) line: 1181
> PartialViewExecuteVisitCallback.visit(VisitContext, UIComponent) line: 53
> ExecuteExtendedVisitContext(BaseExtendedVisitContext).invokeVisitCallback(UIComponent, VisitCallback) line: 322
> UIDropTarget(UIComponent).visitTree(VisitContext, VisitCallback) line: 1612
> UIOutputPanel(UIComponent).visitTree(VisitContext, VisitCallback) line: 1623
> HtmlPanelGroup(UIComponent).visitTree(VisitContext, VisitCallback) line: 1623
> UIDataAdaptor$DataVisitorForVisitTree.process(FacesContext, Object, Object) line: 197
> SequenceDataModel<E>.walk(FacesContext, DataVisitor, Range, Object) line: 66
> UICollapsibleSubTable(UIDataAdaptor).walk(FacesContext, DataVisitor, Object) line: 807
> UICollapsibleSubTable(UIDataAdaptor).visitDataChildren(VisitContext, VisitCallback, boolean) line: 1280
> UICollapsibleSubTable(UIDataTableBase).visitDataChildren(VisitContext, VisitCallback, boolean) line: 416
> UICollapsibleSubTable(UIDataAdaptor).visitTree(VisitContext, VisitCallback) line: 1358
> UIDataAdaptor$DataVisitorForVisitTree.process(FacesContext, Object, Object) line: 197
> SequenceDataModel<E>.walk(FacesContext, DataVisitor, Range, Object) line: 66
> UIDataTable(UIDataAdaptor).walk(FacesContext, DataVisitor, Object) line: 807
> UIDataTable(UIDataAdaptor).visitDataChildren(VisitContext, VisitCallback, boolean) line: 1280
> UIDataTable(UIDataTableBase).visitDataChildren(VisitContext, VisitCallback, boolean) line: 416
> UIDataTable(UIDataAdaptor).visitTree(VisitContext, VisitCallback) line: 1358
> HtmlForm(UIComponent).visitTree(VisitContext, VisitCallback) line: 1623
> HtmlForm(UIForm).visitTree(VisitContext, VisitCallback) line: 371
> HtmlPanelGroup(UIComponent).visitTree(VisitContext, VisitCallback) line: 1623
> UIOutput(UIComponent).visitTree(VisitContext, VisitCallback) line: 1623
> UIViewRoot(UIComponent).visitTree(VisitContext, VisitCallback) line: 1623
> ExtendedPartialViewContextImpl.executeComponents(PhaseId, Collection<String>) line: 287
> ExtendedPartialViewContextImpl.processPartialExecutePhase(PhaseId) line: 267
> ExtendedPartialViewContextImpl.processPartial(PhaseId) line: 224
> UIViewRoot.processDecodes(FacesContext) line: 931
> ApplyRequestValuesPhase.execute(FacesContext) line: 78
> ApplyRequestValuesPhase(Phase).doPhase(FacesContext, Lifecycle, ListIterator<PhaseListener>) line: 101
> LifecycleImpl.execute(FacesContext) line: 118
> FacesServlet.service(ServletRequest, ServletResponse) line: 593
> ApplicationFilterChain.internalDoFilter(ServletRequest, ServletResponse) line: 329
> ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) line: 248
> TestIdentityFilter.doFilter(ServletRequest, ServletResponse, FilterChain) line: 93
> ApplicationFilterChain.internalDoFilter(ServletRequest, ServletResponse) line: 280
> ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) line: 248
> ConversationPropagationFilter.doFilter(ServletRequest, ServletResponse, FilterChain) line: 62
> ApplicationFilterChain.internalDoFilter(ServletRequest, ServletResponse) line: 280
> ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) line: 248
> StandardWrapperValve.invoke(Request, Response) line: 275
> StandardContextValve.invoke(Request, Response) line: 161
> SecurityContextAssociationValve.invoke(Request, Response) line: 153
> StandardHostValve.invoke(Request, Response) line: 155
> ErrorReportValve.invoke(Request, Response) line: 102
> StandardEngineValve.invoke(Request, Response) line: 109
> CoyoteAdapter.service(Request, Response) line: 368
> Http11Processor.process(Socket) line: 877
> Http11Protocol$Http11ConnectionHandler.process(Socket) line: 671
> JIoEndpoint$Worker.run() line: 930
> Thread.run() line: 722
> {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
12 years, 10 months
[JBoss JIRA] (RF-13021) Simpleapp archetype do not work on Tomcat
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13021?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13021:
-----------------------------
Description:
The simple app archetype does not work on Tomcats. They work on JBoss AS.
The only notable error is this one from server log:
{code}
INFO: validateJarFile(/home/jhuska/workspace_jbossToolsTesting/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/rf500Alpha1testingMvn/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class
May 27, 2013 5:37:13 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(/home/jhuska/workspace_jbossToolsTesting/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/rf500Alpha1testingMvn/WEB-INF/lib/servlet-api-2.5.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
{code}
The issue IMHO relates to RF-12998, which was already solved for showcase.
was:
The archetypes do not work on Tomcats. They work on JBoss AS.
The only notable error is this one from server log:
{code}
INFO: validateJarFile(/home/jhuska/workspace_jbossToolsTesting/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/rf500Alpha1testingMvn/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class
May 27, 2013 5:37:13 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(/home/jhuska/workspace_jbossToolsTesting/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/rf500Alpha1testingMvn/WEB-INF/lib/servlet-api-2.5.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
{code}
The issue IMHO relates to RF-12998, which was already solved for showcase.
> Simpleapp archetype do not work on Tomcat
> -----------------------------------------
>
> Key: RF-13021
> URL: https://issues.jboss.org/browse/RF-13021
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: archetype
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Priority: Blocker
>
> The simple app archetype does not work on Tomcats. They work on JBoss AS.
> The only notable error is this one from server log:
> {code}
> INFO: validateJarFile(/home/jhuska/workspace_jbossToolsTesting/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/rf500Alpha1testingMvn/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class
> May 27, 2013 5:37:13 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
> INFO: validateJarFile(/home/jhuska/workspace_jbossToolsTesting/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/rf500Alpha1testingMvn/WEB-INF/lib/servlet-api-2.5.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
> {code}
> The issue IMHO relates to RF-12998, which was already solved for showcase.
--
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, 10 months
[JBoss JIRA] (RF-13021) Simpleapp archetype do not work on Tomcat
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13021?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13021:
-----------------------------
Description:
The simple app archetype does not work on Tomcats. It works on JBoss AS.
The only notable error is this one from server log:
{code}
INFO: validateJarFile(/home/jhuska/workspace_jbossToolsTesting/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/rf500Alpha1testingMvn/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class
May 27, 2013 5:37:13 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(/home/jhuska/workspace_jbossToolsTesting/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/rf500Alpha1testingMvn/WEB-INF/lib/servlet-api-2.5.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
{code}
The issue IMHO relates to RF-12998, which was already solved for showcase.
was:
The simple app archetype does not work on Tomcats. They work on JBoss AS.
The only notable error is this one from server log:
{code}
INFO: validateJarFile(/home/jhuska/workspace_jbossToolsTesting/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/rf500Alpha1testingMvn/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class
May 27, 2013 5:37:13 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(/home/jhuska/workspace_jbossToolsTesting/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/rf500Alpha1testingMvn/WEB-INF/lib/servlet-api-2.5.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
{code}
The issue IMHO relates to RF-12998, which was already solved for showcase.
> Simpleapp archetype do not work on Tomcat
> -----------------------------------------
>
> Key: RF-13021
> URL: https://issues.jboss.org/browse/RF-13021
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: archetype
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Priority: Blocker
>
> The simple app archetype does not work on Tomcats. It works on JBoss AS.
> The only notable error is this one from server log:
> {code}
> INFO: validateJarFile(/home/jhuska/workspace_jbossToolsTesting/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/rf500Alpha1testingMvn/WEB-INF/lib/jsp-api-2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class
> May 27, 2013 5:37:13 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
> INFO: validateJarFile(/home/jhuska/workspace_jbossToolsTesting/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/rf500Alpha1testingMvn/WEB-INF/lib/servlet-api-2.5.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
> {code}
> The issue IMHO relates to RF-12998, which was already solved for showcase.
--
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, 10 months