I'm not quite sure whether we have already define the architectural
approach for ${Subject} in either way I have some inputs about
${Subject} from AS point of view.
If you go through Tomcat changelog[1] doc you can understand it's vital to
upgrade Tomcat version with AS releases when ever possible. Right now it's
required to do a new Kernal release or maintains a Kernal patch to upgrade
Tomcat version, it would be better if we can find a solid approach for this
from C5.
1.) My first suggestion is it would be great if we can move Tomcat out of
the Kernal but I'm not sure about the feasibility of doing this. WDYT ?
is this something possible ?
2.) If 1st option is not possible it would be nice if we can come up with a
architecture which facilitate to plug/change Tomcat version at
platform/product level. Say Kernal ships with a default Tomcat version
while there is a standard hook to plug custom Tomcat version while building
products. AFAIK other than AS other products can depends on Kernal's Tomcat
version. Only drawback is sometime AS can use one Tomcat version while
rest of the platform use another Tomcat version but compare to maintaining
cost for Kernal patch I'm OK to do this.
3.) Since we are expecting C5 remains for many years it would be better to
use Tomcat8 instead of Tomcat7. Tomcat8 RC packs already there but the
time of C5 1.0 releases happen Tomcat8 GA releases should be there.
Otherwise after 1 or 2 years we have to do a major upgrade.
[1] - http://tomcat.apache.org/tomcat-7.0-doc/changelog.html
[2] - http://tomcat.apache.org/download-80.cgi
Thanks !
--
Sagara Gunathunga
Senior Technical Lead; WSO2, Inc.; http://wso2.com
V.P Apache Web Services; http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ; http://ssagara.blogspot.com
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
