> Seems like you invested alot of time and work into this problem.
> I assume your AdvancedFileServer extends FileServerPortlet.
It extends FileWatchPortlet.
> Are you doing the url rewrites etc on the fly during
> getContent() or in a
> preprocessing stage, outside of the portal? Sounds like its
> happening on the
> fly, which leads me to think that amazon is running in full-screen
> application mode.
It does it on the fly and it runs not in application mode - amazon, yahoo,
our intranet site, all that runs as portlet being part of a personalized
portal site at the same time - otherwise we wouldn't have that a big issue
with name clashes/base URLs and so on. It works all quite well, but still we
have problems, e.g. when navigating more than one portlet. When you do that,
you lose your navigational path when you navigate another portlet - in the
portlet you navigated first you see the orginal page defined in the
registry. That's due to the fact, that a portlet has no consciousness. The
redirection through the AdvancedFileServer is done using a request parameter
- for Jetspeed the displayed content is still the page defined inside the
registry. That might be another issue for the porlet API: User/Portlet
specific consciousness per session.
> Do you have any rough ideas of how the AdvancedFileServer
> would work in the
> future portlet api?
I just joined your discussion and need some time to catch up with you guys
on the portlet API (what you have talked about/settled on in the past) -
right now our project doesn't give me much time, so I just can contribute
problems and our part-solutions (see also RE: Portlet API - Portlet
communication and portlet chaining/pipelining).
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
