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 Ivan Mikushin <iv...@vismech.ru> on 2001/05/07 09:54:50 UTC
want to join
Hi!
I'm completely new to the Apache Jakerta Jetspeed project, so excuse me
if I'm writing to a wrong place :)
I have viewed the project's web site and want to participate.
Particularly interested in generic Portlet API and portal implementation
over Cocoon 2.
I have some questions:
1) Is there a mail archive anywhere so that I could read it the previous
discussion on the topics I'm interested in?
2) Any clue to start work ...
Ivan.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: JSR
Posted by Jon Stevens <jo...@latchkey.com>.
on 5/7/01 5:15 AM, "ingo schuster" <in...@web.de> wrote:
> At 13:07 05/07/01, Santiago Gala wrote:
>> Ivan Mikushin wrote:
>>
>>> How about submitting a JSR on defining a generic Portlet API to Java
>>> Community Process?
>
> As far as I now, Jon didn't like this idea when we spoke about it on the
> ApacheCon in London (or was it Stefano?). The reason was, that once you
> have a javax.portlet package, you are handing over the control to Sun...
Neither Stefano nor I like the idea. The JCP sucks balls. No matter how hard
Sun Execs try to say that the JCP is not Sun owned, the reality of it is
that it is.
> A standard however is a very good thing (for vendors as well as for
> customers) and obviousely what we at IBM would like to have.
These days, standards are simply marketing. Whomever has the most marketing
$ wins. That is why JSP is so popular and other *better* technologies are
losing. Sun doesn't advertise anything but what they come up with,
regardless of whether it sucks or not.
So, if you (IBM) publishes a Portlet Spec on the Jetspeed website and then
market the hell out of it and support it properly with a reference
implementation that is OSS (ie: Jetspeed), it will win.
-jon
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: JSR
Posted by ingo schuster <in...@web.de>.
At 13:07 05/07/01, Santiago Gala wrote:
>Ivan Mikushin wrote:
>
>>How about submitting a JSR on defining a generic Portlet API to Java
>>Community Process?
As far as I now, Jon didn't like this idea when we spoke about it on the
ApacheCon in London (or was it Stefano?). The reason was, that once you
have a javax.portlet package, you are handing over the control to Sun...
A standard however is a very good thing (for vendors as well as for
customers) and obviousely what we at IBM would like to have.
ingo.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: JSR
Posted by Santiago Gala <sg...@hisitech.com>.
Ivan Mikushin wrote:
> How about submitting a JSR on defining a generic Portlet API to Java
> Community Process?
>
I don't know other people's agenda (specifically the IBM team).
My opinion is that once we have a default implementation running, and
some other vendor in the wagon it would be the moment.
My priority currently would be to get other portal/application server
vendors join the discussion, and have a Portlet API that is convenient
and usable for the major portlet engines.
The ideal scenario is one where you can buy portal tools from several vendors,
and have also an open source reference implementation evolving together.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
JSR
Posted by Ivan Mikushin <iv...@vismech.ru>.
How about submitting a JSR on defining a generic Portlet API to Java
Community Process?
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: want to join
Posted by Santiago Gala <sg...@hisitech.com>.
raphael.luta@networks.groupvu.com wrote:
> Ivan Mikushin wrote:
>
>> Hi!
>>
>> I'm completely new to the Apache Jakerta Jetspeed project, so excuse me
>> if I'm writing to a wrong place :)
>>
>> I have viewed the project's web site and want to participate.
>> Particularly interested in generic Portlet API and portal implementation
>> over Cocoon 2.
>>
>> I have some questions:
>> 1) Is there a mail archive anywhere so that I could read it the previous
>> discussion on the topics I'm interested in?
>
>
> I don't know the URL by heart but I'm sure somebody can give you a link to the
> archive...
I have sent a mail to marc.theaimsgroup.com, because they only have the
old list archived. This archive is much more "searchable" than the other
ones listed, that are really a digest.
> Cocoon 2 implementation has not started yet nor are there any definite plans
> on how to proceed. Real work on this implementation will start once the new
> portlet API and the Jetspeed 1.3 engine are stabilized...
>
In the new Portlet API we have left hook that will enable interoperation
of stream based (JSP, Velocity, ...) portlets with SAX2 based Portlets.
> About the new Portlet API, you can find the API javadocs in the /proposals
> directory of Jetspeed CVS and the initial implementation of this API has
> been committed a few days ago on a specific CVS branch ('portlet_api').
>
>
>> 2) Any clue to start work ...
>>
>
>
> 1. See http://jakarta.apache.org/site/getinvolved.html
> 2. Grab Jetspeed CVS following the instructions of the Jakarta site
> 3. Send the patches and/or start new functionality discussion on the jetspeed-dev
> lists and implement them :)
>
> At first, your patches will be reviewed and committed by existing committers but if
> you're willing to maintain a specific component/functionality you may quite
> easily get CVS write access...
>
> Welcome in the party :)
>
Ditto!
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: want to join
Posted by ra...@networks.groupvu.com.
Ivan Mikushin wrote:
>
> Hi!
>
> I'm completely new to the Apache Jakerta Jetspeed project, so excuse me
> if I'm writing to a wrong place :)
>
> I have viewed the project's web site and want to participate.
> Particularly interested in generic Portlet API and portal implementation
> over Cocoon 2.
>
> I have some questions:
> 1) Is there a mail archive anywhere so that I could read it the previous
> discussion on the topics I'm interested in?
I don't know the URL by heart but I'm sure somebody can give you a link to the
archive...
Cocoon 2 implementation has not started yet nor are there any definite plans
on how to proceed. Real work on this implementation will start once the new
portlet API and the Jetspeed 1.3 engine are stabilized...
About the new Portlet API, you can find the API javadocs in the /proposals
directory of Jetspeed CVS and the initial implementation of this API has
been committed a few days ago on a specific CVS branch ('portlet_api').
> 2) Any clue to start work ...
>
1. See http://jakarta.apache.org/site/getinvolved.html
2. Grab Jetspeed CVS following the instructions of the Jakarta site
3. Send the patches and/or start new functionality discussion on the jetspeed-dev
lists and implement them :)
At first, your patches will be reviewed and committed by existing committers but if
you're willing to maintain a specific component/functionality you may quite
easily get CVS write access...
Welcome in the party :)
--
Raphaël Luta - luta.raphael@networks.vivendi.net
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org