• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

How can I tell if my portlet is JSR 168 or 286 compatible?

 
Tony Ennis
Ranch Hand
Posts: 86
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Our corporate portal server only supports JSR 168. My application works under jetspeed-2 on my local machine but not the corporate portal. The first thing I need to be sure of is that I didn't give them a JSR 286 portlet.

How can I check?
 
Ashish Sarin
author
Ranch Hand
Posts: 444
10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Tony,

I think the simplest way to check this would be to do the following:
1. If you are using JSP as the view technology then check that the portlet tag library does not point to the Portlet 2.0 URI:


If you see the above taglib declaration then change value of uri attribute to http://java.sun.com/portlet instead to make your portlet compatible with Portlet 1.0.

2. If you are using @ProcessAction or @RenderMode annotations in your code then it means you are using Portlet 2.0 features. Annotations were introduced in Portlet 2.0. Remove the annotations and re-write the methods as doView and processAction methods to make it Portlet 1.0 compatible.

Just curious, when you deploy your portlet in the corporate portal is the portlet successfully registered with the portal server ?

regards
ashish
Author: Portlets in Action
 
Tony Ennis
Ranch Hand
Posts: 86
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I believe the portlet is registered correctly. I am a contractor here - as such I can't really touch anything. I have never seen the portal nor do I have access to it. The portlet server is Websphere+peoplesoft I think. Someone else installed the portlet I coded. It sort of runs which I would not expect if it were noncompliant. The portlet runs fine on my machine using Jetspeed2.

Welcome to hell.
 
Ashish Sarin
author
Ranch Hand
Posts: 444
10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Now I am helpless, just like you

My last suggestion would be to check declaration of portlet-app element in your portlet deployment descriptor. If you see something like this then it may not work on JSR 168 complaint portlet container.


regards
ashish
Author: Portlets in Action
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic