JSR 286: A Comprehensive article

I have been blogging about the features of JSR 286(Java Portlet Specification 2.0) from the time the expert group(of which i was one of the members representing Sun Microsystems), started publishing the draft specification. Everytime one asks me how a feature in JSR 286 works, i have to point him to one of my blogs. A comprehensive article on all features of JSR 286 was missing.

I have written a comprehensive article that includes all features of JSR 286 with examples. This also includes less talked about ones like wild card in eventing, alias support, Portlet URL listeners, etc..If you see that any feature is missing or if there any corrections to be done, let me know, i will incorporate them. Thanks.

The comprehensive article on JSR 286 is at https://portlet-container.dev.java.net/docs/jsr286.html

Comments:

Very good article. I've been looking around for clear jsr-286 explanation with samples. Nothing so comprehensive and clear as this article.

Congratulations!

Posted by Aniceto Perez on January 05, 2010 at 08:18 AM IST #

Thanks for the kind words.

Posted by Deepak on January 05, 2010 at 08:48 AM IST #

Interesting thing!
This is my first time comment at your blog.
Good recommended website.

Posted by z.l.q on February 23, 2010 at 03:30 AM IST #

Hi.
Your article was one of the best, helping me to set up some sample portlets.
Mainly I am just sending a parameter out of a drop down from one portlet "PORTLET1" to another portlet "PORTLET2" using the eventing. PORTLET2 shall remember it for later action, so I store it in there.
This seems to work, but when I open another browser the values set in the first browser appear here as well after a refresh. My first thought was that every browser session creates (a) portlet instance(s), but when I close the second browser, reset the value and start the second browser again, this one again shows the changed (not the original) parameter.
So my question is: Is one portlet "reused" all the time? And how can I avoid it?

I am using portlet container 2.1 in tomcat 6 using java 1.6

Posted by Winfried on May 28, 2010 at 01:28 PM IST #

Where are you storing the parameter in the PORTLET2? Looks like you are storing it in the session. When you create new browser the session is maintained in the new browser so you see the same value in the new browser. So its better to store the parameter in portlet preference rather than the session.

Posted by Deepak on May 31, 2010 at 05:12 AM IST #

Hi. Thanks for your reply.

I have created a local variable in Portlet2 where I store the value. When I call the portlet from a new opened browser I would expect a new session and a new portlet instance with the default value I set in the portlet...

Posted by Winfried on May 31, 2010 at 09:28 AM IST #

ok..now i understand the issue. The portlet instance will remain the same. There is only one instance of the portlet that is created when the portlet is deployed.

Posted by Deepak on May 31, 2010 at 10:53 AM IST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Deepak Gothe

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today