JSR 168 API question

Hi,
How can i forward the request to another "Page" using JSR 168 ?
Where can i find JSR-168 code examples other than the one shipped with JSR168-Struts
bea package ?
Thanks

Carl,
The portlet API does not support the use case you're looking for. The
API has no notion of pages.
WebLogic portlet container, however, does support this use case. Try
using render:pageUrl as in the following example
Click ">here</a> to to goto
page X.</p>
where pageX is the definition label of that page.
Subbu
Carl Samson said the following on 12/08/2003 08:15 AM:
Hi,
How can i forward the request to another "Page" using JSR 168 ?
Where can i find JSR-168 code examples other than the one shipped with JSR168-Struts
bea package ?
Thanks

Similar Messages

JSR 168 APIs

Dear All,
We are trying to get content from IBM Websphere Portal v5.1 and display in our SAP portal . The content in IBM portal is stored in portlets . IBM recommended us to call their JSR 168 API's to just grab the content. We only want the content not the formatting. We cannot use URL iviews as their URL has not only the content but also a navigation panel , and we do not want the navigation panel.
I believe our Portal EP 7.0 can support JSR 168 compliant API from some of the information we found in SDN . But we are not able to locate the any how to guide on how to call such API from SAP whether from ABAP or Java we have no idea. Does anyone have something like a How to guide/ even sample code on how to call JSR 168 API or how can I proceed with this.
Best Rgds

hey you need to set up federated portal network(FPN) to establish this.i had done this before. i you only want webshpere portal content to be displayed in SAP EP, then implementing FPN alone wil do.if you want to dispay the content from SAP EP in IBM websphere then you need to do some coding in portal side to make your application jsr168 compliant
Message was edited by:
jeyasingh samuel Durairaj

JSR-168 Consumer question

Hi,
I am new to plumtree portal but have used some other JSR-168 compliant portals such as exo and websphere. I want to reuse some of the portlets I created in plumtree portal. It seems installing the JSR-168 consumer on the portal server and remote server is a good way to achieve that.
Are there any concerns with installing the JSR-168 consumer on the portal server side? Any performance pennalties, compatibility issue etc? I am going to bring this up to our portal admin once I can get more information regarding it here.
Thanks
-Chengmin

test
<chengmin ding> wrote in message news:[email protected]..
Hi,
I am new to plumtree portal but have used some other JSR-168 compliant
portals such as exo and websphere. I want to reuse some of the portlets I
created in plumtree portal. It seems installing the JSR-168 consumer on
the portal server and remote server is a good way to achieve that.
Are there any concerns with installing the JSR-168 consumer on the portal
server side? Any performance pennalties, compatibility issue etc? I am
going to bring this up to our portal admin once I can get more information
regarding it here.
Thanks
-Chengmin

Consuming web services in a jsr 168 portlet best practices.

I am building portlets (jsr 168 api in Websphere Portal 6.0 using web service client of Rational). Now needed some suggestions on caching the web services data on the portlet. We have a number of portlets (somewhere around 4 or 5) on a portal page which basically rely on a single wsdl Lotus Domino Web Service.
Is there a way I can cache the data returned by webservice so that I dont make repeated calls to the webservice on every portlet request. Any best practices/ideas on how I could do avoid multiple web service calls would be appreciated ?

Interestingly, as it often happens with Oracle portal, this has started working without me doing anything special.
However, the session events my listener gets notified of are (logically, as this portlet works via WSRP) different from user sessions. The problem I'm trying to solve now is that logging off (in SSO) doesn't lead to those sessions being destroyed. They only get destroyed after timeout specified in my web.xml (<session-config><session-timeout>30</session-timeout></session-config>). On the other hand, when they do expire, the SSO session may still be active, in which case the user gets presented with the infamous "could not get markup" error message. The latter is unacceptable in our case, so we had to set session-timeout to a pretty high value.
So the question is, how can we track when the user logs off. We have found the portal.wwctx_sso_session$ and portal.WWLOG_ACTIVITY_LOG1$ (and ...2$) tables, but no documentation for them. However, the real problem with using those tables is that there's no way we could think of to match the portlet sessions with SSO sessions/actions listed in the tables. (Consider situation when someone logs in from two PCs.)
Any ideas?

Converting PDK Portlet calls to JSR 168 portlet calls

Hi,
I am working on making Worklist 10.1.3 portlets WSRP compatible. For that i am converting PDK java calls to equivalent JSR 168 API calls ... I have made some changes and stuck on few things .
Can anyone help me equivalent JSR of these calls .
NOT DONE :--
String actionParam = PortletRendererUtil.getEditFormParameter(pReq);
PortletRendererUtil.submitEditData(pReq, data);
String myURL = pReq.getRenderContext().getPageURL(); // Gets the URL of the page that invoked this portlet.
prevPgURL = UrlUtils.parameterizeLink(renderRequest, UrlUtils.PAGE_LINK, wlPgStartKey+"="+prevPgStart); //Adds new parameters to an existing link
String portletKey = pReq.getPortletInstance().getInstanceName(); // Gets the Portal generated name of the PortletInstance.

Nisabhar,
You could try the [url http://forums.oracle.com/forums/forum.jspa?forumID=14]OAS Portal Forum, as your question doesn't have anything to do with JDeveloper.
John

How to debug jsr 168 portlet in jdeveloper 10.1.3.4

Does anyone know how to locally debug a jsr 168 portlet in jdeveloper 10.1.3.4.
When I click on run it asked for a start page so I supply the view.jsp page.
The following error occurs on the page:
500 Internal Server Error
java.lang.NullPointerException at helloworld.html._view._jspService(_view.java:61) [helloworld/html/view.jsp] at com.orionserver[Oracle Containers for J2EE 10g (10.1.3.4.0) ].http.OrionHttpJspPage.service(OrionHttpJspPage.java:59) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:122) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:111) at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260) at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234) at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29) at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298) at java.lang.Thread.run(Thread.java:595)
This is the first jsr 168 portlet I have tried.
Previously we have been created portlets using the Oracle PDK. Those portlets are easy to debug because the wizard creates an index.jsp page for the start page.
If anyone can provide some insight to my issue it would be greatly appreciated.
Thanks,

Is this a portlet you built from scratch using the JSR 168 APIs, or is this a JSF Portlet using the JSF Portlet Bridge. If the latter, you can debug your JSF application. If the former, you can do remote debugging (let me know if you need information on this).
Hope this helps,
Peter

JSR 168 and UIX.

Hi,
Iam a newbie working on an JSR 168 app that makes an existing portlets as JSR 168 compatible. The portlets was orginaly developed usign the JPDK api and to incorporate standards we are making it as JSR 168 compatible.
We used the UIX pages as the front end for showing portlet content. Is it possible to leverage the existing UIX pages using the JSR 168 API. For Rendering the UIX content we used the JPDK classes like the RenderManager , PortletContainerRenderer etc.
As i understand JSR 168 provides the RenderRequest which represents the request sent to the portlet to handle a render. Can this RenderRequest be used to display UIX pages.
Just wanted to know a couple of things.
a) JPDK providers RenderManager , PortletContainerRenderer etc are there equivalents in the JSR 168 API
b) Difference between the RenderRequest of the JSR and the PorletRenderRequest class .
At a brief Iam looking for an equivalents of in the JSR 168 API which can accomplish this.
Thanks
Mouli

Hi Mouli,
In case of JPDK always you will get single request i.e., HttpServletRequest from the portlet.you can get the PortletRenderRequest from HttpServletRequest.
Way to get PortletRenderRequest from HttpServletRequest :
===========================================
PortletRenderRequest portletRenderRequest=(PortletRenderRequest)oHttpServletRequest.getAttribute("oracle.portal.PortletRenderRequest");
[NOTE : you need to import the following class.
import oracle.portal.provider.v2.render.PortletRenderRequest;]
In case of JSR 168 generally you will get two kinds of request ie., RenderRequest & ActionRequest.Where PortletRequest is the parent interface for this two interfaces.
For Ex.whenever the portlets first time loaded on portalpage the portlet will get RenderRequest & it will create its own portlet markup.When ever you perform any operation in any portlet then it will have ActionRequest & remaining portlets will have RenderRequest.
Please feel free to ask anything related to portal technology..Let me know if i specified anything wrong.....
Thanks & Regards.,
Bala S Murugan.,
sendrequestgetresponse At Gmail Dot Com
http://balamurugan-portlets.blogspot.com/

Is it possiable to use "ALI SCRIPTING FRAMEWORK API " in JSR 168 Portlets?

Hi,
Is it possiable to use "ALI SCRIPTING FRAMEWORK API " in JSR 168 Portlets.
With Regards
Dheeraj Sai

If you want to use (let say it's possible) "ALI SCRIPTING FRAMEWORK API" in JSR 168 then these porlets are not "JSR-168" compatible anymore. So you automatically lost the main benefit of JSR-168 portlet - works over different portal vendors.
I guess if you have decided use JSR-168 you did this for reasons. Then stay this way and don't use any proprietary technologies.
By the way, this topic may help:
http://forums.bea.com/bea/message.jspa?messageID=500025455&tstart=0
Edited by Bryazgin at 05/18/2007 6:36 AM

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-

JSR 168 portlets packaging question

Hello,
I have a bunch of Java (JSR 168, using Spring MVC) portlets (PortletOne, PortletTwo...PortletN) that I created as individual Portal Web projects and are contained in a Portal EAR project. This portal EAR is my deployment unit and also consists of another Portal Web project (Assembly.war) that holds a app.portal file where I plan to assemble all these Java portlets and use it to create a desktop. The reason for having all the individual portlets in web projects of their own is to be able to export them as a unit and use it elsewhere either as a shared library or package it within another EAR file as the need arises.
my application.xml looks somewhat like this:
<?xml version="1.0" encoding="UTF-8"?>
<application id="Application_ID" version="1.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd">
     <display-name>MyEar</display-name>
     <module id="WebModule_1">
          <web>
               <web-uri>Assemby.war</web-uri>
               <context-root>appname</context-root>
          </web>
     </module>
     <module id="WebModule_2">
          <web>
               <web-uri>PortletOne.war</web-uri>
               <context-root>PortletOne</context-root>
          </web>
     </module>
     <module id="WebModule_3">
          <web>
               <web-uri>PortletTwo.war</web-uri>
               <context-root>PortletTwo</context-root>
          </web>
     </module>
</application>But since all these WAR files are at the same level I cannot reference the context definitions and the controllers for the portlets defined in each of these portlet WAR files (PortletOne, PortletTwo,...) from the common web project that holds the app.portal file in Assembly.war. I tried to define a custom classloader structure in weblogic-application.xml and put the assembly war file at a lower level but the app even fails to deploy with IllegalAccessError as soon as a context for each of the war files is registered by the hot deploy process. Moreover, when I deploy the EAR file, the portlets defined in each of the WAR files do not appear in the Resources library when viewed from the Portal Administration console.
Any suggestions how to assemble these individual portlets into a common web project, while still keeping them packaged within the same EAR file? Alternate approaches are welcome too.
I have already considered deploying these portlet WAR files as Weblogic J2EE shared libraries. But with this approach, the overall application response time is very slow in spite of exhausting all tuning options and also cannot pre-compile JSPs in the shared libraries.
Is importing the JSR-168 portlets using the import utility as WSRP portlets a viable option? Will I be able to share session variables across portlets, fire and handle events and be able to pre-compile the JSP in idividual portlets?
Edited by: shyam6190 on Aug 13, 2009 1:25 PM

Hello,
Perhaps the multiple nested classloaders involved with the shared libraries approach is slowing it down- if that is the case, it would be hard to fix.
Using WSRP should work for you; there is a bit more complexity but if you have relatively simple portlets, use the correct JSR168 tags and methods (or the Spring bridge does), it shouldn't be too hard to get to work. The IDE may be able to help you with that; you can create a new portlet of type "remote portlet" in your aggregated webapp, and a wizard will walk you through the steps. If you use local proxy mode, the portlet's individual WSDL URL will be the URL to each portlet's webapp on localhost.
The WSRP configuration can also be done dynamically in the Portal Admin Tools, and even using a specialized JSR168 import tool, but both of these options would only create database instances of portals and portlets in your aggregating webapp. This would be fine if your aggregated EAR never needs to move to a different deployment environment, but if you require portability of the EAR to another environment it complicates packaging, as database information is also required. If you happen to be using WLP version 10.3, I believe there is a bug which prevents the specialized JSR168 import tool from working, but the tool is documented here:
http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/prodOps/deployment.html#wp1047337
Since all the WSDL URLs will point only to the localhost, when you package the aggregated WAR file it should deploy properly to any servers. Information about the local proxy mode, which should improve performance for your configuration, is described here:
http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/federation/Chap-Best_Practices.html#wp1010714
Hope this helps!
Kevin

JSR-168 vs Page Flow question

Hi,
I i use JSR-168 to do my Portlets instead of page flow, which functionnality/features
will i loose ?
Thanks

Two main features
* Managing flow: WLW can help manage flow for pageflows, but with JSR168
portlets, you need to create the flow programmatically.
* Databinding: Pageflows support advanced databinding features, and
these features are not part of the spec defining JSR168 portlets.
Subbu
Carl Samson said the following on 12/08/2003 07:12 AM:
Hi,
I i use JSR-168 to do my Portlets instead of page flow, which functionnality/features
will i loose ?
Thanks

Online chat, Aug. 12, n the Portlet Specification (JSR 168)

The Portlet Specification, JSR 168 ( http://jcp.org/en/jsr/detail?id=168 ), establishes a standard API for creating portlets. It's designed to ensure interoperability between portlets and Java-based portal servers or other Web applications that implement the specification. Learn more about the Portlet Specification, and get questions answered in this chat with Portlet Specification co-lead Alejandro Abdelnur, and Sun ONE Portal Server product manager Adam Abramski. The chat is scheduled for Tuesday, August 12, at 11 A.M.-to-noon Pacific Daylight Time (6:00 P.M.-to-7 P.M. GMT).
To join the chat on August 12, go to http://developer.java.sun.com/developer/community/chat/index.html and click on "Join the current session".

The transcript of this chat is now available at http://developer.java.sun.com/developer/community/chat/JavaLive/2003/jl0812.html

Online Chat, Aug. 12, on the Portlet Specification (JSR 168)

The Portlet Specification, JSR 168 ( http://jcp.org/en/jsr/detail?id=168 ), establishes a standard API for creating portlets. It's designed to ensure interoperability between portlets and Java-based portal servers or other Web applications that implement the specification. Learn more about the Portlet Specification, and get questions answered in this chat with Portlet Specification co-lead Alejandro Abdelnur, and Sun ONE Portal Server product manager Adam Abramski. The chat is scheduled for Tuesday, August 12, at 11 A.M.-to-noon Pacific Daylight Time (6:00 P.M.-to-7 P.M. GMT).
To join the chat on August 12, go to http://developer.java.sun.com/developer/community/chat/index.html and click on "Join the current session".

The transcript for the chat is now available at http://developer.java.sun.com/developer/community/chat/JavaLive/2003/jl0812.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 :).

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

JSR 168 API question

Similar Messages

Maybe you are looking for