Hi All, On Carbon 4.x.x era to support Web profiles we have implemented a ServerListener on top of Carbonized Tomcat. Further when introducing Tomcat based features to Carbon servers we had to do lot of work in order to get the support and this added overhead on maintaining as well.
On future releases we are planing to use vanilla Tomcat servers with added extensions to support additional features required by Carbon servers (ex: SSO, Class loading, analytics etc.) to simplify the internals and to be align with the latest Tomcat releases. I'm currently working on $Subject task and when it comes to Web Profile support we can choose few approaches as I can see, 1. Include TomEE based libs on Tomcat server to get the WebProfile support (IMO approach is not suitable as that is what TomEE project is trying to address the overhead of adding customized features on top of Tomcat) 2. Use TomEE Jax-RS distribution instead of Tomcat such that with single distribution we'll have features of both Tomcat and TomEE 3. Create two flavours of WSO2 AS 6.0.0 one with Tomcat and another with TomEE Jax-RS. So depending on the requirement customers can choose which distribution to use. As per my understanding I prefer the 3nd approach as that way use can choose which variance he want depending on the requirements. Appreciate your feedback on this. Regards, Manoj
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
