Why not just call a method that saves the data when you need to save it and returns the data

It you really want it as a service, why not just make it a webapp or Web Service that accepts requests to save data and responds to requests to get it back later.

Alternatively, you could just store the data in the users session context and retrieve it whenever you want and have it disappear when the user's session dies.

Don't forget that the portal is serving many people at once and just because 1 user is on page 1 does not mean that there aren't a hundred other people on page 3. Your portlet serves all these people and when it is not processing an actual request it is gone.

You need to either use the session context or use a service that is smart enough not to mix up who told him what.

Ron

David Just wrote:
This portlet application service will be responsible for providing data
to a custom Jetspeed level service which will present status at the
decorator level. The portlets that it's collecting data for might be on say page 3 but the user is looking at page 1.
It should be created when the user logs into Jetspeed and be destroyed
when they log out.
I could define this service at the Jetspeed level also, but would prefer
if at all possible to define it in the portlet application level.





David Just l Software Engineer l Vision Solutions l +1 (507) 529-5939 l 
[email protected]
The contents of this e-mail (and any attachments) are privileged and 
confidential. Unauthorized use is strictly prohibited.
-----Original Message-----
From: Ron Wheeler [mailto:[email protected]] Sent: Wednesday, September 23, 2009 11:59 AM
To: Jetspeed Users List
Subject: Re: Create a Portal Application session on login without a
portlet visible

What is it going to do while the user is logged in and how will it know when the user has moved on?

What processing will it be doing while the user has gone to get a sandwich? Or a nap?

Are you just trying to keep track of information for the duration of the

session?

Ron

David Just wrote:
Is it possible to have Jetspeed create a portal application session
scoped object (visible across all portlets in an application) that is
created when the user logs in to Jetspeed without having any of the
portlet application's portlets being visible?

I need a portlet application service (defined in the portlet war) to
start as soon as the user logs into Jetspeed. The caveat is that none
of
the portlets from this application will be visible on the first page
of
the portal.  Has anybody done something like this before?  Is it
possible without putting the service at the Jetspeed level?

Thanks.



David Just l Software Engineer l Vision Solutions l +1 (507) 529-5939
l [email protected]
The contents of this e-mail (and any attachments) are privileged and
confidential. Unauthorized use is strictly prohibited.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to