*Overview* Currently, there are several AS specific configuration options that are available for webapp developers when deploying webapps in AS. A set of identified configurations we have are as follows.
1. Configure the ClassLoader Runtime Environment and Classloading for web apps (such as Carbon/CXF/Tomcat/...) 2. Mark a JAX-RS webapp to be published as a Managed API for API-Everywhere story. 3. Enable Single Sign On support for webapps 4. Webapp SaaS configurations. 5. Enable WebApp Statistics publishing to DAS/BAM *Why?* Right now, we are using different mechanisms to configure these. Mostly, we ask webapp developers to put the configuration options as a context-param in the web.xml. We also have a custom AS specific configuration file called webapp-classloaading.xml to configure classloading runtimes. Using web.xml for this purpose is not a clean approach since web.xml it should only contain configurations that are portable across different application servers. For this purpose, Tomcat uses a custom context.xml to put Tomcat specific configurations. JBoss has jboss-web.xml. WebLogic has weblogic.xml, and so on.. *How?* The idea here is to generalize the current webapp-classloading.xml we already have into a configuration file where all the webapp related WSO2 AS configurations can be put. We could name this file as wso2as-web.xml or wso2as-application.xml. This is targeted for AS6 for immediate use with API-Everywhere feature. The implementation is fairly simple, and may be carried out as a fast-track training project. WDYT? Thanks, KasunG -- *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. email: kasung AT spamfree wso2.com linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
