Jsr168 portlet problem

Hi,
I am creating a JSR168 compliant portlet with
A single form that contains:
- a search field
- a table that displays radiobuttons and search query results
- a button that sets a navigation parameter depending on the itemID that was picked from the table
The problem is that while my search-query parameter is processed fine when running the application locally,
I can not access the input parameter when the portlet is deployed to an OC4J container on a Webcenter Application Server and running in an ADF Faces jspx dashboard.
In my portlet JSP page I have the search field:
<input type="text" name="query">
and I process it with a page refresh and the following:
request.getParameter("query")
which turns out to be null in the deployed portlet.
when I do request.getParameterNames() I get different results depending on whether I run the application in JDeveloper, or when I deploy the portlet and I run it in the dashboard.
getParameterNames() in the deployed portlet only displays my navigation parameter, while getParameterNames() running locally only displays my query parameter.
It seems as if parameters need to be treated differently. Any input would be appreciated!

Hi,
In view.jsp, I have the following under <portlet:defineObjects/>:
String actionURL = "view.jsp";
if (renderResponse != null) {
actionURL = renderResponse.createActionURL().toString();
My form is defined like this:
<form method="POST" action="<%= actionURL %>">
Thanks in advance!
Louisa

Similar Messages

  • Problem deploying JSR168 portlets; Tomcat, Win2003

    Dear All,
    Am having some problems deploying the JSR168 portlets on Tomcat 4.1 and Win2003.
    This is on Windows, and I have to manually deploy it per the instructions...
    So far I__
    1. Exploded the .war and added ptjsr168 to pthome.xml per the sparse installation pdf;
    2. stopped tomcat, deleted the cache (contents of the work directory), restarted.
    3. verified that the application appears in the work directory
    but get the error,
    /PtPortletContainer/portlet/RssPortlet/mode/view
    descriptionThe requested resource (/PtPortletContainer/) is not available.
    ...when I try to browse there to get the correct URL tp paste into the remote server, something like:
    http://portlets.mycustomer.com:8080/ptjsr168/
    The extension to this in the web service is, by default:
    /PtPortletContainer/portlet/RssPortlet/mode/view
    I may be typing the URL wrong, for all I know. Something simple.
    Any ideas?
    Cheers,
    Rob

    You can verify whether your portlet works correctly by testing it on OpenPortal Portlet Container(https://portlet-container.dev.java.net). Or if you think the issue is with Pluto Portal I would recommend posting your issue on the Pluto Portal mail alias.

  • Getting error while working with jsr168 portlet in weblogic portal 10.1

    Hi,
    I have configured jsr168 portlet to display RSS feed.I am not getting any error when I have logged in for 2 to 3 times. It's displaying fine.After that when I again login I am getting this error.
    I am not knowing what's the problem is?Let me know.
    java.lang.NullPointerException at com.bea.portlet.container.UserInfo.getAllProperties(UserInfo.java:149) at com.bea.portlet.container.UserInfo.updateUserInfo(UserInfo.java:117) at com.bea.portlet.container.AppContainer.invokeRender(AppContainer.java:704) at com.bea.netuix.servlets.controls.content.JavaPortletContent.fireRender(JavaPortletContent.java:249) at com.bea.netuix.servlets.controls.content.JavaPortletContent.renderInternal(JavaPortletContent.java:156) at com.bea.netuix.servlets.controls.content.JavaPortletContent.beginRender(JavaPortletContent.java:103) at com.bea.netuix.servlets.controls.application.laf.ContentControlRenderer.beginRender(ContentControlRenderer.java:48) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326) at com.bea.netuix.nf.UIControl.render(UIControl.java:582) at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486) at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146) at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62) at jsp_servlet._framework._skeletons._pcagreen.__flowlayout._jspService(__flowlayout.java:290) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454) at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130) at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72) at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326) at com.bea.netuix.nf.UIControl.render(UIControl.java:582) at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486) at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146) at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62) at jsp_servlet._framework._skeletons._pcagreen.__gridlayout._jspService(__gridlayout.java:292) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454) at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130) at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72) at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361) at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:162) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388) at com.bea.netuix.servlets.manager.UIServlet.processControlTree(UIServlet.java:301) at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:927) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.documentum.web.servlet.CompressionFilter.doFilter(CompressionFilter.java:108) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.documentum.web.env.WDKController.processRequest(WDKController.java:95) at com.documentum.web.env.WDKController.doFilter(WDKController.java:83) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.documentum.web.env.PortalRequestFilter.doFilter(PortalRequestFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:336) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.bea.portal.tools.servlet.http.HttpContextFilter.doFilter(HttpContextFilter.java:60) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200) at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    Edited by jhansi.mandalapu at 05/05/2008 11:20 PM
    Edited by jhansi.mandalapu at 05/05/2008 11:30 PM

    Thanks Brad !!!
    It works...
    earlier I had entitlements set only on Employee Portal and Calendar in the tree structure Community_repository > Calendar > EmployeePortal > Calendar.
    It didnt work and throwed that error.
    After your suggestion I set entitlements on groupware.calendar.appointment to create, view, update, delete and instantiate to true.
    It worked, thanks for your help.
    -Win

  • JSR168 portlet - How to acquire Portal user identity?

    My scenario is:
    - Write a JSR168 portlet to access data in an Oracle database
    - The portlet will use the identity of a Oracle Portal user, who currently logs in, to create the connection to that database
    - In the database, I create a global role, that in turn, assigned to an enterprise role, already granted to the portal user.
    - When that user logins the database, depend on his available roles, the database will control his access on data
    My problem is: how can I get the identity (username/password) of that Portal user to establish the connection to my database?
    If anyone know, plz give me some help. I'm very thankful.

    Dear Steven,
    Can you elaborate on your query a bit further?
    If you are looking for some SQL statement that will validate against a table for a given portal user then you can use the API wwctx_api of Portal.
    For example,
    SELECT FIELD1, FIELD2, FIELD3.....
    FROM TABLE1
    WHERE PORTAL_USER = WWCTX_API.GET_USER;
    I hope this helps.
    Thanks.
    Saabir.

  • Edit mode in JSR168 Portlet

    Hi all,
    I m using Portal version 10.1.4 and developing JSR168 Portlet using JDeveloper 10.1.2.1.0 (Build 1913).
    There is a edit mode in my portlet and i have done entry for this mode in portlet.xml and also implemented doEdit() method.
    inside doEdit() method i have also written response.setContentType("text/html");
    Successfully deployed the .ear and also registered the WSDL url.
    But when i click on the Personalize link of the portlet then a page comes with a message
    Error: Could not get markup. The cookie or session is invalid or there is a runtime exception.
    And the error in wsrp_default_island_1\application.txt is
    javax.portlet.PortletModeException: Portlet mode "edit" is not allowed in current context
         at oracle.webdb.wsrp.server.PortletURLImpl.setPortletMode(Unknown Source)
    Could any one tell me where i m doing wrong.
    help will be appreciated..
    Thnx
    ~Neeraj Sidhaye
    Try_Catch_Finally @ Y !
    ExtremePortal @ Gmail Dot Com

    Hi Harsha,
    Actually there is a problem with setPortletMode method of PortletURL.
    When i use
    PortletURL portletURL=renderResponse.createActionURL();
    portletURL.setPortletMode(PortletMode.EDIT); (Although it is not required , but in case if situation occurs like if i want to change the mode then it will fail)
    In this case if i click on Personalize link then it is throwing an exception.
    Is it bug with Oracle Portal , i don't know....
    When i comment that code then every thing is working perfectly for me
    and the required jsp is rendering in Edit mode of the Portlet.
    Comments ans Suggestions are welcome at 24*7 :-)
    Thnx
    ~Neeraj Sidhaye
    Try_Cactch_Finally @ Y !
    ExtremePortal @ Gmail Dot Com

  • Deploy jsr168 portlet in weblogic

    Hi,
    I'm developing a jsr168 portlet that I would like to be able to deploy in the Weblogic Portal (among others).
    The problem is, after much searching, that I can't figure out how to do it.
    In Websphere I just deploy the .war file through the portal administration web interface and away I go.
    In jetspeed2 I just drop the .war file in the deploy folder and it gets deployed.
    Is there anything similar for Weblogic?
    I've currently got 8.1 SP4 installed.
    I've seen and even tried the portletPreparer tool but I can't get it to work (dependencies on bea classes that I can't find).
    Any help or tips on how to deploy a portlet in a .war file would be greatly appreciated.
    Cheers,
    Eric

    Hi,
    Generally while creating a jar file for deplyong a EJB on an App Server, create a folder called META-INF and copy all your xml files to this folder
    this command could be part of your build.xml if ur using ant
    mkdir build build\META-INF
    copy *.xml build\META-INF
    Then compile ur java files and then create the required jar or ear file for deployment.
    Rgds,
    Seetesh

  • Themes and JSR168 Portlets

    Hi,
    How can I get the information about current themes from JSR168 Portlet classes.
    All Theme.class methods have ProviderContext as parameters. PortletContext is not the same.
    Joanna

    This is a known problem with the preview release, and a fix will be
    included in SP2.
    Subbu
    Ramesh K said the following on 12/09/2003 07:01 AM:
    Is there anyone who can answer this? Has anyone tried using Visitor tools with
    JSR168? Did it work? I am anxious to find out ! Thanks
    "Ramesh" <[email protected]> wrote:
    There seems to be a problem with using the Visitor Tools when the portal
    contains
    JSR 168 portlets.
    When accessing the visitor tools with a JSR168 portlet on a page, the
    Visitor
    Tools throw errors/exceptions. The exception point to portletInstanceId
    being
    NULL or "". The exception occurs on line no 153-155 in visitorToolsMain.jsp.
    Any workarounds? Thanks

  • JSR168 portlet packaging?

    From the JSR168 spec, (which is similar to how other portals seem to behave
    with their proprietary APIs), a JSR168 portlet application appears to be a
    WAR with a portlet.xml and web.xml conforming to the requirements of the
    spec, that can then be installed in any portal.
    From my superficial knowledge based on skimming the WL8.1 portal docs
    recently, WL portlet development appears to be done within a Portal WAR such
    that the portlet(s) are just components of the portal war itself.
    How are these two supposed to work together in the WLP env? Say I develop a
    couple JSR168 portlets in my own Java environment (emacs :-) and then WAR
    them up and install them into Jetspeed-2 and another 168 compliant portal
    when available (eg, IBM's 5.something). I believe those would accept my
    portlet WAR and keep them in that WAR and just reference them from their
    Portals. How would WL8.1.x handle such development (outside of Workshop/WL)
    and deployment to a WL8.1.x portal? Do I have to merge my JSR168 based
    portlet WAR (and thus a web.xml and portlet.xml merge) into the Portal WAR
    (eg, if I want to ship a script to deploy my portlet WAR into an existing
    WL8.1 portal?) or will WL8.1.x be able to reference a Portlet WAR outside of
    a Portal WAR?
    TIA - a confused potential portlet developer...

    I agree with what Joe said...
    BTW, I (and I assume Joe) think JSR168 is a good thing - and it's great that
    WLP has the first prototype of it out there - don't get me wrong, I like it,
    I'd just prefer if it were easier to deploy to given portlets coming in from
    multiple sources being added into an existing portal. From Joe's case, he
    probably doesn't want to have to merge the portlet.xml files. From my case
    as a supplier of portlets, I'd rather not have to have to create different
    install tools/docs/procedures for my customers for each portal vendor now
    that I can have standard portlets based on JSR168...
    "Joe C." <[email protected]> wrote in message
    news:[email protected]...
    You can always import any arbitrary webapp using the WLW as a portalproject
    I'm not sure that solves my problem or the one ISV was talking about(which
    I assume is the same).
    I am not talking about importing a webapp (containing portlets or nto) and
    making it be my portal.
    - Assume I'm already developing a portal with some in-house developed
    portlets.
    - I want to get 3 JSR168 portlets from SAP (just picked a random vendorout
    of the air) and add them to my portal.
    - I want to get 2 JSR168 portlets from Siebel (ditto)
    - And I need one Domino portlet from that other 3 letter vendor (ditto)
    - Each of those vendors is likely to build JSR168 portlets that can be
    installed/used in any JSR168 compliant portal, so they can stop buildingall
    the various per-vendor proprietary API portlets.
    - Each of those vendors needs to package up their portlets for
    shipping/install.
    - Given that JSR168 describes the Web App layout for packaging a portlet,
    each of those vendors is likely to package their portlets up in a WAR.
    - Some JSR168 compliant portals (I believe) will be able to just install
    those WARs and use them as is from the Portal WAR and drop them on pages.
    - WLP 8.1 appears to require that I unpack/extract those WARs and mergethe
    portlet.xml and contents of each of those WARs with my existing Portal WAR
    that I want to add those portlets to. Tell me why this is better?
    To your earlier comments made here:
    The pitfall of this approach is that webapps depend on each other towork correctly
    Well yeah, I expect my portal to depend on my portlets - of course.
    which is against the spirit of webapps.I disagree - EARs depend on the WARs within them. Cooperating WARs can
    depend on each other too.
    A deployer should be able to deploy/undeploy any webapp withoutaffecting the functionality of other
    webapps - which would be case in the model you describe.Of course, if you remove a portlet that a portal depends on, I wouldexpect
    it to break .
    In addition, there are security issues that the deployer must be awareof.
    Of course. That's the case with any J2EE deployment no matter how many
    EARs/WARs you're deployiing.
    "Subbu Allamaraju" <[email protected]> wrote in message
    news:[email protected]...
    Joe,
    You can always import any arbitrary webapp using the WLW as a portal
    project, and during that process you'll have the opportunity to
    automatically update the descriptors (and also adding the correct jar
    files). There is no need to hand-merge descriptors unless you want to.
    Subbu
    Joe C. wrote:
    Please tell me it's going to get better.
    That would make sense if one were developing all their own portlets
    for
    their portals.
    But I (and most people I know) as a customer, that needs to aggregate
    portlets from multiple (possibly many) 3rd parties, such as the big 4
    application vendors, am going to need to know how those standardJSR168
    portlets work and are configured so that I can hand-merge them into my
    company's portal?
    As an end user it doesn't really help me that much that I can developmy
    own
    portlets to JSR168. The whole point of JSR168 is that portlet vendorsthat
    build portlets for others to install into their portals will be able
    to
    build one set of portlets that can then be installed in any compliant
    portal. This limitation seems to prevent that from beingcommonplace/useful
    (given how few people are going to know how to do such merges - theyjust
    want to install 3rd party portlets and drop them on pages). I reallyhope
    Workshop provides a user friendly way to integrate such 3rd party
    JSR168
    portlets or WLP will be missing the whole point of having such astandard in
    the first place. I agree with the ISV that started this
    conversation -
    please provide a means for me to install 3rd party portlets withouthaving
    to hand-merge XML configuration files.
    "Subbu Allamaraju" <[email protected]> wrote in message
    news:[email protected]...
    isv wrote:
    From the JSR168 spec, (which is similar to how other portals seem to
    behave
    with their proprietary APIs), a JSR168 portlet application appears to
    be
    a
    WAR with a portlet.xml and web.xml conforming to the requirements of
    the
    spec, that can then be installed in any portal.For all practical purposes, a portal app is a web app, with the only
    differece being the portlet.xml file. So, a portal app contains
    portlets
    in addition to things that typically exist in a webapp.
    How are these two supposed to work together in the WLP env? Say I
    develop a
    couple JSR168 portlets in my own Java environment (emacs :-) and thenWAR
    them up and install them into Jetspeed-2 and another 168 compliantportal
    when available (eg, IBM's 5.something). I believe those would accept
    my
    portlet WAR and keep them in that WAR and just reference them fromtheir
    Portals. How would WL8.1.x handle such development (outside ofWorkshop/WL)
    and deployment to a WL8.1.x portal? Do I have to merge my JSR168
    based
    portlet WAR (and thus a web.xml and portlet.xml merge) into thePortal
    >>>
    WAR
    (eg, if I want to ship a script to deploy my portlet WAR into anexisting
    WL8.1 portal?) or will WL8.1.x be able to reference a Portlet WARoutside of
    a Portal WAR?For WLP, the unit of development/deployment is a webapp. We're aware
    that some implementations (including the ones you mention) follow a
    model where portal deployment involves several web apps with portlets
    aggregated by a portal deployed in one of those webapps. The pitfall
    of
    this approach is that webapps depend on each other to work correctly -
    which is against the spirit of webapps. A deployer should be able to
    deploy/undeploy any webapp without affecting the functionality ofother
    webapps - which would be case in the model you describe. In addition,
    there are security issues that the deployer must be aware of.
    Having said this, if your portlets are already bundled into a WARfile,
    you need to merge the portlets into the portal webapp. Or, you couldlet
    WL convert your webapp into a portal webapp. We don't intend tosupport
    portlet referencing from other webapps.
    Subbu

  • Portlet problem on Oracle Portal Server....

    Hi all,
    i m using Oracle Portal Server 10.1.2.
    Problem is as follows:-
    There are two portlets (P1, P2) added on two seperate portal tabs( TB1,TB2) respectively under Portal Builder.
    On portlet P1 when i do a action say Save and it saves the data.
    now i go to portlet P2 which is on tab TB2 and when i come back on TB1 to go on portlet P1 then in the PortletRenderRequest i still get action value as Save and it saves the previous data once more.
    in short....:- even moving on portal tabs the previous action of the last rendered portlet is firing.
    how it is persisting the action in request , even after i have done with moving on portal tabs.
    even on refreshing the page it is adding the same data again.
    But this doesn't happen with IBM Portal Server.(Tested the same code with all the above conditions)
    could any one please have some thoughts ???
    Always nJoy Work
    Neeraj Sidhaye
    try_catch_finally @ !
    ExtremePortal @ Gmail Dot Com

    Hi Guys,
    One good thing i found is
    When i perform the same operations (as described in the first post of this thread) with JSR168 Portlets then it is working Perfectly.
    So i feel , only the problem is with JPDK Porltet and not with Oracle Portal Server.
    It's good to see that JSR168 are working fine except
    portletURL.setPortletMode(PortletMode.EDIT) ( till now i found this only )
    nJoy Work
    ~Neeraj Sidhaye
    ChkOut_ChkIn @ Yahoo Dot Co Dot In
    ExtremePortal @ Gmail Dot Com

  • JSR168 Portlet Exception with Oracle OC4J and Spring

    JSR168 Portlet Exception with Oracle OC4J and Spring
    I’m having a problem with accessing a Spring JSR168 Portlet when deployed on Oracle OC4J. I have created a very simple portlet that just renders simple jsp page. I created two versions. One using GenricPortlet and one using org.springframework.web.portlet.mvc.AbstractContro ller. The non-Spring portlet deploys and runs as expected. The Spring portlet deploys but throws the following exception
    Code:
    07/11/05 08:23:44 [ERROR] DispatcherPortlet - Could not complete request <javax.portlet.PortletException>javax.portlet.PortletExcept
    ion
    at oracle.portlet.server.containerimpl.RequestDispatcherImpl.include(RequestDispatcherImpl.java:74)
    at org.springframework.web.portlet.DispatcherPortlet.render(DispatcherPortlet.java:1077)
    at org.springframework.web.portlet.DispatcherPortlet.doRenderService(DispatcherPortlet.java:809)
    at org.springframework.web.portlet.FrameworkPortlet.processRequest(FrameworkPortlet.java:475)
    at org.springframework.web.portlet.FrameworkPortlet.doDispatch(FrameworkPortlet.java:445)
    at javax.portlet.GenericPortlet.render(GenericPortlet.java:163)
    at oracle.portlet.server.containerimpl.ServerImpl.getMarkup(ServerImpl.java:161)
    at oracle.portlet.wsrp.v1.WSRPv1ToServer.getMarkup(WSRPv1ToServer.java:4512)
    at oracle.portlet.wsrp.v1.WSRP_v1_Markup_PortTypeSoapToJaxb.getMarkup(WSRP_v1_Markup_PortTypeSoapToJaxb.java:68)
    at oasis.names.tc.wsrp.v1.bind.runtime.WSRP_v1_Markup_Binding_SOAP_Tie.invoke_getMarkup(WSRP_v1_Markup_Binding_SOAP_Tie.java
    :60)
    at oasis.names.tc.wsrp.v1.bind.runtime.WSRP_v1_Markup_Binding_SOAP_Tie.processingHook(WSRP_v1_Markup_Binding_SOAP_Tie.java:7
    79)
    at oracle.j2ee.ws.server.StreamingHandler.handle(StreamingHandler.java:297)
    at oracle.j2ee.ws.server.JAXRPCProcessor.doEndpointProcessing(JAXRPCProcessor.java:413)
    at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
    at oracle.j2ee.ws.server.JAXRPCProcessor.doRequestProcessing(JAXRPCProcessor.java:277)
    at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
    at oracle.j2ee.ws.server.JAXRPCProcessor.doService(JAXRPCProcessor.java:134)
    at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
    at oracle.portlet.server.service.ContextFilter.doFilter(ContextFilter.java:86)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
    at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
    at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
    at com.evermind.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:239)
    at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
    at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: javax.servlet.ServletException: Error in servlet
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:759)
    at com.evermind.server.http.ServletRequestDispatcher.unprivileged_include(ServletRequestDispatcher.java:160)
    at com.evermind.server.http.ServletRequestDispatcher.access$000(ServletRequestDispatcher.java:51)
    at com.evermind.server.http.ServletRequestDispatcher$1.oc4jRun(ServletRequestDispatcher.java:97)
    at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
    at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:102)
    at oracle.portlet.server.containerimpl.RequestDispatcherImpl.include(RequestDispatcherImpl.java:65)
    ... 34 more
    Nested Exception is javax.servlet.ServletException: Error in servlet
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:759)
    at com.evermind.server.http.ServletRequestDispatcher.unprivileged_include(ServletRequestDispatcher.java:160)
    at com.evermind.server.http.ServletRequestDispatcher.access$000(ServletRequestDispatcher.java:51)
    at com.evermind.server.http.ServletRequestDispatcher$1.oc4jRun(ServletRequestDispatcher.java:97)
    at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
    at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:102)
    at oracle.portlet.server.containerimpl.RequestDispatcherImpl.include(RequestDispatcherImpl.java:65)
    at org.springframework.web.portlet.DispatcherPortlet.render(DispatcherPortlet.java:1077)
    at org.springframework.web.portlet.DispatcherPortlet.doRenderService(DispatcherPortlet.java:809)
    at org.springframework.web.portlet.FrameworkPortlet.processRequest(FrameworkPortlet.java:475)
    at org.springframework.web.portlet.FrameworkPortlet.doDispatch(FrameworkPortlet.java:445)
    at javax.portlet.GenericPortlet.render(GenericPortlet.java:163)
    at oracle.portlet.server.containerimpl.ServerImpl.getMarkup(ServerImpl.java:161)
    at oracle.portlet.wsrp.v1.WSRPv1ToServer.getMarkup(WSRPv1ToServer.java:4512)
    at oracle.portlet.wsrp.v1.WSRP_v1_Markup_PortTypeSoapToJaxb.getMarkup(WSRP_v1_Markup_PortTypeSoapToJaxb.java:68)
    at oasis.names.tc.wsrp.v1.bind.runtime.WSRP_v1_Markup_Binding_SOAP_Tie.invoke_getMarkup(WSRP_v1_Markup_Binding_SOAP_Tie.java
    :60)
    at oasis.names.tc.wsrp.v1.bind.runtime.WSRP_v1_Markup_Binding_SOAP_Tie.processingHook(WSRP_v1_Markup_Binding_SOAP_Tie.java:7
    79)
    at oracle.j2ee.ws.server.StreamingHandler.handle(StreamingHandler.java:297)
    at oracle.j2ee.ws.server.JAXRPCProcessor.doEndpointProcessing(JAXRPCProcessor.java:413)
    at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
    at oracle.j2ee.ws.server.JAXRPCProcessor.doRequestProcessing(JAXRPCProcessor.java:277)
    at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
    at oracle.j2ee.ws.server.JAXRPCProcessor.doService(JAXRPCProcessor.java:134)
    at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
    at oracle.portlet.server.service.ContextFilter.doFilter(ContextFilter.java:86)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
    at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
    at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
    at com.evermind.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:239)
    at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
    at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:619)
    2007-11-05 08:23:44.085 WARNING An internal error has occurred in method getMarkup()
    I have managed to deploy and run the Spring portlet using Sun App Server and Sun Portlet container with no problems which leads me to believe my Spring setup is correct.
    I also have managed to run the Spring pets portlet example on Sun App Server and Sun Portlet container with no problems. But again it fails on Oracle with the same problem.
    To deploy on Oracle I ran the oracle wsrp jar against my EAR. As far as I can tell it has not corrupted any of the Spring setup in the web.xml.
    The version are as follows
    Oracle Portal 10.1.4 running on OAS 10.1.2
    calling the portlet using WSRP v1.
    The portlet is running on standalone OC4J 10.1.3.3 with Oracle portlet container 10.1.3.2. On Windows Spring 2.0.6.
    Any ideas? Thanks Paul

    Was an answer ever found? I am currently experiencing the same issue.
    Edited by: user10567841 on Nov 8, 2008 12:21 PM

  • Jsr168 portlet issue

    Hi,
    1. I developped two jsr168 portlet and deployed them to java portlet container successfully, but the status of one is always not loaded, against, the status of the other is loaded, do you why?
    2. i want to add the portlet which its status is loaded to my page, but I cann't find it in the portal builder. Do you know where is it or how to find it or how to add a jsr168 portlet to a page after deploying it?
    thanks very much
    jason

    Thanks very much for your reply.
    because i don't want to use the JDeveloper to help me to develop and deploy the jsr168 compliant portlet on oracleAS10g Portal, so my question is that how to add my jsr168 portlet to a page when i deploy it successfully?
    In fact, I already finish developping the jsr168 portlet and deploy it to java portlet container on oralceAS10g successfully. but i cann't find it in the portal builder, so i don't know how to add it to my page. can you give me more information about it in detail? I don't think i can get enough information from the developer's guild pdf document, i read it, but i still cann't figure out my problem.
    thanks again
    jason

  • How to get Page URL inside a JSR168 Portlet

    Hi,
    How can i get the Portal's page URL inside a JSR168 Portlet?
    All I can see in renderRequest Object is information about the portlet itself not about the page it is inside.
    Thanks,
    André

    Hi Andre
    Please see this note on My Oracle Support. 433507.1
    Hope that helps!
    AMN

  • Floating JSR168 Portlets

    Is the floating window state available to JSR168 portlets? If it is where to set
    it? Thanks

    This is what I heard from tech support regarding floating JSR168 portlets!
    "I opened CR135056 for your case. I will let you know if I get response from our
    engineer."
    So, I guess we just have to wait and pray ! Thanks
    Martin Porter <[email protected]> wrote:
    >
    Hi,
    We are also attempting to use a floating portlet for help mode for non
    JSR-168 portlets but that does not work either. We currently have an
    open support case with BEA with this since 13th April and thus far no
    fix so i would not expect to see a fix in the short term as it seems
    floating portlets simply dont work !.
    Regards
    Martin
    Ramesh wrote:
    Hi Subbu,
    I tried your solution. It doesn't seem to work. I even rebuilt theapplication
    and redeployed (Do I need to do that when weblogic-portlet.xml is changed?).Can
    you please tell me what could be wrong? I checked the file to makesure there
    wasn't any typo or other mistakes.
    Thanks
    K. Ramesh
    Subbu Allamaraju <[email protected]> wrote:
    Add
    <portlet>
    <portlet-name>same_name_as_in_portelt_xml</portlet-name>
    <supports>
    <mime-type>same_mime_type_as_in_portlet_xml</mime-type>
    <window-state>
    <name>float</name>
    </window-state>
    </supports>
    </portlet>
    in weblogic-portlet.xml. The same can be used for adding delete support.
    Subbu
    Ramesh wrote:
    Anyone? Is it not possible? I would think it would be.
    On the same note, can the help for a portlet be shown in a separatewindow also?
    How would I achieve that? Thanks
    "Ramesh" <[email protected]> wrote:
    Is the floating window state available to JSR168 portlets? If it
    is
    where
    to set
    it? Thanks

  • How to debug JSR168 portlets

    Hi,
    Is there a way to debug the jsr168 portlets from Jdeveloper, possibly using remote debugging feature? If yes, appreciate step-by-step instruction on this.
    I have posted a query related to remote debugging here:
    Remote Debugging (Jdev 10.1.3 to AS 10.1.3)
    Thanks,
    Pandian.

    I'm not sure I understand your question. It sounds like you have JSF (faces) components and JSP pages; do you also have JSR168 portlets? The WEB-INF/portlet.xml file should have nothing to do with JSF / JSP pages; it is used only to declare JSR168 portlets.
    To try and answer your question though, if you have JSR168 portlets listed in WEB-INF/portlet.xml, these portlets should show up in the administrative tools when the webapp deploys.

  • How to expose JSR168 portlets from existing JSF webapp?

    Hi all,
    I have a web application with JSF components, and a set of JSP pages that use these components. In WEB-INF, I also have a standard portlet.xml which describes what JSP page to expose for the declared portlet(s).
    Is there any administrative interface in the WebLogic Portal that would automatically detect these portlets as soon as I deploy the webapp, so that I can display them ? My idea is that as soon as this webapp with the portlet.xml is deployed, my portlets should be added to the list of available portlets somewhere. Is that so with the WebLogic portal ? Thanks very much for your feedback.
    P.S: I am using WebLogic Portal 10.0
    Regards,
    Angel

    I'm not sure I understand your question. It sounds like you have JSF (faces) components and JSP pages; do you also have JSR168 portlets? The WEB-INF/portlet.xml file should have nothing to do with JSF / JSP pages; it is used only to declare JSR168 portlets.
    To try and answer your question though, if you have JSR168 portlets listed in WEB-INF/portlet.xml, these portlets should show up in the administrative tools when the webapp deploys.

Maybe you are looking for