You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Todd Kuebler <tk...@cisco.com> on 2003/10/24 00:12:42 UTC
Jetspeed2 and MVC idea
I continue to believe that the Portlet idea in practice should simply
implement the controller paradigm of the MVC instead of being some class
that needs extending by the typical web developer just to create a html
fragment. Just like servlets are best served by something like Struts, I
believe portlets are best served by something like the MVCPorlet
idea. There should be a config file that ties actions/events to views,
which the controller (portlet) uses to render it's fragment.
Maybe the J2 core doesn't deal with that, only providing a container for
JSR 168, but as a portal implementation it will have to deal with this idea
sooner or later to reach maturity imho since web applications are almost
universally seeking the MVC paradigm going forward.
Thoughts?
%regards -tk
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: Jetspeed2 and MVC idea
Posted by David Le Strat <dl...@yahoo.com>.
Hello Todd,
Here is my rationale. Jetspeed 2 is a portal
framework, and how you do MVC in your portlets does
not really have much to do with the portal framework.
With JSR168, your portlets can be deployed to any
other portal engine, so why would you want to tie the
portlet implementation to the portal framework? If
you create a calendar portlet, wouldn't it make more
sense to be able to deploy it independently of the
portal engine?
For some Jetspeed specific portlets designed to
provide portal management support, you will have to
consume Jetspeed services, in any other case, I am not
sure why you would want to hook your portlets to the
Jetspeed engine.
Regards,
David.
--- Todd Kuebler <tk...@cisco.com> wrote:
>
> Wow. So you are saying that if you want to do MVC
> style development that
> you _should not_ use Jetspeed 2? Ok.
>
>
> -tk
>
>
> At 08:43 PM 10/23/2003 -0700, David Le Strat wrote:
> >Todd,
> >
> >What about using Struts or JSF as your Portlet MVC
> >model? Looks like the Struts team is working with a
> >Struts version compatible with JSR168 and the final
> >release of JSF should be compatible as well.
> >
> >Regards,
> >
> >David.
> >
> >--- Todd Kuebler <tk...@cisco.com> wrote:
> > >
> > > I continue to believe that the Portlet idea in
> > > practice should simply
> > > implement the controller paradigm of the MVC
> instead
> > > of being some class
> > > that needs extending by the typical web
> developer
> > > just to create a html
> > > fragment. Just like servlets are best served by
> > > something like Struts, I
> > > believe portlets are best served by something
> like
> > > the MVCPorlet
> > > idea. There should be a config file that ties
> > > actions/events to views,
> > > which the controller (portlet) uses to render
> it's
> > > fragment.
> > >
> > > Maybe the J2 core doesn't deal with that, only
> > > providing a container for
> > > JSR 168, but as a portal implementation it will
> have
> > > to deal with this idea
> > > sooner or later to reach maturity imho since web
> > > applications are almost
> > > universally seeking the MVC paradigm going
> forward.
> > >
> > > Thoughts?
> > >
> > >
> > > %regards -tk
> > >
> > >
> > >
>
>---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > > jetspeed-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail:
> > > jetspeed-dev-help@jakarta.apache.org
> > >
> >
> >
> >__________________________________
> >Do you Yahoo!?
> >The New Yahoo! Shopping - with improved product
> search
> >http://shopping.yahoo.com
> >
>
>---------------------------------------------------------------------
> >To unsubscribe, e-mail:
> jetspeed-dev-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail:
> jetspeed-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> jetspeed-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: Jetspeed2 and MVC idea
Posted by Todd Kuebler <tk...@cisco.com>.
Wow. So you are saying that if you want to do MVC style development that
you _should not_ use Jetspeed 2? Ok.
-tk
At 08:43 PM 10/23/2003 -0700, David Le Strat wrote:
>Todd,
>
>What about using Struts or JSF as your Portlet MVC
>model? Looks like the Struts team is working with a
>Struts version compatible with JSR168 and the final
>release of JSF should be compatible as well.
>
>Regards,
>
>David.
>
>--- Todd Kuebler <tk...@cisco.com> wrote:
> >
> > I continue to believe that the Portlet idea in
> > practice should simply
> > implement the controller paradigm of the MVC instead
> > of being some class
> > that needs extending by the typical web developer
> > just to create a html
> > fragment. Just like servlets are best served by
> > something like Struts, I
> > believe portlets are best served by something like
> > the MVCPorlet
> > idea. There should be a config file that ties
> > actions/events to views,
> > which the controller (portlet) uses to render it's
> > fragment.
> >
> > Maybe the J2 core doesn't deal with that, only
> > providing a container for
> > JSR 168, but as a portal implementation it will have
> > to deal with this idea
> > sooner or later to reach maturity imho since web
> > applications are almost
> > universally seeking the MVC paradigm going forward.
> >
> > Thoughts?
> >
> >
> > %regards -tk
> >
> >
> >
>---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > jetspeed-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> > jetspeed-dev-help@jakarta.apache.org
> >
>
>
>__________________________________
>Do you Yahoo!?
>The New Yahoo! Shopping - with improved product search
>http://shopping.yahoo.com
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: Jetspeed2 and MVC idea
Posted by David Le Strat <dl...@yahoo.com>.
Todd,
What about using Struts or JSF as your Portlet MVC
model? Looks like the Struts team is working with a
Struts version compatible with JSR168 and the final
release of JSF should be compatible as well.
Regards,
David.
--- Todd Kuebler <tk...@cisco.com> wrote:
>
> I continue to believe that the Portlet idea in
> practice should simply
> implement the controller paradigm of the MVC instead
> of being some class
> that needs extending by the typical web developer
> just to create a html
> fragment. Just like servlets are best served by
> something like Struts, I
> believe portlets are best served by something like
> the MVCPorlet
> idea. There should be a config file that ties
> actions/events to views,
> which the controller (portlet) uses to render it's
> fragment.
>
> Maybe the J2 core doesn't deal with that, only
> providing a container for
> JSR 168, but as a portal implementation it will have
> to deal with this idea
> sooner or later to reach maturity imho since web
> applications are almost
> universally seeking the MVC paradigm going forward.
>
> Thoughts?
>
>
> %regards -tk
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> jetspeed-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org