[JBoss JIRA] (RF-13018) a4j:commandButton wrong actions performed
by Rob Hare (JIRA)
Rob Hare created RF-13018:
-----------------------------
Summary: a4j:commandButton wrong actions performed
Key: RF-13018
URL: https://issues.jboss.org/browse/RF-13018
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 4.3.2, 4.2.3.Final
Environment: Server: Fedora 17, Jboss AS 7.1.1.Final, Jboss EAP 6.1.0.Beta, Java 1.7.0_15
Browsers: Chrome 26 and Chrome 27 on (Linux & Windows 7), Firefox 20.0 (Linux & Windows 7), IE 9
Reporter: Rob Hare
When an a4j commponent (a4j:commandButton, a4j:jsFunction) is activated, actions of other a4j:commandButtons on the page with type=button will be fired.
For example, pressing either button in the following code will cause both richBean.function1() and richBean.function2() actions.
{noformat}
<h:form id="testForm">
<a4j:commandButton id="button1" type="button" value="Button 1"
action="#{richBean.function1}" />
<a4j:commandButton id="button2" type="button" value="Button 2"
action="#{richBean.function2}" />
</h:form>
{noformat}
Note, if one of the a4j:commandButton is marked immediate, then only one action (possibly the wrong action) will be performed and block others. For instance if an a4j:jsFunction action was being triggered, the a4j:commandButton action may occur making appear that the a4j:jsFunction failed.
--
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-12969) rich:tabPanel: Click on already selected rich:tab causes JavaScript error
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/RF-12969?page=com.atlassian.jira.plugin.s... ]
Jan Papousek closed RF-12969.
-----------------------------
> rich:tabPanel: Click on already selected rich:tab causes JavaScript error
> -------------------------------------------------------------------------
>
> Key: RF-12969
> URL: https://issues.jboss.org/browse/RF-12969
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.2
> Environment: Mojarra 2.1.20
> Reporter: Michael Abele
> Assignee: Brian Leathem
> Priority: Blocker
> Labels: regression
> Fix For: 4.3.2, 5.0.0.Alpha1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Clicking on an already active tab causes a JavaScript error with 4.3.2 CR1.
> The following example works fine with 4.3.1
> {code}
> <rich:tabPanel switchType="ajax">
> <rich:tab name="1">
> </rich:tab>
> <rich:tab name="2">
> </rich:tab>
> </rich:tabPanel>
> {code}
> JavaScript error output in Chrome is:
> {quote}
> Uncaught TypeError: Cannot call method 'onCompleteHandler' of undefined
> (anonymous function)
> serverEventHandler packed.js:529
> (anonymous function) packed.js:505
> (anonymous function) packed.js:488
> (anonymous function) packed.js:456
> (anonymous function) packed.js:488
> sendEvent jsf.js.jsf:1613
> response jsf.js.jsf:2254
> jsf.ajax.response packed.js:656
> richfaces.queue.response packed.js:1170
> jsf.ajax.response packed.js:799
> onComplete jsf.js.jsf:1398
> AjaxEngine.req.xmlReq.onreadystatechange jsf.js.jsf:1379
> {quote}
> JavaScript error in Firefox is
> {quote}
> TypeError: RichFaces.$(...) is undefined
> return new Function("event", handlerCode);
> {quote}
--
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 Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/RF-13009?page=com.atlassian.jira.plugin.s... ]
Jan Papousek updated RF-13009:
------------------------------
Affects Version/s: 4.3.2
> 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.0.0.Alpha1
>
>
> 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-13009) drag and drop inside collapsible subtable causes assertion error
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/RF-13009?page=com.atlassian.jira.plugin.s... ]
Jan Papousek commented on RF-13009:
-----------------------------------
No, it doesn't.
> 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.0.0.Alpha1
>
>
> 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-12784) Showcase readme - update deployment from eclipse part
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12784?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-12784:
----------------------------
Fix Version/s: 5.0.0.Alpha2
(was: 5.0.0.Alpha1)
> Showcase readme - update deployment from eclipse part
> -----------------------------------------------------
>
> Key: RF-12784
> URL: https://issues.jboss.org/browse/RF-12784
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: doc, showcase
> Affects Versions: 4.3.0.Final, 5-Tracking
> Reporter: Juraj Húska
> Assignee: Juraj Húska
> Priority: Trivial
> Fix For: 4.3.3, 5.0.0.Alpha2
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The deployment of the showcase from eclipse needs to be written down in in more details, because it is not trivial:
> An user needs to be aware of:
> * select correct maven profile
> * alter the deployment assembly
> * be aware of wrong context root load in the eclipse browser
> I will send pull request for this one.
--
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-12784) Showcase readme - update deployment from eclipse part
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12784?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč reopened RF-12784:
-----------------------------
This patch wasn't again applied correctly (it was likely rewritten with migration from readme.txt to README.md).
> Showcase readme - update deployment from eclipse part
> -----------------------------------------------------
>
> Key: RF-12784
> URL: https://issues.jboss.org/browse/RF-12784
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: doc, showcase
> Affects Versions: 4.3.0.Final, 5-Tracking
> Reporter: Juraj Húska
> Assignee: Juraj Húska
> Priority: Trivial
> Fix For: 4.3.2, 5.0.0.Alpha1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The deployment of the showcase from eclipse needs to be written down in in more details, because it is not trivial:
> An user needs to be aware of:
> * select correct maven profile
> * alter the deployment assembly
> * be aware of wrong context root load in the eclipse browser
> I will send pull request for this one.
--
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-12784) Showcase readme - update deployment from eclipse part
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12784?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-12784:
----------------------------
Fix Version/s: 4.3.3
(was: 4.3.2)
> Showcase readme - update deployment from eclipse part
> -----------------------------------------------------
>
> Key: RF-12784
> URL: https://issues.jboss.org/browse/RF-12784
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: doc, showcase
> Affects Versions: 4.3.0.Final, 5-Tracking
> Reporter: Juraj Húska
> Assignee: Juraj Húska
> Priority: Trivial
> Fix For: 4.3.3, 5.0.0.Alpha1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The deployment of the showcase from eclipse needs to be written down in in more details, because it is not trivial:
> An user needs to be aware of:
> * select correct maven profile
> * alter the deployment assembly
> * be aware of wrong context root load in the eclipse browser
> I will send pull request for this one.
--
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 Himanshu Bhardwaj (JIRA)
[ https://issues.jboss.org/browse/RF-13017?page=com.atlassian.jira.plugin.s... ]
Himanshu Bhardwaj 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:
<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>
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>
> 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