Hello All!
This is a more philisophical thought train on the overall design of the
Portlet API:
I think that one of the weaknesses of the Jetspeed implementation is that
you have all these different portlet types depending on the type of content
that the portlet is actually dealing with. (And its not even dependant
upon the final information the portlet is rendering) [Example: Cocoon
portlet vs RSS portlet, vs JSP portlet etc. etc.]
Instead of throwing all these portlet types for every content type, why
don't we have a processing pipeline that would take care of the basic
download / transformation, etc. We then would have to set up the generic
portlet API to be independent of the actual data returned, but have
attributes to allow the portlet container to figure out what it needs to do
with the data returned.
Any thoughts on this? I'll be more than happy to start coming up with some
concrete examples, but I'd really like to know if people are interested in
exploring this possibility first.
Thanks,
-Mike
--
--------------------------------------------------------------
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]
