Howard Lewis Ship wrote:
This is more of a general portlet question.
I have a portlet that wants to display a dynamic image (*) as part of
its output.
In a traditional HTML application, I would build a URL to a servlet
and the servlet would build the image and send a bytestream to the
client.
I want to do something similar with a portlet.
Is it possible to build such a URL? I want to build a render URL and
have the handler for that URL build and return the image bytestream.
With portlets, the URL always goes back to the portal.
The portal then asks your portlet to contribute its portion of the
content to the full bytestream.
Your portlet could do the exact same thing as the servlet: generate the
image bytestream within the context of the entire portlet stream. It can
generate the content itself or dispatch to your servlet (internally) to
retrieve the content.
If I understand, I think you are looking to still go thru the portal to
get your content, but for the URL to specify the content of just one
portlet. (I could be wrong) I don't know of a portable solution to do
that. I was thinking you could handle a special portlet mode, or max
window state, but its still up to the portal to decide on the layout
around the portlet.
As a non-portable solution: Jetspeed can specifically be told to
generate the content of a given portlet using the portlet pipeline,
specified in the URL
/jetspeed/portal?pipeline=portlet-pipelineentity={portletentity}
I've also done similar solutions using a portlet page holding one
portlet and no layout or decorator
(*) This is really about Tapestry Portlet support. The dynamic image
data is really going to be images packaged in JARs that need to be
exposed to the client. Tapestry includes an engine service that will
access such things. I'm trying to see if I can avoid using a Tapestry
servlet in anotherwise Tapestry portlet application.
--
David Sean Taylor
Bluesunrise Software
[EMAIL PROTECTED]
[office] +01 707 773-4646
[mobile] +01 707 529 9194
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
