JSF portlet: namingContainer - duplicate id error

Hi Experts,
I am developing a JSF portlets having only a click button. When I click the button, it throws duplicate id exception. If I don't use namingContainer tag, it runs well. Here is the JSP code and exception:
JSP:
<%@ page language="java" contentType="text/html;charset=UTF-8"%>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
<%@ taglib uri="http://bea.com/faces/adapter/tags-naming" prefix="netuix"%>
<f:view>
     <netuix:namingContainer id="simpleJsfContainer">
          <h:outputText value="Simplest JSF Portlet" />
          <h:form>
               <h:commandButton id="postbackButton" value="Click here" />
          </h:form>
     </netuix:namingContainer>
</f:view>
Exception
opening /simplejsf/simpleJsf.faces.
The source of this error is:
java.lang.IllegalStateException: Client-id : simpleJsf_1 is duplicated in the faces tree. Component : simpleJsf_1, path: {Component-Path : [Class: javax.faces.component.UIViewRoot,ViewId: /simplejsf/simpleJsf.jsp][Class: com.bea.portlet.adapter.faces.component.naming.NamingContainerComponent,Id: simpleJsf_1]}
     at org.apache.myfaces.application.jsp.JspStateManagerImpl.checkForDuplicateIds(JspStateManagerImpl.java:350)
     at org.apache.myfaces.application.jsp.JspStateManagerImpl.checkForDuplicateIds(JspStateManagerImpl.java:365)
     at org.apache.myfaces.application.jsp.JspStateManagerImpl.saveSerializedView(JspStateManagerImpl.java:305)
     at org.apache.myfaces.taglib.core.ViewTag.doAfterBody(ViewTag.java:122)
     at jsp_servlet._simplejsf.__simplejsf._jsp__tag0(__simplejsf.java:133)
     at jsp_servlet._simplejsf.__simplejsf._jspService(__simplejsf.java:91)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at org.apache.beehive.netui.pageflow.PageFlowPageFilter.continueChainNoWrapper(PageFlowPageFilter.java:455)
     at org.apache.beehive.netui.pageflow.PageFlowPageFilter.runPage(PageFlowPageFilter.java:432)
     at org.apache.beehive.netui.pageflow.PageFlowPageFilter.doFilter(PageFlowPageFilter.java:284)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:503)
     at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
     at com.bea.portlet.adapter.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:110)
     at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:234)
     at com.bea.portlet.adapter.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:77)
     at org.apache.beehive.netui.pageflow.faces.internal.PageFlowViewHandler.renderView(PageFlowViewHandler.java:203)
     at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384)
     at com.bea.portlet.adapter.faces.FacesContentStubImpl.render(FacesContentStubImpl.java:354)
     at com.bea.netuix.servlets.controls.content.FacesContent.beginRender(FacesContent.java:420)
     at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:485)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
     at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
     at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
     at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
     at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
     at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
     at jsp_servlet._framework._skeletons._bighorn.__flowlayout._jspService(__flowlayout.java:175)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:505)
     at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
     at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
     at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
     at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
     at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
     at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
     at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
     at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
     at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
     at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
     at jsp_servlet._framework._skeletons._bighorn.__gridlayout._jspService(__gridlayout.java:219)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:505)
     at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
     at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
     at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
     at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
     at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
     at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208)
     at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:162)
     at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
     at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
     at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
     at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251) at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:686) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.bea.portal.tools.servlet.http.HttpContextFilter.doFilter(HttpContextFilter.java:60) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:336) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3502) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2186) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2092) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Could you please tell me what's the problem?
Thanks
Tridib
Edited by: Tridib on 12-Feb-2010 08:48

Alright. I found it! I changed JSF implementation from MyFaces to Sun Reference implementation 1.1 and it worked! For details about how to set sun implementation as JSF implementation in portal project refer to section 2.2 in [White Paper|http://blogs.oracle.com/tridib_samanta/weblogic-portal-jsf-whitepaper.pdf] .
Edited by: Tridib on 16-Feb-2010 06:32

Similar Messages

JSF Portlet Bridge Error

Hi ,
I have developed a JSF portlet bridge page , which i am trying to consume in another WebCenter App. However when i open the consuming page i get the following error in the server console
SOAP call returned the fault : no serializer is registered for (interface javax.xml.soap.SOAPElement, {urn:oasis:names:tc:wsrp:v1:types}releaseSessionsResponse). Check that the producer URL has been correctly specified, that the producer server machine and producer container are running, that the producer application is deployed correctly, and that the client can reach the server if behind a firewall.
     at oracle.portlet.client.connection.wsrp.ActivityServerWrapper.checkAndReturnHttpException(ActivityServerWrapper.java:61)
     at oracle.portlet.client.connection.wsrp.ActivityServerWrapper.initCookie(ActivityServerWrapper.java:1963)
     at oracle.portlet.client.techimpl.wsrp.WSRPInitCookiePipe.execute(WSRPInitCookiePipe.java:119)
     at oracle.portlet.client.techimpl.wsrp.WSRPInitCookiePipe.pre(WSRPInitCookiePipe.java:51)
any idea on how to resolve this?
thanks in advance

Hi Kunai,
Can you take a look at this blog entry featuring a step-by-step screen cast and see if it clears things up? I'd be happy to answer your questions if there's any left.
Regards,
Peter

Announcing: Developing JSF Portlets with WebLogic Portal Whitepaper

Just Released: Developing JSF Portlets with WebLogic Portal Whitepaper
A supplemental developer's guide has been published to help guide WLP 10.x customers that wish to use JSF as the web framework for building portlets on WebLogic Portal. This is a sizable document (150 pages) that covers a large number of topics. It also coaches developers on best practices and common pitfalls.
Important: It also clarifies the supported configuration of JSF within Portal Web Projects. Workshop for WebLogic by default configures a web project in a configuration that is not supported by WebLogic Portal. The guide explains how to address this:
* Change from the unsupported MyFaces JSF implementation to the supported Sun Reference Implementation (RI)
* Change from the unsupported "client" STATE_SAVING_METHOD to the supported "server"
The guide can be downloaded here:
http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf
To help internet searches locate this document, the table of contents is reproduced below:
Introduction
1.1. Prerequisites...................................................................... 8
1.2. Applicable Versions............................................................ 8
1.3. Native Portlet Bridges and Standard Portlet Bridges .......... 8
1.4. JSF Portlet Support Roadmap ........................................... 9
1.5. Whitepaper Structure ....................................................... 10
1.6. Look Before You Leap ..................................................... 10
1.7. For More Information........................................................ 10
Part 1: Converting JSF Applications into Portlets
2. IDE Support for JSF Portlets Chapter ...................................... 12
2.1. Workshop for WebLogic – WebLogic Portal's Supported IDE 12
2.2. Workshop Features for JSF Support in WebLogic Portal.. 12
3. Introduction to JSF Portlets Chapter ........................................ 18
3.1. Creating Your First JSF Portlet......................................... 18
3.2. Essentials of JSF Portlet Views........................................ 21
3.3. WebLogic Portal Artifacts................................................. 22
4. Configuring JSF within WebLogic Portal Chapter..................... 24
4.1. JSF Library Modules in WebLogic Server ........................ 24
4.2. Installing the JSF Libraries into a Portal Web Project ....... 25
4.3. JSF Configuration Settings............................................... 27
4.4. Configuring JSF 1.2 ......................................................... 29
4.5. Building an Unsupported JSF Implementation Library Module 31
4.6. Faces Configuration is Web Application Scoped.............. 31
5. Navigation within a JSF Portlet Chapter................................... 33
5.1. Navigating within a Portlet with the JSF Controller ........... 33
5.2. Redirects.......................................................................... 34
6. Namespacing Chapter ............................................................. 35
6.1. Namespacing Managed Bean Names.............................. 35
6.2. Client ID Namespacing with the View and Subview Components 35
6.3. Client ID Namespacing with the WLP NamingContainer .. 36
7. Logging, Iterative Development, and Debugging Chapter ........ 39
7.1. Logging............................................................................ 39
7.2. Iterative Development ...................................................... 39
7.3. Debugging ....................................................................... 40
8. Custom JavaScript Chapter ..................................................... 42
8.1. DOM Manipulation within a JSF ....................................... 42
8.2. Form Validation within a JSF Portlet ................................ 45
9. Preparing JSF Portlets for Production Chapter ........................ 46
9.1. Configuration.................................................................... 46
9.2. Performance and Scalability............................................. 47
9.3. Security............................................................................ 49
9.4. Localization...................................................................... 50
Part 2: Interacting with the Portal Environment
10. Native Bridge Architecture Chapter ...................................... 54
10.1. Container Architecture Overview.................................. 54
10.2. Container Architecture.................................................. 54
10.3. Container Interactions .................................................. 55
11. Interportlet Communication Chapter .................................... 56
11.1. Using Session and Request Attributes for IPC (Anti-pattern) 56
11.2. Using the WLP Event Facility for IPC with JSF Portlets 56
11.3. Notifications ................................................................. 60
11.4. Comparison of the IPC Approaches ............................. 60
12. Scopes Chapter ................................................................... 62
12.1. Conceptual Scopes for Standard JSF Applications ...... 62
12.2. Conceptual Scopes for Portal Applications................... 63
12.3. Implementation Patterns for Portal Scopes .................. 63
13. State Sharing Patterns Chapter ........................................... 66
13.1. State Sharing Concepts ............................................... 66
13.2. HttpSession Versus HttpServletRequest ...................... 66
13.3. Base Code for HttpSession Patterns ............................ 67
13.4. Single Portlet Pattern ................................................... 68
13.5. Multiple Portlet Patterns ............................................... 69
14. Rendering Lifecycles Chapter .............................................. 77
14.1. WLP and JSF Lifecycles .............................................. 77
14.2. Invocation Order of WLP and JSF Lifecycle Methods... 77
14.3. Accessing WLP Context Objects from JSF Managed Beans 78
15. Portal Navigation Chapter .................................................... 80
15.1. Programmatically Constructing JSF Portlet URLs ........ 80
15.2. Changing the Active Portal Page.................................. 80
15.3. Redirects within a Portal............................................... 83
16. Ajax Enablement Chapter .................................................... 85
16.1. Ajax in JSF Portlets...................................................... 85
16.2. Partial Page Rendering Pattern.................................... 85
16.3. Stateless API Request Pattern ..................................... 86
16.4. Portlet Aware API Request Pattern .............................. 87
16.5. Controlling the WLP Ajax Framework........................... 91
17. Additional WLP Features Chapter........................................ 93
17.2. Portlet Container Features ........................................... 93
17.3. Portal Container Features ............................................ 98
18. Example: Implementing a Login Portlet Chapter .................. 99
18.1. Login Portlet Motivation................................................ 99
18.2. Login Portlet Design..................................................... 99
18.3. Login Portlet Implementation...................................... 101
Part 3: Integrating Third Party Libraries
19. Integration Overview Chapter............................................. 111
19.1. Types of Libraries....................................................... 111
19.2. Roadmap for MyFaces Trinidad and ADF Faces Rich Client 111
20. Using the Facelets View Technology Chapter.................... 113
20.1. Introduction to Facelets .............................................. 113
20.2. Configuring Facelets Support ..................................... 113
21. Using the Apache MyFaces Tomahawk Component Library Chapter 115
21.1. What is Apache MyFaces Tomahawk? ...................... 115
21.2. Support for Tomahawk in WLP................................... 115
21.3. Tomahawk Component List........................................ 116
21.4. Installing and Configuring Tomahawk......................... 119
21.5. Resolving the Duplicate ID Issue................................ 120
21.6. Referring to Resources .............................................. 120
21.7. forceId Attribute.......................................................... 124
21.8. File Upload................................................................. 125
22. Using the Apache Beehive Navigation Controller Chapter . 126
22.1. Apache Beehive Page Flow ....................................... 126
22.2. JSF and Page Flows .................................................. 126
22.3. Configuring the JSF Integration with Page Flows ....... 127
Appendices
23. Appendix 1: Consolidated List of Best Practices ................ 130
24. Appendix 2: Known Issues and Workarounds.................... 132
24.1. CR383659, CR383662 Inconsistent failures with JSF portlets 132
24.2. CR342124: IllegalStateException due to duplicate client-id 132
24.3. CR384916: IllegalStateException due to duplicate client-id when using certain components such as Tomahawk and Trinidad...... 133
24.4. CR361477 Problems with the integration of JSF portlets with Apache Beehive Page Flows.................................................................. 133
24.5. CR377945 JSF 1.2 suffers from a memory leak during iterative development .............................................................................. 134
25. Appendix 3: The JSFPortletHelper Class ........................... 135
26. Appendix 4: The CleanupPhaseListener Class .................. 147

Hi Peter!
First, I wish to thank you for the great work.
We followed your whitepaper and managed to deploy a JSF portlet on WLS.
But we are not able to register it (consume it) as remote portlet in Oracle Portal 10.1.4. The error log is as follows:
An error occurred while trying to refresh the provider. (WWC-43190)
An error occurred during the call to the WSRP Provider:
java.rmi.RemoteException: serialization error: serialization error:
unexpected null value for literal data; nested exception is:
serialization error: serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
unexpected null value for literal data
Java stack trace from root exception:
unexpected null value for literal data
at
oracle.webdb.wsrp.RegistrationContext_LiteralSerializer.doSerialize(RegistrationContext_LiteralSerializer.java:107)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
oracle.webdb.wsrp.GetServiceDescription_LiteralSerializer.doSerialize(GetServiceDescription_LiteralSerializer.java:88)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
com.sun.xml.rpc.client.StreamingSender._writeRequest(StreamingSender.java:473)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:62)
at
oracle.webdb.wsrp.WSRP_v1_ServiceDescription_PortType_Stub.getServiceDescription(WSRP_v1_ServiceDescription_PortType_Stub.java:63)
at
oracle.webdb.wsrp.client.design.v1.OraWSRP_v1_ServiceDescription_PortType.getServiceDescription(Unknown
Source)Do you have any idea why this happens? Or you can provide some useful links to WLP -Oracle Portal federation?
Thank you and best regards,
PaKo

Jsf-naming:namingContainer leads to ClassCastException

Hi,
I am having a problem creating a JSF-Portlet (JSF 1.2) in a WebLogic Portal 10.3.2
I am trying to create a portal JSF-Portlet using the jsf-1.2_09 libraries (WebLogic default). The Portlet works great until I try to integrate the <jsf-naming:namingContainer tag into my jsp.
I am using the Oracle Tutorial "Developing JSF Portlets with WebLogic Portal"
The JSP is really simple
*<code>*
<%@ page language="java" contentType="text/html;charset=UTF-8"%>
<%@ taglib prefix="f" uri="http://java.sun.com/jsf/core"%>
<%@ taglib prefix="h" uri="http://java.sun.com/jsf/html"%>
<%@ taglib prefix="jsf-naming" uri="http://bea.com/faces/adapter/tags-naming"%>
<f:view>
<jsf-naming:namingContainer id="loginJSFPortlet" >
<h:outputText value="Login Test"/>
<h:form>
<h:commandButton id="loginButton" value="Anmelden" action="login"/>
</h:form>
</jsf-naming:namingContainer>
</f:view>
*</code>*
When calling the portal desktop the following exception is thrown
*<exception>*
<23.06.2010 16:25 Uhr MESZ> <Error> <ServletContext-/eKimWebTest> <BEA-000000> <Exception thrown in doFacesRequest:render
javax.faces.FacesException: java.lang.ClassCastException: com.bea.portlet.container.RenderRequestImpl
     at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:128)
     at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
     at org.apache.myfaces.portlet.faces.bridge.BridgeImpl.doFacesRender(BridgeImpl.java:906)
     at org.apache.myfaces.portlet.faces.bridge.BridgeImpl.doFacesRequest(BridgeImpl.java:769)
     at javax.portlet.faces.GenericFacesPortlet.doBridgeDispatch(GenericFacesPortlet.java:645)
     Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassCastException: com.bea.portlet.container.RenderRequestImpl
     at com.bea.portlet.adapter.faces.ScopedIdSupport.getScopeKey(ScopedIdSupport.java:74)
     at com.bea.portlet.adapter.faces.taglib.naming.internal.NamingContainerTagImpl.doStartTag(NamingContainerTagImpl.java:200)
     at com.bea.portlet.adapter.faces.taglib.naming.NamingContainerTag.doStartTag(NamingContainerTag.java:101)
     at jsp_servlet.__login._jsp__tag1(__login.java:165)
     at jsp_servlet.__login._jsp__tag0(__login.java:127)
     Truncated. see log file for complete stacktrace
>
*</exception>*
When I don't use the namingContainer tag everything works fine.
Any Idea what's going wrong here?
Thkx in advance
Edmund
Edited by: egeesken on 23.06.2010 07:38

Hello Edmund,
The "jsf-naming" tag library you are importing is from the WLP "native" JSF 1.1 portlet bridge, which uses an entirely different way to render JSF as portlets than the new JSR329 JSF 1.2 to Java Portlet 2.0 bridge that you are using (the "GenericFacesPortlet"). Unfortunately, the jsf-naming tags are not compatible with the JSR329 bridge.
I'm not a JSF expert, so unfortunately I can't suggest an equivalent way of doing what you want to do, but I am sure it is possible. Hopefully someone else on here with JSF expertise can help you out.
Kevin

Need to add as a WSRP Connection in JDev for Weblogic Portal JSF Portlets.

I am trying to register WLP 10.3.4 JSF Portlets as a WSRP connection in JDev Webcenter 11.1.1.6 Portal Framework application . The below are steps:
-Created Simple WLP Application with JSF Portlets and deployed them on WLS 10.3.4 domain.
-The WSDL url available is http://localhost:7003/TEST_WEB_PORTAL/producer?wsdl
-Now Open JDev and created WCP Framwork app
-Under Application Resource, right click on Connections -> New Connection -> WSRP Producer.
-Click Next on step1 -> Enter WSDL URL on Step 2 and then click next on next 3 screens.
-It tries to register but ended up with below exception:
3-Dec-2012 12:48:03 oracle.adfdtinternal.model.portlet.wizards.registration.wsrp.WSRPProducerRegUtil registerProducer
WARNING:
oracle.portlet.client.persistence.PersistenceException: oracle.mds.core.ConcurrentMOChangeException: MDS-00165: metadata Object "/oracle/adf/portlet/WsrpPortletProducer0/portletDefs/portletPortletproducer/markupTypes/markupType0_texthtml.pxml" has changed
MDS-00512: failure to create document /oracle/adf/portlet/WsrpPortletProducer0/portletDefs/portletPortletproducer/markupTypes/markupType0_texthtml.pxml because file C:\Oracle\PS5\mywork\testSR3-6514764665\mds\oracle\adf\portlet\WsrpPortletProducer0\portletDefs\portletPortletproducer\markupTypes\markupType0_texthtml.pxml already exists
     at oracle.portlet.client.persistenceimpl.mds.MDSPersistenceContext.commit(MDSPersistenceContext.java:473)
     at oracle.portlet.client.beanimpl.persistence.PersistenceBeanContext.commit(PersistenceBeanContext.java:128)
     at oracle.portlet.client.adapter.simple.SimpleAdapter.commit(SimpleAdapter.java:465)
     at oracle.adfinternal.model.portlet.manager.PortletProviderManager.commit(PortletProviderManager.java:1487)
     at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerPortletProvider(PortletProviderManager.java:1647)
     at oracle.adfinternal.model.portlet.manager.PortletProviderManager.registerPortletProvider(PortletProviderManager.java:597)
     at oracle.adfdtinternal.model.portlet.wizards.registration.wsrp.WSRPProducerRegUtil.registerProducer(WSRPProducerRegUtil.java:308)
     at oracle.adfdtinternal.model.portlet.wizards.registration.wsrp.WSRPProducerRegistrationWizard$1.doWork(WSRPProducerRegistrationWizard.java:863)
     at oracle.ide.dialogs.ProgressRunnable.run(ProgressRunnable.java:161)
     at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:655)
     at java.lang.Thread.run(Thread.java:662)
Caused by: oracle.mds.core.ConcurrentMOChangeException: MDS-00165: metadata Object "/oracle/adf/portlet/WsrpPortletProducer0/portletDefs/portletPortletproducer/markupTypes/markupType0_texthtml.pxml" has changed
MDS-00512: failure to create document /oracle/adf/portlet/WsrpPortletProducer0/portletDefs/portletPortletproducer/markupTypes/markupType0_texthtml.pxml because file C:\Oracle\PS5\mywork\testSR3-6514764665\mds\oracle\adf\portlet\WsrpPortletProducer0\portletDefs\portletPortletproducer\markupTypes\markupType0_texthtml.pxml already exists
     at oracle.mds.core.UpdateableMOContent.constructConcurrentMOChangeException(UpdateableMOContent.java:1376)
     at oracle.mds.core.UpdateableMOContent.saveMOContent(UpdateableMOContent.java:1143)
     at oracle.mds.core.MDSTransaction.flushChangesToPTrans(MDSTransaction.java:851)
     at oracle.mds.core.MDSTransaction.internalCommit(MDSTransaction.java:2928)
     at oracle.mds.core.MDSSession.flushChanges(MDSSession.java:1022)
     at oracle.mds.core.MDSSession.flushChanges(MDSSession.java:850)
     at oracle.portlet.client.persistenceimpl.mds.MDSSessionWrapper.flushChanges(MDSSessionWrapper.java:61)
     at oracle.portlet.client.persistenceimpl.mds.MDSPersistenceContext.commit(MDSPersistenceContext.java:456)
     ... 10 more
Caused by: oracle.mds.persistence.DocumentExistsException: MDS-00512: failure to create document /oracle/adf/portlet/WsrpPortletProducer0/portletDefs/portletPortletproducer/markupTypes/markupType0_texthtml.pxml because file C:\Oracle\PS5\mywork\testSR3-6514764665\mds\oracle\adf\portlet\WsrpPortletProducer0\portletDefs\portletPortletproducer\markupTypes\markupType0_texthtml.pxml already exists
     at oracle.mds.internal.persistence.file.Fil
I have followed the steps given in the http://docs.oracle.com/cd/E26806_01/wlp.1034/e14235/chap_webcenter_interop.htm#BABGIIIJ for preventing User Authentication error by creating user of PortalSystemAdministrator group but did not help.
Please let me know if anyone have faced this exception or any pointers.
Thanks
Kamal Gulati

Hi,
I tried creating a simple JSF portlet and I can able to register and it is working Fine, but my teammet got the same issue like you :) . While Analyzing what I found is , the location where we created the portlet in weblogic portal. If you created your portlet directly under WebContent folder then this issue is coming up, so try to create the portlet in a folder inside the WebContent folder, say create a folder with name portlets under webcontent and create the JSF portlet inside that portlets folder.
Now start the server and register the same in WebCenter, you will not get that exception. I am going to raise a ticket with Oracle about this issue and get the root cause.
Thanks
Karthikeyan

JSF Portlet default view (FacesPortlet)

If we are creating a JSF based portlet using Sun's JSF RI and jsf-portlet bridge, then in portlet.xml we define this:
{color:#0000ff}
<portlet>
<portlet-name>myPortlet</portlet-name>
<portlet-class>
com.sun.faces.portlet.FacesPortlet
</portlet-class>
<init-param>
<name>com.sun.faces.portlet.INIT_VIEW</name>
<value>/default.jsp</value>
</init-param>
</portlet>{color}
But in faces-config.xml, we define our navigation using navigation-cases, like this:
{color:#008000}
{color}
{color:#0000ff}
<navigation-rule>
<navigation-case>
<from-outcome>exceptionNavigation</from-outcome>
<to-view-id>/error.jsp</to-view-id>
</navigation-case>
</navigation-rule>{color}
What I'm trying to do is this:
I want to programmatically access the navigation rule which references the default view.
I can fish out the INIT_VIEW value using:
{color:#0000ff}
String initView = application.getInitParameter(com.sun.faces.portlet.LifecycleImpl.INIT_VIEW_PARAMETER);{color}
But this returns me the actual jsp name, ie: {color:#0000ff}/default.jsp{color}
This means I cannot use faces to navigate to it, like this:
{color:#0000ff}
application.getNavigationHandler()
.handleNavigation( context, null, initView );{color}
As the navigation model is core to JSF, would it not be better for FacesPortlet to require, in portlet.xml,
a global navigation-case rather than just a jsp page?
This would apply to EDIT_VIEW, HELP_VIEW, etc.
In order to implement the functionality I want, I have to specify my default or INIT_VIEW page twice, once in portlet.xml and a second time in faces-config.xml. What is more, I cannot use this as independent code, because I have to know or prescribe the navigation-case containing the default/initView to the user of the code:
{color:#0000ff}
<navigation-case>
<from-outcome>com.sun.faces.portlet.INIT_VIEW</from-outcome>
<to-view-id>/default.jsp</to-view-id>
</navigation-case>{color}
Regards,
Stewart
PS: How do I display code correctly using this editor?

I have answered my own question. This is how to programmatically access the INIT_VIEW jsp in this situation:
ExternalContext econtext = context.getExternalContext();
String initViewId = (String) econtext.getRequestMap().get(
(String) econtext.getRequestMap().get(
com.sun.faces.portlet.LifecycleImpl.INIT_PARAMETER ));
UIViewRoot viewRoot = context.getApplication().getViewHandler().createView(context, initViewId);
context.setViewRoot(viewRoot);
context.renderResponse();
It the viewId IS the jsp name, and navigation can be achieved directly on the jsp name using the ViewHandler class. This is what the NavigationHandler does, under the bonnet (sorry, hood).
Give myself a Duke Star!
:-)

JSF portlet library in JSF 1.1

1. Is JSF portlet library part of released binary for JSF 1.1?
2. Is it supposed to be? Is SUN going to support this library? and also ship in binary form?
If answer to 2 is yes where is the binary for 1.1 released bits?

Dear Jayashri,
I'm getting the following exception:
500 Internal Server Error
javax.servlet.jsp.JspException
at com.sun.faces.taglib.jsf_core.ViewTag.doStartTag(ViewTag.java:117)
at seguridad.Login._jspService(Login.jsp:5)
[seguridad/Login.jsp]
I'm getting it very often, in several JSPs, in a randomly fashion. I'm using JSF 1.1_01, running on Oracle OC4J.
I downloaded the JSF 1.1 source code and started to research it. I found that ViewTag.java is calling the doStartTag() method from UIComponentTag.java. In the latest class, there are 3 cases where am exception is being thrown. Two of them show a "PENDING - i18n" comment, like if it was not finished by the developers.
I found you CVS developer ID in some of the source code, so I thought about searching for you on the sun forums and write you. Luckily, I found you.
Question: This is a bug, right? Is this related to i18n? I'm running my JSF pages on Spanish (<f:view locale="es-es">), so I guess this is in fact an i18n.
What can I do to avoid this situation? Is there a fix?
PLEASE help me, we are developing a very critical app
Brian

JSF Portlet with RichFaces implementation

I am trying to build a JSF 1.1 portlet with RichFaces implementation.
Although, the portlet gets displayed with out any errors. I do not see the RichFaces capabilities getting executed such as "A4J:support" tag is not doing an Ajax based form validation.
Any help on this? Are there any completed PoCs on RF compatibility with JSF portlets.
Thanks
Rajesh

Hello,
Have you resolved your issue ? I am also trying to run a RichFaces-based webapp on an Oracle portal (WCI) and I have some troubles.
If you have time to look at my problem, I created a post here Oracle JSF Bridge with JBoss Richfaces .
Thanks
K.L.

Developing JSF Portlets with WebLogic Portal (Oracle White paper May 2009)

I have created a simple JSF Portlet following the steps delineated in paragraph 3.1.1 Creating a JSF Enabled WLP Web Project of the white paper mentioned above. I used Workshop for Weblogic 10gR3. When I tried to deploy that very simple portlet and portal I got this error message :
"!MESSAGE Unable to register J2EE shared library C:\bea\wlportal_10.3\samples\lib\j2ee-modules\wlp-sample-lookandfeel-web-lib.war".
Clearly the folder and file "samples\lib\j2ee-modules\wlp-sample-lookandfeel-web-lib.war" are not under my "C:\bea\wlportal_10.3". My question is where do I download it? Where does it come from?
Thanks in advance.

Maybe you did not include the samples when you installed Oracle WebLogic Portal? Now that this is an Oracle product, samples are not installed or configured by default. This is a change in policy from when WebLogic Portal was a BEA thing, so it takes some getting used to and there are probably plenty of places where documentation and papers could be enhanced to emphasize this.
In addition, it looks like there might be an error in the white paper with respect to configuring your web app to include samples. I don't see any mention of taking an extra step to include the sample facets in your portal app. This oversight may have been caused by the author working with a pre-release of Oracle WebLogic Portal that had not yet been "Oracle-ized" enough to get the default samples out of there. In the old days, I think the samples were automatically included in your portal web app.
To get the samples in a new portal web app while you are creating it with the IDE you can click the "Modify..." button on the first dialog. It is next to the "Configuration" text area. This pops up a dialog that lets you select the "Weblogic Portal Samples" facet for your web app.
To get the samples in an existing portal web app after it has been created, right click the app in the IDE, click "Properties...", click "Project Facets", and select the "Weblogic Portal Samples".
Sorry, I'm not sure what the remedy is for getting samples into an installed product that was not installed with the samples. Unfortunately, I think that is the problem that you need solved. Sorry about that. Hopefully you are working in a test or dev environment that makes it easy to blow away old installations and start over? If not, then maybe install it with samples someplace else and copy the samples/... dir over to your other install?

BI 7.0 - Duplicate Record Error while loading master data

I am working on BI 7.0 and I am trying to load master data to an info object.
I created an Infopackage and loaded into PSA.
I created transformation and DTP and I get an error after I execute the DTP about duplicate records.
I have read all previous threads about duplicate record error while loading master data and most of the them suggested to check 'Ignore duplicate records' option in the infopackage. But in 7.0, I can only load to PSA with infopackage and it doesn't have any option for me to ignore duplicate records.
My data is getting loaded to PSA fine and I get this error while loading to info object using DTP.
I would appreciate your help to resolve this issue.
Regards,
Ram.

Hi,
Refer:
http://help.sap.com/saphelp_nw2004s/helpdata/en/45/2a8430131e03c3e10000000a1553f6/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/d0/538f3b294a7f2de10000000a11402f/frameset.htm
With rgds,
Anil Kumar Sharma .P

Why don't responseHeader's works in JSF Portlet

Hi All,
I have a JSF portlet where i want to save the contents of my Text area on the click of a button to a word document.(IBM Websphere portal) <h:inputTextarea id="text1" value="#{pc_TextAreaView.textAreaValue}" rows="10" cols="50" /> <h:commandButton id="save" value="Save As Word" action="#{pc_TextAreaView.SaveAsWord}"/> In my page bean i have written the follwoing code but the response.setHeader() doesn't seem to work.I am not getting any pop dialog and i cannot save my file.Please let me know what is wrong in this code snippet.How can i make it work in my portlet.
public String SaveAsWord() {
FacesContext context = FacesContext.getCurrentInstance();
HttpServletResponse response = (HttpServletResponse)context.getExternalContext().getResponse();
response.setContentType("application/vnd.ms-word");
     response.setHeader("Content-Disposition", "attachment; filename=myfile.doc");
     response.setHeader("Cache-Control", "no-cache");
     try{
     byte[] buf=new byte[4*1024];
     InputStream inStream=new ByteArrayInputStream(textAreaValue.getBytes());
     OutputStream outStream=response.getOutputStream();
     int sizeRead;
     while ( ( sizeRead=inStream.read(buf, 0, buf.length) ) != -1 )
       outStream.write(buf, 0, sizeRead);
     inStream.close();
     outStream.close();
     catch(IOException ex){
      ex.printStackTrace();
     return null;
}Best Regards,
Pallavi

Hi ,
I am working with jsf 1.2 and jasper 3.0.
For this problem just try with "aFacesContext.responseComplete();" method. This will work!
Here is my code for generating pdf file report.
demoreport.jsp code:
<h:commandLink immediate="true" actionListener="#{reportGenerator.generateReport}">
                              <h:outputText value="Generate Report"/>
                         </h:commandLink>Here is bean method: (ReportGenerator.java)
Note: Services is the user defined class for getting connection obj.
public void generateReport(ActionEvent actionEvent)
                                   throws ClassNotFoundException, SQLException, IOException,JRException
          Connection connection;
          FacesContext aFacesContext = FacesContext.getCurrentInstance();
          HttpServletResponse response = (HttpServletResponse)aFacesContext.getExternalContext().getResponse();
          ServletContext context = (ServletContext)aFacesContext.getExternalContext().getContext();
          String reportFileName = context.getRealPath("/reports/DemoReport.jasper");
          System.out.println("reportFileName: "+ reportFileName);
          InputStream reportStream = aFacesContext.getExternalContext().getResourceAsStream("/reports/DemoReport.jasper");
          ServletOutputStream servletOutputStream = response.getOutputStream();
          //Class.forName("com.mysql.jdbc.Driver");
          connection = Services.getConnection(); //get the db connection.
          try{
          JasperRunManager.runReportToPdfStream(reportStream,servletOutputStream, new HashMap(),connection);
          catch(JRException lJRException){
               System.out.println("while run report");
               lJRException.printStackTrace();
          //connection.close();
          response.setContentType("application/pdf");
          response.setHeader("Content-disposition","attachment; filename=DemoReport.pdf");
          servletOutputStream.flush();
          servletOutputStream.close();
          aFacesContext.responseComplete();
     }Regards,
Nils

Adobe Acrobat 8 Form Duplicate text error

Hello World!
I work for a school with 200+ computers installed with **. The problem I'm having is when a user downloads a PDF form from our web page and goes to start inserting data in the fields the text just duplicates in all the boxes. If you try and delete the text from any of the boxes it delets everything. I've tried repairing the install by running the original installer file. I've even reinstalled a test system and still duplicate this error. Please let me know if there is any other information I can provide that will help you help me.
Windows XP SP3
Office 2007
Adobe Acrobat 8

Hi,
This forum is not for Acrobat product.
Plaese post your question again in http://forums.adobe.com/community/acrobat if you haven't.
Thanks,
-- Hiroshi

IsUserInRole from WC Portal to consumed JSF Portlet

Hi experts,
I'm trying to retrieve, the J2EE Roles [ Enterprise Roles a.k.a Security Realm "Groups" of a logged in user ]
from from consumer Webcenter Portal Application into a Producer JSF Portlet.I have seen there were many posts mentioning that this isUserInRole method always return false. I'm also facing the same problem.
My configurations are following -
Portlet Producer App
web.xml
<security-role>
<description>RelationManager</description>
<role-name>RM</role-name>
</security-role>
<security-role>
<description>Team Leader</description>
<role-name>TL</role-name>
</security-role>
portlet.xml
<security-role-ref>
<role-name>RM</role-name>
<role-link>RM</role-link>
</security-role-ref>
weblogic.xml /* Have tried with & without creating this descriptor, but no luck */
<security-role-assignment>
<role-name>RM</role-name>
<principal-name>RM</principal-name> /* I have defined a weblogic group by the name "RM" within defaultAuthenticator and assigned testUser to it. */
</security-role-assignment>
WC Consumer PortalApp
web.xml
<security-role>
<role-name>RM</role-name>
</security-role>
weblogic.xml
<security-role-assignment>
<role-name>RM</role-name>
<principal-name>RM</principal-name> /* Since its the same WLS Server the same group as above will hold good */
</security-role-assignment>
+ I have done the mapping of UserGroups of the Portlets to J2EE Roles of Webcenter Portal consumer during Portlet Registration process.
I have a requestScoped managedBean within my JSFPortlet where I'm retrieving the user Principal and Roles -
public String getLoggedInUser() {
FacesContext facesContext = FacesContext.
getCurrentInstance();
ExternalContext ectx = facesContext.getExternalContext();
PortletRequest portletRequest = (PortletRequest)ectx.getRequest();
return ( portletRequest.getUserPrincipal().getName());
public String getPortletUserRole(){
FacesContext facesContext = FacesContext. getCurrentInstance();
ExternalContext externalContext = facesContext.getExternalContext();
PortletRequest portletRequest = (PortletRequest)externalContext.getRequest();
if ( portletRequest.isUserInRole ("RM") == true ) return "RM" ;
else return "";
Results :
The getLoggedInUser returns ""
And so does the getPortletUserRole method.
What am I missing and whether this is the correct approach to get the userRoles from PortalApp to Portlet.
Env: JDEV 11.1.1.5 , Integrated WLS
Note: I haven't done any configuration related to WS-Security between Portal App and Portlet App,_ since both are deployed to the same integrated Server.
-Reju

If you haven't already you have to perform user category mapping between the portal roles to portlet roles.
This can be achieved using WLST scripts.
Thanks.
Micah C.

JSF Portlet doesn't render after EventHandler

I'm trying to set up basic event IPC between 2 JSF portlets in WLP 10.3.2.
Portlet A has a JSP with an inputText and and a commandLink:
<h:inputText value="#{aBean.inputValue}"/>
<h:commandLink action="#{aBean.clickMe}" value="Click Me">
</h:commandLink>Backing action creates the event:
public String clickMe() {
    FacesContext fc = FacesContext.getCurrentInstance();
    ExternalContext ec = fc.getExternalContext();
    ActionRequest ar = (ActionRequest)ec.getRequest();
    HttpServletRequest request =
        (HttpServletRequest) ar.getAttribute("javax.servlet.request");
    PortletBackingContext pbc =
        PortletBackingContext.getPortletBackingContext(request);
    pbc.fireCustomEvent("clickMe", inputValue);
    return "";
}Portlet B is configured with Init-Param:
javax.portlet.faces.bridgeEventHander=com.example.event.EventHandlerand Java Processing Event for {urn:com:oracle:wlp:netuix:event:custom}clickMe
EventHandler has:
public EventNavigationResult handleEvent(FacesContext context, Event event) {
    String elExpression = "#{bBean}";
    ELContext elContext = context.getELContext();
    ValueExpression valueExpression = context.getApplication().getExpressionFactory().createValueExpression(
        elContext, elExpression, BBean.class);
    BBean bBean = (BBean)valueExpression.getValue(elContext);
    bBean.setDisplayValue((String) event.getValue());
    return null;//new EventNavigationResult(null, "clickMe");
}It doesn't seem to matter whether or not I return an EventNavigationResult.
If I have both portlets displayed on the same portal page, portlet B is not rendered after the event processing. Only the portlet header displays.
As a workaround, I found that if I set a WLP-Handled Event to Handle Custom Event and Change Window State to normal, the portlet renders correctly. However, this workaround does not work if the portlets are on different portal pages as my usecase requires.
Am I missing something or what do I need to do to get the receiving portlet to render? Anyone have a basic JSF event IPC example working?

I'm trying to set up basic event IPC between 2 JSF portlets in WLP 10.3.2.
Portlet A has a JSP with an inputText and and a commandLink:
<h:inputText value="#{aBean.inputValue}"/>
<h:commandLink action="#{aBean.clickMe}" value="Click Me">
</h:commandLink>Backing action creates the event:
public String clickMe() {
    FacesContext fc = FacesContext.getCurrentInstance();
    ExternalContext ec = fc.getExternalContext();
    ActionRequest ar = (ActionRequest)ec.getRequest();
    HttpServletRequest request =
        (HttpServletRequest) ar.getAttribute("javax.servlet.request");
    PortletBackingContext pbc =
        PortletBackingContext.getPortletBackingContext(request);
    pbc.fireCustomEvent("clickMe", inputValue);
    return "";
}Portlet B is configured with Init-Param:
javax.portlet.faces.bridgeEventHander=com.example.event.EventHandlerand Java Processing Event for {urn:com:oracle:wlp:netuix:event:custom}clickMe
EventHandler has:
public EventNavigationResult handleEvent(FacesContext context, Event event) {
    String elExpression = "#{bBean}";
    ELContext elContext = context.getELContext();
    ValueExpression valueExpression = context.getApplication().getExpressionFactory().createValueExpression(
        elContext, elExpression, BBean.class);
    BBean bBean = (BBean)valueExpression.getValue(elContext);
    bBean.setDisplayValue((String) event.getValue());
    return null;//new EventNavigationResult(null, "clickMe");
}It doesn't seem to matter whether or not I return an EventNavigationResult.
If I have both portlets displayed on the same portal page, portlet B is not rendered after the event processing. Only the portlet header displays.
As a workaround, I found that if I set a WLP-Handled Event to Handle Custom Event and Change Window State to normal, the portlet renders correctly. However, this workaround does not work if the portlets are on different portal pages as my usecase requires.
Am I missing something or what do I need to do to get the receiving portlet to render? Anyone have a basic JSF event IPC example working?

Query- IPC using JSF Portlets in WebLogic Portal

The question is how to pass data when doing InterPortlet Communication using Local JSF portlets in Weblogic Portal.
I will eloborate on the particular scenario we have below.
Two JSF portlets are build (both are not using Java Page Flows). The first porltet has a table of data. When the user clicks on one of the items in the table (which is coded using <h:commandLink/> option), the second portlet should show some details on the item clicked.
For example:
If there is a list of books in first portlet, when clicking on one of the book name, the details of book should come up in the second portlet.
To achieve this, faces event was enabled in first portlet with requestAttrPersistence option set to session.
For example :
<netuix:content>
<netuix:facesContent contentUri="/bookList.faces" requestAttrPersistence="session">
<netuix:facesEvents>
<netuix:facesEvent action="/bookDetails.faces" eventName="bookDetailEvent"/>
</netuix:facesEvents>
</netuix:facesContent>
</netuix:content>
The second portlet was configured to handle faces events, particularly the bookDetailEvent.
Example:
<netuix:handleFacesEvent eventLabel="handleFacesEvent1" eventName="bookDetailEvent" fromSelfInstanceOnly="false" onlyIfDisplayed="true" sourceDefinitionLabels="JSFPortlet_1" sourceDefinitionWildcard="this">
<netuix:invokeFacesAction action="/bookDetails.faces"/>
</netuix:handleFacesEvent>
Going by this method, how can we find the particular book whose detail has to be shown? As in JSF, we dont directly access the request attributes, what is the ideal way to pass data from one page to other?
Please help on this.

i am also having the same problem.I tried by passing _nfls=false but it didn't work.Can you suuggest where do i need to set this or any other parametrs such as this programmatically?

JSF portlet: namingContainer - duplicate id error

Similar Messages

Maybe you are looking for