You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Mats Forssblad <fr...@algonet.se> on 2001/09/20 15:31:06 UTC
Source for portlet api?
Where do I find the source for
org.apache.jetspeed.portlet.PortletAdapter and
org.apache.jetspeed.portlets.AbstractPorlet? I have javadoc for the api,
and I'm using the compiled classes with IBM Portal Server 1.2, but the
source for this and other classes seems not to be present in the
Jetspeed source branch for the new api.
Also I find the widespread use of the package com.ibm.wps.portlets - in
IBM tutorials and samples - disturbing. What's the policy on this? I'm
really scared to touch them, but if it's just a naming issue, and it's
all going to end up as org.apache.jetspeed-stuff, I guess they can be
used.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: Source for portlet api?
Posted by "Scott A. Roehrig" <sa...@hotmail.com>.
Well taken...
I think that as the release of jetspeed nears as well, the documentation on
the portletAPI as used in jetspeed will become clearer. WPS leverages a
large portion of the code and IBM has reverse contributed a good amount of
the API.
Scott
----- Original Message -----
From: "Mats Forssblad" <fr...@algonet.se>
To: <je...@jakarta.apache.org>
Sent: Friday, September 21, 2001 6:35 AM
Subject: Re: Source for portlet api?
>
>
> "Scott A. Roehrig" wrote:
> >
> > IBM has returned portions of the WPS code to the Jetspeed project. Not
all
> > of WPS is open source however.
> >
> > Scott
>
> Yes, and this is expected. But core portlet API classes in the
> org.apache.jetspeed.* packages should be available. Discrepancies
> between the API as shipped by IBM and what we find in the jetspeed
> source are also expected with a developing api. But an indication of the
> status of an important class like PortletAdapter would be...nice.
>
> Finally, of course you'd expect IBM to make some useful interfaces and
> abstract classes for producing portlets, and they would of course not be
> open source. But if you look closely at the com.ibm.wps.portlets package
> you'll find some things that really might just as well be part of the
> api. An important example is the IBM PortletController and related
> interfaces. They are extremely similar to the jetspeed PortletAdapter.
> They add some true value by the method
> void doActionEven ( ActionEvent event )
> while they 'retain' methods that are already in the jetspeed core api,
> like doView(), doEdit(), doHelp().
> It's no big deal to stick to PortletAdapter and add your own interface
> for handling an ActionEvent, but I guess right now hundreds of portlets
> are shipped to market that are dependent - for no really good reason -
> on PortletController, and thus not portable.
>
> > ----- Original Message -----
> > From: "Mats Forssblad" <fr...@algonet.se>
> > To: <je...@jakarta.apache.org>
> > Sent: Thursday, September 20, 2001 9:31 AM
> > Subject: Source for portlet api?
> >
> > > Where do I find the source for
> > > org.apache.jetspeed.portlet.PortletAdapter and
> > > org.apache.jetspeed.portlets.AbstractPorlet? I have javadoc for the
api,
> > > and I'm using the compiled classes with IBM Portal Server 1.2, but the
> > > source for this and other classes seems not to be present in the
> > > Jetspeed source branch for the new api.
> > > Also I find the widespread use of the package com.ibm.wps.portlets -
in
> > > IBM tutorials and samples - disturbing. What's the policy on this? I'm
> > > really scared to touch them, but if it's just a naming issue, and it's
> > > all going to end up as org.apache.jetspeed-stuff, I guess they can be
> > > used.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: Source for portlet api?
Posted by Mats Forssblad <fr...@algonet.se>.
"Scott A. Roehrig" wrote:
>
> IBM has returned portions of the WPS code to the Jetspeed project. Not all
> of WPS is open source however.
>
> Scott
Yes, and this is expected. But core portlet API classes in the
org.apache.jetspeed.* packages should be available. Discrepancies
between the API as shipped by IBM and what we find in the jetspeed
source are also expected with a developing api. But an indication of the
status of an important class like PortletAdapter would be...nice.
Finally, of course you'd expect IBM to make some useful interfaces and
abstract classes for producing portlets, and they would of course not be
open source. But if you look closely at the com.ibm.wps.portlets package
you'll find some things that really might just as well be part of the
api. An important example is the IBM PortletController and related
interfaces. They are extremely similar to the jetspeed PortletAdapter.
They add some true value by the method
void doActionEven ( ActionEvent event )
while they 'retain' methods that are already in the jetspeed core api,
like doView(), doEdit(), doHelp().
It's no big deal to stick to PortletAdapter and add your own interface
for handling an ActionEvent, but I guess right now hundreds of portlets
are shipped to market that are dependent - for no really good reason -
on PortletController, and thus not portable.
> ----- Original Message -----
> From: "Mats Forssblad" <fr...@algonet.se>
> To: <je...@jakarta.apache.org>
> Sent: Thursday, September 20, 2001 9:31 AM
> Subject: Source for portlet api?
>
> > Where do I find the source for
> > org.apache.jetspeed.portlet.PortletAdapter and
> > org.apache.jetspeed.portlets.AbstractPorlet? I have javadoc for the api,
> > and I'm using the compiled classes with IBM Portal Server 1.2, but the
> > source for this and other classes seems not to be present in the
> > Jetspeed source branch for the new api.
> > Also I find the widespread use of the package com.ibm.wps.portlets - in
> > IBM tutorials and samples - disturbing. What's the policy on this? I'm
> > really scared to touch them, but if it's just a naming issue, and it's
> > all going to end up as org.apache.jetspeed-stuff, I guess they can be
> > used.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: Source for portlet api?
Posted by "Scott A. Roehrig" <sa...@hotmail.com>.
IBM has returned portions of the WPS code to the Jetspeed project. Not all
of WPS is open source however.
Scott
----- Original Message -----
From: "Mats Forssblad" <fr...@algonet.se>
To: <je...@jakarta.apache.org>
Sent: Thursday, September 20, 2001 9:31 AM
Subject: Source for portlet api?
> Where do I find the source for
> org.apache.jetspeed.portlet.PortletAdapter and
> org.apache.jetspeed.portlets.AbstractPorlet? I have javadoc for the api,
> and I'm using the compiled classes with IBM Portal Server 1.2, but the
> source for this and other classes seems not to be present in the
> Jetspeed source branch for the new api.
> Also I find the widespread use of the package com.ibm.wps.portlets - in
> IBM tutorials and samples - disturbing. What's the policy on this? I'm
> really scared to touch them, but if it's just a naming issue, and it's
> all going to end up as org.apache.jetspeed-stuff, I guess they can be
> used.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org