[wsas-java-dev] Moving to Jetty 6.1.1

[saminda abeyruwan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jetty community also advices uses to program with servlets instead of
handlers. As Azeez has said, if WSAS could completely moved from
handlers to servlets, it will simplify many things.

Thank you

Saminda

Afkham Azeez wrote:
> The reason I mentioned the Jetty plus issue was, we were considering
> using only servlets instead of servlets+jetty handlers(This is what we
> have now), which simplifies many things. In order to use servlets, you
> need Jetty plus.
> 
> -- azeez
> 
> Afkham Azeez wrote:
>> +1 to moving to Jetty 6.1.1.
>>
>> We may also need to take the following issues in Jetty 6.1.1 into
>> consideration:
>>
>> 1) AJP incompatibility with latest mod_proxy
>> 2) java 1.5 method in jetty plus
>>
>> --Azeez
>>
>> saminda abeyruwan wrote:
>>> Hi all,
>>>
>>> Jetty has released 6.1.1 version, and it has better Session Management
>>> facilities and improvements. Thus, without changing the current code
>>> base of WSAS, it can be moved to Jetty 6.1.1. WSAS currently uses Jetty
>>> 6.0.1 version.
>>>
>>> Thank you
>>>
>>> Saminda
>> _______________________________________________
>> Wsas-java-dev mailing list
>> Wsas-java-dev at wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Wsas-java-dev mailing list
>> Wsas-java-dev at wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFsKDVYmklbLuW6wYRAo2QAKCJQ6yF6q2nvwkK/Ss/o/cbhEf9ygCgjXsK
6azv5PM4yZr6gOFBNYvY2ao=
=Hdts
-----END PGP SIGNATURE-----