WSRP/JSR-168 for production?

Maybe I'm missing something, but from my little research on the use of WSRP/JSR-168 within Portal, all indications are this is not ready for production use. Meaning, if I use JDeveloper (or some other tool) I cannot deploy production quality Portlets based on these standards within Portal 10g (9.0.4). Is this correct, or did I miss something?
Given this, my only choice is to use the JPDK if I wish to develop Java based portlets.
Thanks...
Dean

Hi all,
Even i am also looking for if any body has consumed the JSR168 portlet on
OracleAs Portal 10g Release 2.
I have found some article where it is mentioned that
Production Support for JSR 168 and WSRP
Once upgraded to Oracle Portal 10.1.4, a repository only upgrade on top of OracleAS 10.1.2.0.2, your portal version provides production support for building and consuming standards-based portlets. Oracle portal provides a Java Portlet Wizard within Oracle JDeveloper to build JSR 168 portlets and publish those portlet to Oracle's container or any portlet standards container. You can then consume JSR 168 portlet with Oracle Portal through WSRP. Oracle Portal also supports consuming any portlet through WSRP as well as JPDK portlets.
U can read the complete details here:-
http://www.oracle.com/technology/products/ias/portal/html/pdk_1014_new_features.html
Thnx
~Neeraj Sidhaye
[email protected]
[email protected]

Similar Messages

  • WSRP & JSR-168

    Hello!
    I'm trying to declare my portlets as remote and connect to them.
    I have JSR-168 compliant portlets and I created remote portlets to them on a consumer.
    But every time I submit a form the portal reverts to the initual state instead of processing my request.
    I was also wondering if WebLogic processes only URLs created using the netui library?
    thank in advance,
    Vica

    Hi all,
    Even i am also looking for if any body has consumed the JSR168 portlet on
    OracleAs Portal 10g Release 2.
    I have found some article where it is mentioned that
    Production Support for JSR 168 and WSRP
    Once upgraded to Oracle Portal 10.1.4, a repository only upgrade on top of OracleAS 10.1.2.0.2, your portal version provides production support for building and consuming standards-based portlets. Oracle portal provides a Java Portlet Wizard within Oracle JDeveloper to build JSR 168 portlets and publish those portlet to Oracle's container or any portlet standards container. You can then consume JSR 168 portlet with Oracle Portal through WSRP. Oracle Portal also supports consuming any portlet through WSRP as well as JPDK portlets.
    U can read the complete details here:-
    http://www.oracle.com/technology/products/ias/portal/html/pdk_1014_new_features.html
    Thnx
    ~Neeraj Sidhaye
    [email protected]
    [email protected]

  • WSRP (jsr-168) portlets no edit/help buttons appear

    Hi,
    I have some jsr-168 portlets that I wrote that work on other portal software (like uPortal). They have both help and edit buttons (specified in the portlet.xml and handlers written into the portlet code) and you can click them and see both the help and edit modes of the portlets. However, when I put these portlets on Oracle Portal (10.1.2/10.1.4), the edit/help (or personalize) buttons don't show up. I even tried to use the sample portlets from sun, like the BookmarkPortlet, etc, and they have the same problem.
    Any ideas?
    Thanks,
    -Mike M.

    Hi,
    I dont see anything obvisouly wrong with what you are doing. I suspect the var attribute though. Can you try out this sample
    ">view</a><br>
    <a href="
    <portlet:renderURL windowState="maximized" portletMode="help"/>">help</a><br>
    Thanks,
    Sharmila

  • JSR 168 / WSRP support in EP

    Hi All,
    As I am getting no clear reply, I would like to ask the SDN-ers for help regarding the JSR 168 and WSRP support by the Portal.
    Can anyone tell me whether any of the above standards is supported by the NW'04 or NW'04s - and if not (i guess this is the case for JSR 168) - for which NW release it is planned ?
    I will appreciate your quick reply
    Regards
    Maciek

    Yeah, but I was hoping for some more up-to-date news... This one is dated august'05. I have a presentation saying that BOTH WSRP and JSR168 will be available as of 04's ("Project Paris").
    We do have the WSRP - but it seems that in the meantime the JSR is gone...

  • Portlet API:  JSR 168 / 286  vs Vendor Extensions

    Currently evaluating Websphere 5.1 vs WebLogic 8.1 Portal software.
    It seems like both IBM and BEA push you towards using their Portal extensions as "value add" features. I am really interested in sticking to JSR 168 for portability.
    Does anyone have any experience with these tools developing JSR 168? I would appreciate your observations about using the vendor extensions vs JSR 168 support in these tools. Please add any comments on other portal software you have had success with.
    Any idea when will JSR 286 come out with final spec?
    Message was edited by:
    java@finance

    sorry.Correction.I am using Oracle portal 10.1.4 .
    -Vid-

  • Oracle Portal WSRP messing things up for Tapestry JSR-168 portlet?

    I've been trying to consume a Tapestry JSR-168 portlet in Oracle Portal 10.1.4. However a very simple tapestry page is (already) failing. This page displays some boilerplate text and a form component including one text input item. Upon display the following stacktrace is shown:
    06/03/03 14:42:58 webmodule: [id=3230371113264,1] EXCEPTION THROWN: Uncaught exception
    org.apache.hivemind.ApplicationRuntimeException: Invalid URL "wsrp_rewrite?wsrp-urlType=blockingAction&wsrp-mode=wsrp%3Aview&wsrp-windowState=wsrp%3Anormal&wsrp-secureURL=false/wsrp_rewrite" [context:/WEB-INF/Home.page, line 5, column 59]
         at org.apache.tapestry.engine.RequestCycle.renderPage(RequestCycle.java:380)
         at org.apache.tapestry.portlet.PortletRendererImpl.renderPage(PortletRendererImpl.java:70)
         at $PortletRenderer_109c058b59f.renderPage($PortletRenderer_109c058b59f.java)
         at $PortletRenderer_109c058b59e.renderPage($PortletRenderer_109c058b59e.java)
         at org.apache.tapestry.portlet.PortletHomeService.service(PortletHomeService.java:80)
         at $IEngineService_109c058b58a.service($IEngineService_109c058b58a.java)
         at org.apache.tapestry.services.impl.EngineServiceInnerProxy.service(EngineServiceInnerProxy.java:77)
         at org.apache.tapestry.services.impl.EngineServiceOuterProxy.service(EngineServiceOuterProxy.java:66)
         at org.apache.tapestry.engine.AbstractEngine.service(AbstractEngine.java:248)
         at org.apache.tapestry.services.impl.InvokeEngineTerminator.service(InvokeEngineTerminator.java:60)
         at $WebRequestServicer_109c058b559.service($WebRequestServicer_109c058b559.java)
         at $WebRequestServicer_109c058b558.service($WebRequestServicer_109c058b558.java)
         at $WebRequestServicer_109c058b557.service($WebRequestServicer_109c058b557.java)
         at $WebRequestServicer_109c058b556.service($WebRequestServicer_109c058b556.java)
         at org.apache.tapestry.portlet.RenderRequestServicerToWebRequestServicerBridge.service(RenderRequestServicerToWebRequestServicerBridge.java:49)
         at $RenderRequestServicer_109c058b551.service($RenderRequestServicer_109c058b551.java)
         at $RenderRequestServicer_109c058b550.service($RenderRequestServicer_109c058b550.java)
         at $RenderRequestServicer_109c058b54b.service($RenderRequestServicer_109c058b54b.java)
         at $RenderRequestServicer_109c058b54a.service($RenderRequestServicer_109c058b54a.java)
         at org.apache.tapestry.portlet.ApplicationPortlet.render(ApplicationPortlet.java:161)
         at oracle.webdb.wsrp.server.Server.getMarkup(Unknown Source)
         at oracle.webdb.wsrp.WSRP_v1_Markup_PortType_Tie.invoke_getMarkup(WSRP_v1_Markup_PortType_Tie.java:98)
         at oracle.webdb.wsrp.WSRP_v1_Markup_PortType_Tie.processingHook(WSRP_v1_Markup_PortType_Tie.java:495)
         at com.sun.xml.rpc.server.StreamingHandler.handle(StreamingHandler.java:230)
         at com.sun.xml.rpc.server.http.ea.JAXRPCServletDelegate.doPost(JAXRPCServletDelegate.java:153)
         at com.sun.xml.rpc.server.http.JAXRPCServlet.doPost(JAXRPCServlet.java:69)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
         at oracle.webdb.wsrp.server.ContextFilter.doFilter(Unknown Source)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: oracle.webdb.wsrp.server.ContainerIllegalArgumentException: Invalid URL "wsrp_rewrite?wsrp-urlType=blockingAction&wsrp-mode=wsrp%3Aview&wsrp-windowState=wsrp%3Anormal&wsrp-secureURL=false/wsrp_rewrite"
         at oracle.webdb.wsrp.server.PortletResponseImpl.encodeURL(Unknown Source)
         at oracle.webdb.wsrp.server.RenderResponseImpl.encodeURL(Unknown Source)
         at org.apache.tapestry.portlet.PortletWebResponse.encodeURL(PortletWebResponse.java:60)
         at $WebResponse_109c058b636.encodeURL($WebResponse_109c058b636.java)
         at $WebResponse_109c058b51e.encodeURL($WebResponse_109c058b51e.java)
         at org.apache.tapestry.engine.RequestCycle.encodeURL(RequestCycle.java:207)
         at $IRequestCycle_109c058b63f.encodeURL($IRequestCycle_109c058b63f.java)
         at $IRequestCycle_109c058b53a.encodeURL($IRequestCycle_109c058b53a.java)
         at org.apache.tapestry.portlet.PortletLink.getURL(PortletLink.java:68)
         at org.apache.tapestry.portlet.PortletLink.getURL(PortletLink.java:126)
         at org.apache.tapestry.form.FormSupportImpl.render(FormSupportImpl.java:490)
         at org.apache.tapestry.form.Form.renderComponent(Form.java:250)
         at org.apache.tapestry.AbstractComponent.render(AbstractComponent.java:617)
         at org.apache.tapestry.BaseComponent.renderComponent(BaseComponent.java:92)
         at org.apache.tapestry.AbstractComponent.render(AbstractComponent.java:617)
         at org.apache.tapestry.AbstractPage.renderPage(AbstractPage.java:275)
         at org.apache.tapestry.engine.RequestCycle.renderPage(RequestCycle.java:366)
         ... 36 more
    06/03/03 14:42:58 webmodule: [id=3230371113264,1] WARNING: Unable to process client request: Invalid URL "wsrp_rewrite?wsrp-urlType=blockingAction&wsrp-mode=wsrp%3Aview&wsrp-windowState=wsrp%3Anormal&wsrp-secureURL=false/wsrp_rewrite"
    org.apache.hivemind.ApplicationRuntimeException: Invalid URL "wsrp_rewrite?wsrp-urlType=blockingAction&wsrp-mode=wsrp%3Aview&wsrp-windowState=wsrp%3Anormal&wsrp-secureURL=false/wsrp_rewrite" [context:/WEB-INF/Home.page, line 5, column 59]
         at org.apache.tapestry.engine.RequestCycle.renderPage(RequestCycle.java:380)
         at org.apache.tapestry.portlet.PortletRendererImpl.renderPage(PortletRendererImpl.java:70)
         at $PortletRenderer_109c058b59f.renderPage($PortletRenderer_109c058b59f.java)
         at $PortletRenderer_109c058b59e.renderPage($PortletRenderer_109c058b59e.java)
         at org.apache.tapestry.portlet.PortletHomeService.service(PortletHomeService.java:80)
         at $IEngineService_109c058b58a.service($IEngineService_109c058b58a.java)
         at org.apache.tapestry.services.impl.EngineServiceInnerProxy.service(EngineServiceInnerProxy.java:77)
         at org.apache.tapestry.services.impl.EngineServiceOuterProxy.service(EngineServiceOuterProxy.java:66)
         at org.apache.tapestry.engine.AbstractEngine.service(AbstractEngine.java:248)
         at org.apache.tapestry.services.impl.InvokeEngineTerminator.service(InvokeEngineTerminator.java:60)
         at $WebRequestServicer_109c058b559.service($WebRequestServicer_109c058b559.java)
         at $WebRequestServicer_109c058b558.service($WebRequestServicer_109c058b558.java)
         at $WebRequestServicer_109c058b557.service($WebRequestServicer_109c058b557.java)
         at $WebRequestServicer_109c058b556.service($WebRequestServicer_109c058b556.java)
         at org.apache.tapestry.portlet.RenderRequestServicerToWebRequestServicerBridge.service(RenderRequestServicerToWebRequestServicerBridge.java:49)
         at $RenderRequestServicer_109c058b551.service($RenderRequestServicer_109c058b551.java)
         at $RenderRequestServicer_109c058b550.service($RenderRequestServicer_109c058b550.java)
         at $RenderRequestServicer_109c058b54b.service($RenderRequestServicer_109c058b54b.java)
         at $RenderRequestServicer_109c058b54a.service($RenderRequestServicer_109c058b54a.java)
         at org.apache.tapestry.portlet.ApplicationPortlet.render(ApplicationPortlet.java:161)
         at oracle.webdb.wsrp.server.Server.getMarkup(Unknown Source)
         at oracle.webdb.wsrp.WSRP_v1_Markup_PortType_Tie.invoke_getMarkup(WSRP_v1_Markup_PortType_Tie.java:98)
         at oracle.webdb.wsrp.WSRP_v1_Markup_PortType_Tie.processingHook(WSRP_v1_Markup_PortType_Tie.java:495)
         at com.sun.xml.rpc.server.StreamingHandler.handle(StreamingHandler.java:230)
         at com.sun.xml.rpc.server.http.ea.JAXRPCServletDelegate.doPost(JAXRPCServletDelegate.java:153)
         at com.sun.xml.rpc.server.http.JAXRPCServlet.doPost(JAXRPCServlet.java:69)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
         at oracle.webdb.wsrp.server.ContextFilter.doFilter(Unknown Source)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
         at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: oracle.webdb.wsrp.server.ContainerIllegalArgumentException: Invalid URL "wsrp_rewrite?wsrp-urlType=blockingAction&wsrp-mode=wsrp%3Aview&wsrp-windowState=wsrp%3Anormal&wsrp-secureURL=false/wsrp_rewrite"
         at oracle.webdb.wsrp.server.PortletResponseImpl.encodeURL(Unknown Source)
         at oracle.webdb.wsrp.server.RenderResponseImpl.encodeURL(Unknown Source)
         at org.apache.tapestry.portlet.PortletWebResponse.encodeURL(PortletWebResponse.java:60)
         at $WebResponse_109c058b636.encodeURL($WebResponse_109c058b636.java)
         at $WebResponse_109c058b51e.encodeURL($WebResponse_109c058b51e.java)
         at org.apache.tapestry.engine.RequestCycle.encodeURL(RequestCycle.java:207)
         at $IRequestCycle_109c058b63f.encodeURL($IRequestCycle_109c058b63f.java)
         at $IRequestCycle_109c058b53a.encodeURL($IRequestCycle_109c058b53a.java)
         at org.apache.tapestry.portlet.PortletLink.getURL(PortletLink.java:68)
         at org.apache.tapestry.portlet.PortletLink.getURL(PortletLink.java:126)
         at org.apache.tapestry.form.FormSupportImpl.render(FormSupportImpl.java:490)
         at org.apache.tapestry.form.Form.renderComponent(Form.java:250)
         at org.apache.tapestry.AbstractComponent.render(AbstractComponent.java:617)
         at org.apache.tapestry.BaseComponent.renderComponent(BaseComponent.java:92)
         at org.apache.tapestry.AbstractComponent.render(AbstractComponent.java:617)
         at org.apache.tapestry.AbstractPage.renderPage(AbstractPage.java:275)
         at org.apache.tapestry.engine.RequestCycle.renderPage(RequestCycle.java:366)
         ... 36 moreAny of you got any clue whether this is an issue of Tapestry, or of Oracle Portal. I'm guessing it is Oracle Portal messing things up, as it is Oracle which gets mentioned in the stacktrace as cause.
    Thanks.

    My mistake! The error was a result of a badly formatted portal.xml

  • Support for JSR 168 and WSRP

    Hi,
    does SAP EP 7.0 supports JSR 168 and WSRP standards?
    Regards,
    Ladislav

    Hi Ladislav,
    Here are a few pointers that might answer your question:
    - WSRP 1.0 is supported in NetWeaver 7.0 (see this [SAP Help Page|http://help.sap.com/saphelp_nw70/helpdata/en/43/23fb36cad10d23e10000000a1553f7/frameset.htm] for more information)
    - JSR 168 support for Netweaver 7.0 has been discussed often but never confirmed in SAP documentation (check this thread for a recent SAP unofficial comment about its upcoming availability). However, NetWeaver CE 7.1 already supports JSR 168 (see this [SAP Help Page|http://help.sap.com/saphelp_nwce10/helpdata/en/44/5b96b37b6f4de1e10000000a1553f7/frameset.htm])
    Hope this helps.
    Best Regards,
    Joseph

  • Apache Struts Bridge for JSR-168 Portlet

    Hello,
    I am trying to call a struts application from a JSR-168 Portlet.
    But I am not getting this class "oracle.webdb.wsrp.server.PortletApplicationImpl"
    Which is required for this.
    Can anyone, tell me, where to find this class.
    Thanks
    Sam
    Message was edited by:
    samplified

    I was able to find that class by downloading the Oracle Portlet Container 10.1.2.0.2 and following the instructions for extracting it into my OC4J. When you do that it will give you a file called ${OC4J_HOME}/shared-lib/oracle.wsrp/1.0/wsrp-container.jar. That jar file contains the class you need.
    Oracle Portlet Container 10.1.2.0.2: http://download.oracle.com/otndocs/tech/ias/portal/files/portlet-container.zip
    PDK Page: http://www.oracle.com/technology/products/ias/portal/pdk.html

  • JSR 168 support on production environment??

    Hello Oracle people,
    when are you going to support JSR168 portlets in you Oracle Portal?? Where is the money customers pay you for working? not enough? What do we do with this piece of closed source box you gave us if you can not be ahead many other open source (free) products? Can you stand the pace? you say "we support standards"... and I see you are falling behind.

    you should be demanded because of the way you assure support of the JSR168 in your executive brochures... Any layer out there who can help?
    Look this question and how Oracle answers:
    Does Oracle Portal support JSR 168 and WSRP?
    Oracle has been an active member of the standards bodies and been instrumental in the process of defining these portal interoperability standards:
    * JSR-168: Defines how Java developers should write portlets using standard APIs.
    * OASIS WSRP (Web Services for Remote Portlets): Defines the communication protocol between a portal application and the remote portlet./li>
    Oracle fully supports the JSR 168 portlet specification. You can develop JSR 168 portlets using the Java Portlet Wizard, a JDeveloper plug-in. You can also deploy JSR 168 portlets to Oracle's or any other vendor's JSR 168 Java Portlet Container. Portlets deployed to Oracle's container are exposed to portals through WSRP, and can be registered against any portal vendor's WSRP compliant portal. The current version of Oracle Portal (Oracle Portal 10g Release 2 (10.1.2)) does not support WSRP, but you can register and test standard portlets using the OracleAS Portal Developer's Preview for Portlet Standards or the hosted WSRP compliant portal on http://portalstandards.oracle.com. You find additional information about Oracle and Portal standards on http://portalstandards.oracle.com.
    When there is a simple answer: NO we do not support the JSR168 in Oracle Portal. We do a lot of other things... see this and that. But sadly our Oracle Portal does not support it, you can test a preview version but if it crashes its your problem (we proudly do very expensive closed source :).

  • Remote Inter Portlet Communication for JSR 168

    Hi All,
    We are stuck in a big problem using JSR 168 as remote portlets. We will be relieved if someone can suggest few ideas on this. I will provide the scenario which we are trying now.
    We have two portlets namely portlet A and portlet B which are Java(JSR 168) type portlets. These two portlets are offered as remote and they reside in the producer application. We have consumed these two portlets in our consumer application.
    The portlet A is triggering an event and portlet B is listening to the event triggered by portlet A. Currently we are trying to implement this functionality using Ajax. We tried to use customEventUrl tag in our jsp belonging to portlet A and we finally figured out that customEventUrl will not work in Remote portlets. We are not sure as how to pass the information from remote portlet A to remote portlet B. Please let us know your thoughts about this as whether the implementation is really possible when using Remote portlets.
    IMPORTANT NOTE: The event handling and the configuration code that we have made in the above scenario is working perfectly for non-remote java portlets. The problem is occurring only when we consume them in the consumer application.
    Thanks
    Vijay

    Hello Ashwin,
    What version of WebLogic Portal are you using? And is this the same for both the consumer and producer?
    If you are using WLP 10.3.2 I would highly recommend using JSR286 portlets (the next version of the Java Portlet (JSR168) specification) and the JSR286-standard eventing. The JSR286 eventing model is actually much cleaner and easier to understand than the WLP-proprietary support for events in JSR168 portlets.
    However, if you are using a version of WLP prior to 10.3.2 and can't upgrade, JSR168-style events are your only choice. I can give you examples, but they all look very similar to the examples in the online documentation.
    When events work between portlets locally, but not over WSRP, the usual problems are:
    - There is one or more of "onlyIfDisplayed", "sourceDefinitionLabels" or "sourceInstanceLabels" attributes declared on the handle*Event element in the .portlet file. These attributes restrict when the portlet should receive an event, and they usually don't work the way you think when running over WSRP. It is best to not use these attributes for portlets which are going to be used over WSRP.
    - A payload is being sent with the event which is not actually serializable. If serialization of the event payload (which is required for versions of WLP prior to 10.3.2 for WSRP) fails, the event will not be delivered to the portlet.
    - The producer may be configured to not accept events. Check your producer's WEB-INF/wsrp-producer-config.xml file; the "service-config" element should either not have an "offer-extensions" attribute, or this attribute's value should be "true".
    - The events may be getting sent during a portlet lifecycle other than processAction or handleEvent. There is no way for WSRP to handle events which have been sent during preRender or render, so it simply doesn't work.
    - In the case of JSR168 portlets, if you have a backing file on the portlet (in addition to the portlet implementation as well), that may not work in some circumstances over WSRP. It is best to have the event handlers be in the portlet implementation class and avoid the use of backing files for JSR168 portlets.
    If none of those things help you, my suggestion would be to post a sample .portlet file for one of the portlets that is supposed to be receiving the event, as well as the method signature in that portlet's implementation class that is supposed to be receiving the event, and the code which is sending the event that is supposed to be received.
    Kevin

  • USING APACHE STURUTS BRIDGE WITH ORACLE PORTAL FOR STRUTS - JSR 168 PORTLET

    I am trying to develop a JSR - 168 compliant portlet which uses struts framework.I am using APACHE STRUTS BRIDGE to run the application in my ORACLE 10.1.4 Portal server.While doing the configuration accoring to the documentation given in URL http://www.ja-sig.org/wiki/display/PLT/Struts+Bridge
    (apache struts bridge), i was asked to add an <init-param> entery in the portlet.xml file to get the ServletContext.So i need to know where is the ServletContextProvider implementation class which implements ServletContextProvider available in Oracle AS so that i can use that to get the ServletContext and use it furthur.
    Thanks
    Deepak

    you could write your own implementation class for the ServletContextProvider interface and fill in the portlet.xml with the class you class
    It could be written as follows:
    package Edmunds.com.portal.bridges;
    import javax.portlet.GenericPortlet;
    import javax.portlet.PortletRequest;
    import javax.portlet.PortletResponse;
    import javax.servlet.ServletContext;
    import javax.servlet.http.HttpServletRequest;
    import javax.servlet.http.HttpServletRequestWrapper;
    import javax.servlet.http.HttpServletResponse;
    import javax.servlet.http.HttpServletResponseWrapper;
    /* note that PortletApplicationImpl is oracle version of portletContextImpl */
    import oracle.webdb.wsrp.server.PortletApplicationImpl;
    import org.apache.portals.bridges.common.ServletContextProvider;
    * PortalServletContextProvider supplies access to the Servlet context of Oralce Portal Portlet.
    public class PortalServletContextProvider implements ServletContextProvider {
    public ServletContext getServletContext(GenericPortlet portlet)
    return ((PortletApplicationImpl) portlet.getPortletContext()).getServletContext();
    public HttpServletRequest getHttpServletRequest(GenericPortlet portlet, PortletRequest request)
    return (HttpServletRequest) ((HttpServletRequestWrapper) request).getRequest();
    public HttpServletResponse getHttpServletResponse(GenericPortlet portlet, PortletResponse response) {
    return (HttpServletResponse) ((HttpServletResponseWrapper) response).getResponse();
    }

  • JSR-168/WSRP iViews

    Hi,
    I have the following doubts to be cleared.It would be of great help if someone knows abt these and revert back ASAP.
    1) How many iViews currently exist? Is there a directory of available iViews?
    2) Is SAP planning to provide today's iView functionality as JSR-168/WSRP portlets together with the new release (or later)?
    3) Would it make sense to create JSR-168/WSRP portlets by reusing existing iViews? I.e. is the iView Java code customizable? Would that be a feasible approach in order to provide iView-like functionality through JSR-168 or WSRP portlets?
    4)Any other alternatives to expose iView-like functionality through a non-SAP portal? If so, what would that look like?
    Regards.....

    Hi Christian,
    1) This question is independent of WSRP/JSR, right? --> So, you mean, how many iViews in general.. There is no list published by SAP giving an overview of available iViews. However, you could get a little overview when checking out the business packages currently available offered by SAP and partners.
    https://www.sdn.sap.com/sdn/contentportfolio.sdn
    2) SAP is not planning to provide all the functionality in a JSR168/WSRP-compliant manner. SAP will support WSRP by the end of this year with the next NetWeaver release. However, this does not mean that the existing content will be available via WSRP. Some might be, but to which extent, cannot be said for sure now. JSR is intended to be supported next year, meaning that the NetWeaver Portal will be able to consume JSR168-compliant portlets, but not provide all the existing content in JSR168 format.
    3) You are not allowed to modify iViews delivered by SAP. If you intend to modify iViews, which you created on your own, it depends on how much effort you want to spend on it and how long you can wait with your projects since both standards are not supported at the moment yet with the current SP releases.
    4) Please a bit more specific about what you mean with iView-like functionality. In general, to leverage the full functionality of SAP iViews you always need the full NetWeaver Portal framework. There are some scenarios of how to integrate the SAP EP into the WebSphere Portal. Check out the docs here on SDN.
    Kind regards,
    Thomas

  • Is the JSR-168 portlet-container supported for 10.1.3?

    And if so, what are the actions to be taken to install it on OC4J 10.1.3 standalone? I tried to install it earlier but ran into problems, see: WSRP Provider registration fails for OC4J10.1.3 container (stack), why?
    I want to use OC4J 10.1.3 as my JSR-168 container, because I can (try and) deploy Tapestry 4.0 portlets in this application server, that use Java annotations. I then want to consume these portlets over WSRP - part of Portal 10.1.4

    <bump count="2"/>

  • What is the difference between JSR 168 portlets and WSRP portlets?

    What is the difference between JSR 168 portlets and WSRP portlets?

    Here is the difference between JSR168 and WSRP:
    The WSRP specification does not make any statements as to implemention. Java's portlet specification, JSR 168, and WSRP are not competing technologies. JSR 168 may be used to define a portlet, and WSRP may be used to define a portlet's operations to remote containers. JSR 168 portlets and WSRP may be used together to define a portlet and to provide remote operations. Similarly, .NET portlets may be created for use with WSRP. Interoperability between JSR 168 and .NET WSRP implementations has been demonstrated

  • WSRP and JSR 168 Docs

    Can anyone tell me where to find some good documentation (especially tutorials) for WSRP and JSR 168?
    Thanks

    This is a good document for WSRP understanding.
    http://xml.coverpages.org/WSRP-Primerv0920040830a.pdf

Maybe you are looking for

  • Cannot install CRS on AIX 5.3 ML09 with HACMP 5.4.1

    We have a two-node HACMP cluster, it's handling the networking and storage. (raw LV's) It's a fairly simple setup. I followed the instructions in document 404474.1 "Status of Certification of Oracle Clusterware with HACMP 5.3 & 5.4" to ensure it's co

  • Iphoto 2.0 blackout

    iphoto 2.0 does not work, screen goes black and locks, not a memory fault I have 22.3 Gb on ipad4 with IOS7.0.4.  The previous version of iPhoto worked OK.

  • O som fica mudo no meio da conversa

    o som fica mudo no meio da conversa o defeito apareceu algumas vezes já, estou usandoo o OX 10.8.2 e o facetime 2.0 (1080), alguem sabe como resolver isso, obrigado

  • How to give the list.tablename in from clause

    Hi, I am getting error invalid table name when I give list_item.tablename in from clause ex : q1:= 'select * from &p1_list.tablename'; return q1; here p1_list is the list of schema values. It worked fine when I give the type SQL Query. If I give the

  • Printing delivery notes upon picking confirmation

    We wish to only print delivery notes once picking is confirmed and goods ready to go.  We can achieve this in VL02n via amendment to routine 35 in V/27 however generation of output does not appear to apply when picking is confirmed via transaction VL