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...

Similar Messages

  • 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 Under WebSphere?

    If we develop portlets using JSR 168/ WSRP for Plumtree using WebSphere Studio and WebSphere (rather than WebLogic), should they work?
    If there were problems that required a Plumtree fix, would such a fix be provided under normal support?
    Thanks.

    If we develop portlets using JSR 168/ WSRP for Plumtree using WebSphere Studio and WebSphere (rather than WebLogic), should they work?
    If there were problems that required a Plumtree fix, would such a fix be provided under normal support?
    Thanks.

  • 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

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

  • 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 :).

  • JSR-168 Support

    Do we have any plans to resume support for JSR-168 portlets to extend integration with other portal platforms besides WCI and WLP?

    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 :).

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

  • JSR 168 and Struts support sample error

    I'm trying to get the sample webapp for JSR 168 and Struts support working with
    WebLogic 8.1, and I'm having problems with the struts portlet. The other portlets
    seem to work fine, but the Struts portlet gives the following error after clicking
    "Save" on most of the forms:
    Page Flow Error - Action Not Found
    Page Flow: Global.app
    Action: html-setters.do
    Unable to find action html-setters.do.
    That error appears in the browser. At the same time, the following exception
    appears in the server window:
    <Aug 18, 2003 4:34:12 PM EDT> <Error> <netui> <BEA-420012> <There was an error
    while running a lifecycle stage :: Lifecycle: UIControl.render :: for the control
    :: null ::.
    com.bea.netuix.nf.UIControlException: For portlet [strutsPortlet], could not do
    page flow lookup for the given action [html-setters.do] in the given PageFlow:
    [struts/exercise-taglib].
    This exception is followed by hundreds of lines of the following:
    at com.bea.wlw.netui.pageflow.scoping.ScopedServletUtils.strutsLookup(ScopedServletUtils.java:363)
    as well as several stack overflow errors.
    I believe I have installed the JSR168 and Struts support package according to
    the instructions, and have copied the required jars into the samples WEB-INF/lib
    directory. I also have tried to write my own Struts application in a portlet,
    and it gets the exact same errors when I try to submit a form to my actions.
    Any insight would be much appreciated!
    Thanks,
    Patrick

    Hi Brodi,
    I am having the same problem as Patrick. The problem is not in the struts portlet,
    but in the forms the portlet navigates to. After the struts portlet loads, I
    am able to use the html:links and navigate through the pages. Though when I try
    to submit a form I get the action not found error. For example the html-select
    page has a form. This page loads fine, but when I hit the save button I get the
    following error.
    <Aug 25, 2003 11:00:00 AM EDT> <Error> <netui> <BEA-420012> <There was an error
    while running a lifecycle stage :: Lifecycle: UIControl.render :: for the contro
    l :: null ::.
    com.bea.netuix.nf.UIControlException: For portlet [strutsPortlet], could not do
    page flow lookup for the given action [html-select.do] in the given PageFlow:
    struts/exercise-taglib].
    The application appears to loose the struts context. It tries to find the localhost:7001/samples/html-select.do
    action instead of localhost:7001/samples/struts/exercise-taglib/html-select.do
    action. How do I keep the application from loosing context?
    Thank you,
    Karen
    "Brodi Beartusk" <[email protected]> wrote:
    >
    Patrick-
    I've seen similar things happen when the module name is either not specified
    correctly
    in the StrutsContent element in the portlet, or when the module is misconfigured,
    usually because of either a mising config file or a mis-named config
    file.
    Ensure that you have a the struts config file for the exercise-taglib
    module in
    WEB-INF, named jpf-struts-config-struts-exercise-taglib.xml.
    -Brodi Beartusk
    "Patrick Callis" <[email protected]> wrote:
    I'm trying to get the sample webapp for JSR 168 and Struts support working
    with
    WebLogic 8.1, and I'm having problems with the struts portlet. Theother
    portlets
    seem to work fine, but the Struts portlet gives the following errorafter
    clicking
    "Save" on most of the forms:
    Page Flow Error - Action Not Found
    Page Flow: Global.app
    Action: html-setters.do
    Unable to find action html-setters.do.
    That error appears in the browser. At the same time, the followingexception
    appears in the server window:
    <Aug 18, 2003 4:34:12 PM EDT> <Error> <netui> <BEA-420012> <There was
    an error
    while running a lifecycle stage :: Lifecycle: UIControl.render :: for
    the control
    :: null ::.
    com.bea.netuix.nf.UIControlException: For portlet [strutsPortlet], could
    not do
    page flow lookup for the given action [html-setters.do] in the given
    PageFlow:
    [struts/exercise-taglib].
    This exception is followed by hundreds of lines of the following:
    at com.bea.wlw.netui.pageflow.scoping.ScopedServletUtils.strutsLookup(ScopedServletUtils.java:363)
    as well as several stack overflow errors.
    I believe I have installed the JSR168 and Struts support package according
    to
    the instructions, and have copied the required jars into the samples
    WEB-INF/lib
    directory. I also have tried to write my own Struts application ina
    portlet,
    and it gets the exact same errors when I try to submit a form to myactions.
    Any insight would be much appreciated!
    Thanks,
    Patrick

  • 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

  • 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

  • JSR 168 support and portlet taglib

    I could not find support for the ActionURL tag in the JSR 168 release for 8.1.
    Are these tags available? If so, where can I find them?
    Thanks,
    Steve

    Chris,
    You can obtain an instance of renderRequest from the http request as in:
    <%
    RenderRequest renderRequest = (RenderRequest)
    request.getAttribute("javax.portlet.request");
    %>
    Alternatively, if you've JSP base class set to
    com.bea.portlet.jsp.PortletJspBase in your weblogic.xml (see WLS docs on
    how to set a default base class for JSPs), all JSPs in your webapp can
    automatically access renderRequest, renderResponse and portletConfig
    variables directly, as in
    <%
    renderResponse.createActionURL(...);
    %>
    Subbu
    Chris Jennings wrote:
    I need custom tags that can get the namespace of a portlet. I don't mind writing
    some to fill the gap until the final release. How can I get access to the RenderRequest
    from in a home grown custom tag now?
    Thanks!
    Chris
    Subbu Allamaraju <[email protected]> wrote:
    These tags will be available in the final release. The preview release
    does not include this tag library.
    Subbu

  • 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"/>

  • How to convert JSR 168 compliant Portlets into SAP supported iViews.

    Hi,
    How to convert JSR 168 compliant Portlets into SAP supported iViews in SAP NetWeaver 2004.
    Thanks & Regards
    Siva

    Guys,
    JSR is not supported untill NW05. Please check this
    /thread/176954 [original link is broken]
    Akhilesh

Maybe you are looking for