geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Wilkins <gr...@mortbay.com>
Subject Re: heads-up: Servlet-2.5 & jetty 6 branch?
Date Mon, 06 Mar 2006 22:07:48 GMT
Bill Dudney wrote:
> Hi Greg,
> 
> Seems I jumped the gun and did not write up a JIRA for this before 
> getting started. I've got most of the Servlet 2.5 and JSP 2.1 api's 
> typed in. I want to take one more pass over them to make sure I have 
> all the correct exceptions on the methods and other details like that.

No problems - it's good that the job is done.

Yell when they are checked in and I'll proof read them and 
give them a run against Jetty 6.

Also have a look at http://wiki.apache.org/incubator/GrandCentralProposal
a proposal (work in progress) to move the APIs to a top level project.

cheers


> I'll be submitting a patch early next week that has both of these api 
> projects.
> 
> Sorry for not entering a jira issue on it earlier....
> 
> http://issues.apache.org/jira/browse/GERONIMO-1686
> 
> TTFN,
> 
> Bill Dudney
> MyFaces - myfaces.apache.org
> 
> 
> On Mar 2, 2006, at 12:55 AM, Greg Wilkins wrote:
> 
>>
>> All,
>>
>> I'm tuning back into G after zoning out for a while....
>> I'd like to started work on the jetty6 integration to
>> provide servlet 2.5
>>
>> The goals of the jetty 6 integration will be:
>>  + 2.5 servlet API.
>>  + annotation support
>>  + Simplify integration using Jetty 6 interceptor friendly  architecture.
>>  + Use geronimo threadpool
>>  + Use Session API ( or iteration of that (see comments posted 
>> earlier)) as
>>    basis of session manager
>>  + Experiment with WADI and clustering integration
>>  + Better JACC specific security handler (perhaps to be back ported 
>> to Jetty)
>>  + Potentially use common server socket factories and eventually  SSL
>> Engine
>>    factories
>>
>> For this I'm going to created a branch geronimo/sandbox/servlet-2.5
>> and add geronimo-spec-servlet to geronimo/spec/branches/JEE5
>>
>> I'm going for a full branch:
>>
>>  + because I actually want to see how hard it will be to use
>>    svn to maintain a parallel dev branch.
>>  + I want some stability
>>  + I think there will be some moderately global changes that
>>    may affect multiple modules.
>>  + The branch will be a good place for a 2.5 tomcat module
>>    to be developed at the same time.
>>
>> everybody OK with this?
>> I'd like to start this soonish, although I'm tempted to wait
>> for maven2 to be working.
>>
>> cheers
>>
>>
>>
>>
> 
> 


Mime
View raw message