In AS6 we don't try to embed or try to create our own containers, instead we are providing 2 types of extensions to Tomcat users.
1.) Extensions to enable WSO2 platform features to Tomcat ( e.g - security, monitoring etc.) 2.) Value added features for Tomcat ( e.g - Classloading runtimes, API-Everywhere etc.) TomEE WP is itself an extended Tomcat server, if we can test and ensure above WSO2 extensions for Tomcat are run on TomEE without any issue, do we have to do anything additional ? For me this is more or less testing effort, as an example when we develop a SSO Valve for IS, it should work on both Tomcat and TomEE. Like we provide WSO2 pre-installed Tomcat distribution we can provide WSO2 pre-installed TomEE distribution as well, but that is just a usability improvement only users can download pre-installed distribution or they can install WSO2 extensions top of any compatible Apache TomEE version. Thanks ! On Wed, Feb 10, 2016 at 11:31 AM, Manoj Kumara <[email protected]> wrote: > 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 > > > -- Sagara Gunathunga Architect; 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
