[JBoss JIRA] (RF-13017) richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible
by Himanshu Bhardwaj (JIRA)
Himanshu Bhardwaj created RF-13017:
--------------------------------------
Summary: 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-13010) Popup panel inside popup panel: button not rendered in IE10
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13010?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-13010:
------------------------------------
There are no errors in the browser console. It works fine if there is only one popup on the page but fails in nested popups. If the button is in the first popup, it is rendered correctly.
I haven't tried two popups side-by-side yet.
> 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-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:
------------------------------------
any error messages in the javascript console? Does this only fail for nested popups? what if the button is in the first popup? or if the two popups are side-by-side?
> 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-12938) Update Shrinkwrap
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12938?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč resolved RF-12938.
-----------------------------
Resolution: Done
> Update Shrinkwrap
> -----------------
>
> Key: RF-12938
> URL: https://issues.jboss.org/browse/RF-12938
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: tests - functional
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 4.3.2, 5.0.0.Alpha1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> Cancelling tests resulted in a ShrinWrap zip file error when trying to re-run the test:
> {quote}
> WARNING: Exception encountered during export of archive
> org.jboss.shrinkwrap.api.exporter.ArchiveExportException: Failed to write asset to output: /WEB-INF/lib/arquillian-warp.jar
> at org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$3.handle(StreamExporterDelegateBase.java:272)
> at org.jboss.shrinkwrap.impl.base.io.IOUtil.closeOnComplete(IOUtil.java:219)
> at org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.processNode(StreamExporterDelegateBase.java:233)
> at org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:105)
> at org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:109)
> at org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:109)
> at org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.doExport(AbstractExporterDelegate.java:95)
> at org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.access$001(StreamExporterDelegateBase.java:50)
> at org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$1.call(StreamExporterDelegateBase.java:121)
> at org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$1.call(StreamExporterDelegateBase.java:116)
> at org.jboss.shrinkwrap.impl.base.exporter.zip.JdkZipExporterDelegate$1.call(JdkZipExporterDelegate.java:124)
> at org.jboss.shrinkwrap.impl.base.exporter.zip.JdkZipExporterDelegate$1.call(JdkZipExporterDelegate.java:118)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: java.io.IOException: Pipe closed
> at java.io.PipedInputStream.checkStateForReceive(PipedInputStream.java:261)
> at java.io.PipedInputStream.receive(PipedInputStream.java:227)
> at java.io.PipedOutputStream.write(PipedOutputStream.java:149)
> at java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:253)
> at java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:211)
> at java.util.zip.ZipOutputStream.write(ZipOutputStream.java:314)
> at org.jboss.shrinkwrap.impl.base.io.IOUtil.copy(IOUtil.java:139)
> at org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$2.execute(StreamExporterDelegateBase.java:261)
> at org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$2.execute(StreamExporterDelegateBase.java:233)
> at org.jboss.shrinkwrap.impl.base.io.IOUtil.closeOnComplete(IOUtil.java:217)
> ... 15 more
> {quote}
> [~alrubinger] pointed out that our Shrinkwrap version was old and out of date. We need to upgrade to the latest Shrinkwrap to overcome this issue.
--
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