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

Similar Messages

  • WSRP or JSR-168 Portlets with PDK-Java

    Is it possible to create WSRP or JSR-168 compliant portlets with PDK-Java or Bi beans?
    Thanks,

    When PDK-Java was designed 4-5 years ago, there was no portlet standard on the horizon. While from an architecture point of view PDK-Java is very similar to WSRP, it uses a proprietary protocol. Therefore you can't expose PDK-Java portlets through WSRP.
    You can, however, leverage the BI-beans in JSR 168 portlets, just like in any other Java environment.
    Peter

  • Spring and JSR 168 Portlet

    I have an application which uses Spring beans and JSR 168 based portlet. I want to know how can i get access to the my spring beans in the portlet controller. I am trying to do the following
    public WebApplicationContext getSpringContext(PortletRequest request) {
    HttpServletRequest servletRequest = (HttpServletRequest)request.getAttribute("javax.servlet.request");
    WebApplicationContext appContext = WebApplicationContextUtils.getWebApplicationContext(servletRequest
                        .getSession().getServletContext());
    return appContext;
    Actually a NPE happens @ "servletRequest.getSession()"
    The spring beans are initialized during deployment using the spring contextListener
    This code works in other J2EE container which have JSR 168 support, like BEA, JBOSS
    Any help is greatly appreciated.

    OMG!
    Today, I wanted to build a really simple portlet with spring, and deploy it on oc4j / iAS10gR2 - since it hoped it will ease development in the future.
    Your post, doesn't motivate so much - but let's hope I've a bit more luck getting it running :)
    -> Have you looked at the spring-framework 2.0.3 release demos? In the 2.0.3 release a new demo: petportal is included - maybe this helps :)

  • URL generation - Https and JSR 168

    We have some JSR 168 complaint portlets that are working fine under http. However,
    when we switch to https (with a webserver front-end), the edit button functionality
    generates incorrect urls. It tries to use http and then append port 443. These
    urls do not work with the web server front-end.
    I know all urls for JPF portlets etc are controlled through the url-template-config.xml
    file, but it seems that the JSR 168 portlets do not use this file. Any idea what
    these portlets use and what configuration change I could make to resolve this
    issue?
    Thanks
    Kunal

    Hi Subbu -
    I have modified the template to use relative paths - maybe that will solve my
    issue. Here is my modified template.
    Thanks
    Kunal
    Subbu Allamaraju <[email protected]> wrote:
    Hi Kunal,
    In WLP, all portlets rely on url-templates-config.xml to create URLs.
    The edit button is independent of the type of the portlet you are using.
    For Java portlets, could you make sure you have the following snippet
    in
    this file:
    <java-portlet-url-templates>
    <url-template-ref type="action" name="portlet-default"/>
    <url-template-ref type="secure-action" name="portlet-default"/>
    <url-template-ref type="resource" name="portlet-default"/>
    <url-template-ref type="secure-resource" name="portlet-default"/>
    </java-portlet-url-templates>
    </url-template-config>
    where the name of the template should be mapped to one of the templates
    defined in this file.
    If you still face issues with this, please post the templates specified
    in this file so that I can take a look. Also, let me know if you are
    using GA or SP2.
    Subbu
    Kunal Mittal wrote:
    We have some JSR 168 complaint portlets that are working fine underhttp. However,
    when we switch to https (with a webserver front-end), the edit buttonfunctionality
    generates incorrect urls. It tries to use http and then append port443. These
    urls do not work with the web server front-end.
    I know all urls for JPF portlets etc are controlled through the url-template-config.xml
    file, but it seems that the JSR 168 portlets do not use this file.Any idea what
    these portlets use and what configuration change I could make to resolvethis
    issue?
    Thanks
    Kunal
    [url-template-config.xml]

  • JSR 168 Container

    Is the JSR 168 container available for download?

    We have Application Server 10g installed. We also have applied patchset 9.0.4.1
    We have tried to install WSRP and JSR 168 containers following steps detailed in OracleAS Portal Developer's Preview for Portlet Standards install guide.
    We tried to install repository database on the 9.2.0.4 database (not the Metadata Repostiory Database as noted in install guide) we got error that OWA_VPD_CTX procedure is missing.
    We continued installation ignoring this error and after we created DAD (described in the 'Wiring the Portal Repository to the Portal Middle Tier and Infrastructure' section of install guide) we could not successfully execute ptlasst.sh script. This is the error in the log file:
    Error in getting the Portal version INSTALL_ERROR : Could not obtain Portal version : null
    OPCA_ERROR : Portal installation throws exception :null
    I guess because of this we cannot start DAD and later cannot register WSRP provide...

  • 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

  • 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

  • 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

  • JSR-168 and Request Parameters

    Hi!
    I'm creating a portlet application; right now it only has one portlet in it. The landing page for my portlet (view mode) has the following form code:
        <FORM action="<portlet:renderURL/>">
            I'm thinking of a number between 1 and 10.<BR><BR>
            <I>What is it?</I>
            <INPUT name="<portlet:namespace/>number" type="text" size="10" />
            <INPUT name="submit" type="submit" value="Guess!!" />
        </FORM>When I submit this form, I see the parameter in my browser's URL window prefixed with the portlet namespace:
       http://host:port/portal/page/portal/portalpage?__ns36_5643_36_1_1_number=3&submit=Guess%21%21Here is how I'm trying to get the "number" parameter in the Java class associated with this jsp:
                String number = (response.getNamespace()+"number");I have also tried with
                String number = response.getParameter("number");In both cases the variable number gets assigned the null value.
    How can I capture parameters sent by a form on a JSP page on the portlet's Java class?
    I am developing this portlet application with JDeveloper 10.1.3.3.0.4157 and deploying to Oracle Application Server 10.1.2.0.2 with a wsrp-compliant container. Portlet is consumed in Oracle Portal 10.1.4.
    Thank you for your response.

    I'm sorry; I typed it wrong:
    It's
    String number = request.getParameter("number");However, if you're referring to the namespace, then the way I have on my book (Portlet Programming, Effectively Using the JSR-168 Standard, by Cameron McKenzie) is really
    (response.getNamespace()+"number")

  • JSR 168 and Web Services For Remote Portlets

    Hi,
       I have recently joined SAP.In my previous work experience I have worked extensively on the Sun Java Portal Server and was curious about the following
    1.Does SAP Enterprise Portal Server support JSR 168 compliant Portlets.
    2.If yes the Question that naturally follows is:Can portlets(view Components)in a SAP Portal be remote enabled?In other words does SAP portal support WSRP standards.
    3.If the SAP Enterprise Portal has implemented  the JSR 168 specifications then how does the architecture seperate out the Portal engine from the Portlet Container.
    In other words where does the actual wrapping from a HTTPServletRequest to a Portlet Request happen?
    4.The JSR 168 specifications restricts the use of IFrames and many HTML tags in the fragments that are returned by the portlets running in the Portlet Container.Is this taken care of in SAP Enterprise Portal?
    5.Can WebDynpro applications be embedded in a JSR 168 compliant portlet?
    6.How is parity maintaned between portlet session HTTP session and the Applications session?
    7.Does SAP Portal support deployment through a par model?
    Thanks and Regards
    Sujeet Mishra
    SAP Labs India Ltd
    [email protected]

    > 1.Does SAP Enterprise Portal Server support JSR 168
    > compliant Portlets.
    I'd like to know the answer to this question as well. I wrote an email but didn't receive any response. So i guess JSR 168 isn't supported yet?

  • Parameter passing and forwarding issues with 10.1.4 JSR 168 portlets

    Hi,
    I'm using version 10.1.4 version of Oracle Portal Server, and am trying to move a JSP web application to a JSR 168 compliant portlet.
    I am experiencing these issues:
    1. There are <form> tags in my JSPs. I've set the action attribute to "<portlet:actionURL>". This works okay and I can see the parameters in my processAction properly. However, if I modify the action attribute to "<portlet:renderURL>", I do not see any parameters in my doView(). Is this expected or a known bug?
    2. As a workaround of the issue #1, in my processAction, I'm using response.setRenderParameter(). This works but has a serious side effect: the first set of values set are set permanently for the session. Subsequent submissions of my JSP fail to alter the values. Is this expected? This problem is not there if setRenderParameter() is not used.
    3. My JSPs use request.setAttribute() and request.getSession().setAttribute(). I don't see these attributes in my processAction using request.getAttributeNames(). Is there another way of retrieving them?
    4. In my JSP, I have this code in a method declaration:
    String forwardPage = "hello.jsp";
    RequestDispatcher forwarder = request.getSession().getServletContext().getRequestDispatcher(forwardPage);
    forwarder.forward(request, response);
    This results in an exception on the server:
         06/05/07 00:25:10 AnupamPortlets: JspServlet: unable to dispatch to requested page: java.lang.NullPointerException
         at com.evermind.server.http.HttpApplication.isLegalFileSystemPath(HttpApplication.java:1298)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:502)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
         at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:253)
         at opportunity_detail____contacts__view._Controller.processRequest(_Controller.java:2516)
         at opportunity_detail____contacts__view._Controller._jspService(_Controller.java:2592)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
         at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121)
         at oracle.webdb.wsrp.server.RequestDispatcherImpl.include(Unknown Source)
         at mypackage1.Portlet1.doView(Portlet1.java:158)
    I've tried moving the page around and using request.getContextPath() and getNamedDispatcher(), but same error.
    This is supported, right? I saw some old messages about this being a bug on the PDK side.
    Actually, using forwarder.include() works, but causes other issues
    Any ideas what I can try of any of these will be greatly appreciated. Thanks.

    Hi Anupam,
    I can help you with question #2.
    2. As a workaround of the issue #1, in my processAction, I'm using response.setRenderParameter(). This works but has a serious side effect: the first set of values set are set permanently for the session. Subsequent submissions of my JSP fail to alter the values. Is this expected? This problem is not there if setRenderParameter() is not used.
    I believe that the issue is an artifact of the interpretation of the JSR-168 specification by Oracle. I discovered that the setRenderParameter basically ends up sending a redirect back to the browser with the render parameters in the URL. This raised security concerns as you may have wanted to pass some sort of internal data from your action to your render request. The parameters in the url "hang around" once they are there so your portlet keeps recieving them. Based on this behavior I have decided to not use setRenderParameter in Oracle portal.
    -sean
    Solutions Architect
    www.sagelogix.com

  • How to DEPLOY and ACCESS JSR 168 portlet in weblogic server

    I installed Web Logic Server 10.3, Web Logic Portal 10.3 and Workshop 10.3 on my system. I created a sample portal application in workshop and able to see the output with the help of workshop.
    1. I imported JSR 168 portlet in "Import Utility" and able to see the deployed war in Deployments folder of "Weblogic Server Administration Console", but unable to test that deployed portlet. That Deployed portlet was unable to see in "Weblogic Portal Administration Console"
    2. How can i import JSR 168 portlet from workshop and view that portlet?
    3. How can i import JSR 168 portlets from "Weblogic Portal Administration Console" and view them?
    Please help me out with the solutions and procedures...
    Thanking you in advance,
    Bhargavi Javvadi.

    Create a WAR file for your Web app
    Put it where the Weblogic 8.1 docs tell you to.
    Restart Weblogic server.
    %

  • 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 of JSR 168 and JSR 286 portlets

    Hi,
    As far as I know there is no direct support for JSR 168 compliant portlets in the SAP portal. Remote portlets can be consumed using WSRP. I was wondering whether the SAP portal will provide direct support for JSR 168 or even JSR 286 portlets in future releases?
    Regards,
    Kevin

    Hi Kevin,
    Long time ago SAP promised to implement JSR 168. Nowadays, you don't find much official documentation stating SAP portal is JSR168 compliant.
    SAP introduced the Federated Portal Network (Consumer and Producer portals), also with WSRP support.
    Check:
    cheers,
    Noë

  • 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]

Maybe you are looking for