JSR Portlets not showing If the page is forwarded from another page

Hi!

I have an strange problem: I have a web application with a filter, this filter calculates a portal url and forwards to this url. The final forwarded url is standard: /portal/site/siteA/menuitem.****?vgnextoid=****

But if this page has jsr portlets inside, these portlets are not shown!!. The rest of the dynamic portlets and styles are working perfectly. It is very strange. Anybody know what could be the problem?

Thanks to everybody!

Find more posts tagged with

Comments

David_GarcAa_GonzAlez

Anybody could explain me how the jsr portlets are inserted in the page to investigate what could be the problem?

Is there any necessary filter or servlet that is not being executed in the forwarded url but it's being executed in the original url?

Thanks.

Travis_Ebert

Quoted David García González (david_garciagonzalez@ieci.es) on 2011/04/12 13:31:

Hi!

Thanks to everybody!

David,

Are the custom JSR168 portlets or are these the two JSR portlets that come with DPM? If it is a problem with the DPM portlets, you may want to post the question to "Vignette DPM/DSM/Render Forum".

---Travis

David_GarcAa_GonzAlez

No, the problem is with custom JSR portlets, the DPM portlets are showing perfect, but these portlets are portalbeans, not JSR.

I am reviewing the code of a VPS extension named furl, and in this extension a servlet does a forward to a url, so, in practice, it must work.

Then, the installation guide of this extension, explains the following:

You must edit the portal/WEB-INF/web.xml file to modify some filter-mappings.

<filter-mapping>

<filter-name>InitPortalContextFilter</filter-name>

<servlet-name>controller</servlet-name>

<dispatcher>REQUEST</dispatcher>

<dispatcher>INCLUDE</dispatcher>

<dispatcher>FORWARD</dispatcher>

</filter-mapping>

I have done the same, but the portlets are not showing.

It is very strange, what could be the problem?

Thanks to everybody.

David_GarcAa_GonzAlez

I am investigating, in the display page, the content of the portlet is an empty string.

portletWindow.getContent()); //this is an empty string

 <vgn-portal:renderPortlet>          <vgn-portal:onRenderSuccess>           <vgn-portal:insertPortletContent />          </vgn-portal:onRenderSuccess> <vgn-portal:onRenderFailure> </vgn-portal:onRenderFailure> </vgn-portal:renderPortlet>

What could be the problem? It is very very strange.

Travis_Ebert

Quoted David García González (david_garciagonzalez@ieci.es) on 2011/05/09 17:46:

I am investigating, in the display page, the content of the portlet is an empty string.

portletWindow.getContent()); //this is an empty string

 <vgn-portal:renderPortlet>          <vgn-portal:onRenderSuccess>           <vgn-portal:insertPortletContent />          </vgn-portal:onRenderSuccess> <vgn-portal:onRenderFailure> </vgn-portal:onRenderFailure> </vgn-portal:renderPortlet>

What could be the problem? It is very very strange.

David,

Did you try placing the jsr portlet directly on a standard portal page to confirm that it renders correctly that way before trying to test using the render tags?

---Travis

David_GarcAa_GonzAlez

Perhaps there is a problem with Portal 7.4 because I installed Service Pack 2 and now It is working perfectly.

Doy you have this problem registered in any KB or patch?

Floyd Flowers

After reviewing the defect, the fix that seems relevant to what you described as the problem was the following:

EFix_149733_Propagate_Resolver_Loose_Navigation_Context

Update PortalContextImpl, add a check for existence of resolver in the URL and propagating the resolver to other URL's(render, action and resource URL's) being generated.

As listed in the Portal 7.4 known and fixed issues list:

https://knowledge.opentext.com/knowledge/llisapi.dll/fetch/2001/3551166/16714881/16714575/16744990/16679522/Vignette_Portal_7.4_Known_Issues.html?nodeid=16725434&vernum=-2