[EMAIL PROTECTED] 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to