Neeme Praks wrote:
<snip>
> > Hmm.. What's the need for that ? If you only have 1 portlet
> > the use of a controller
> > doesn't make much sense. If you plan ton pass several portlet
> > parameters, you're
> > actually recreating a PSML fragment, there should be a more
> > compact (but maybe less readable) notation.
>
> how about assigning names also to portletsets and referencing them also
> from the URL?
> This would also eliminate the need for "applications"?
Hmm.. that is interesting. This may fit into my new PSML proposal (with
profiles). We could have named sets and profiles. So 'applications'
would be a PortletSet and the ApplicationsPortlet would essentially be a
PortletSetPortlet that would just show you how to navigate a set of
Portlets... but essentially this would just be a NavigationController.
> > In all case, I'd think we should start using "namespaced"
> > parameters to avoid
> > conflict with other sets of parameters:
> >
> > ie, instead of portlet, use jetspeed-portlet
> > and instead of portlet-controller, use jetspeed-controller
> >
> > or maybe if we feel lazy, "jet-portlet" and "jet-controller"
>
> how about making it configurable... but by default they should be
> namespaced, I agree.
I am +1 for namespacing. But I think it is safe to say that within
Turbine/Jetspeed... as long as we plant the flag in the soil.. that we
can use 'portlet', 'portlet-controller', etc within the Engine.
Kevin
--
Kevin A Burton (e-mail: [EMAIL PROTECTED], UIN: 73488596, ZKey:
burtonator)
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
To fight and conquer in all your battles is not supreme excellence;
supreme
excellence consists in breaking the enemy's resistance without fighting.
- Sun Tzu, 300 B.C.
--
--------------------------------------------------------------
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]
