Re: Jetspeed portlet lifecycle genesis

[Andrew C. Oliver]

Thanks!

- There's already a setContent() method implemented in the AbstractPortlet
  that can be used to preload content (you still need to deal with the JSP
  case)

I think you're misunderstanding something. preLoad isn't intent on
creating anything that could be construed as "View". The idea is that
data that the view might depend upon can be loaded...

So for instance...

init
preload(RunData) { get stuff from the database }
getContent(RunData) { get the database stuff from the cache and present it via Velocity JSP whatever... }

- the rendering is triggered by the use of JetspeedTool.getContent()

Maybe you can implement your solution by writing a custom PortletSet

-- i'd like to do something that I can donate to jetspeed. I'd rather work collaboratively than create some nasty branch of my own.

implementation that would create the content loading threads before invoking
the controller to lay out the complete page.

Should think about that...

A little custom logic in AbstractPortlet should be enough to make sure that
a background thread can get a lock on the portlet toset its content without
allowing getContent() from being called from the main request thread...

Well it seems to me that getcontent should still do the view and such. preLoad should just be for fetching data, etc.

Thanks for your help! I'll get hacking...this being a hackathon and all!

-Andy

I hope this helps.

--
Rapha�l Luta - [EMAIL PROTECTED]
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/

--
To unsubscribe, e-mail:
For additional commands, e-mail:

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>