Hi Sameera, We need to show that this file is specific to web-applications deployed on AS and/or any other servers with webapp-mgt + CRE features right?
So can we name it as "wso2-web.xml" ? This way it is generic across the platform. I agree with RuwanA on the fact that wso2as.xml will be a config file for the AS and will not give a sense that it is only used for web-applications. Examples http://geronimo.apache.org/GMOxDOC30/geronimo-webxml.html http://docs.oracle.com/cd/E26576_01/doc.312/e24929/dd-files.htm#GSDPG00078 https://docs.jboss.org/jbossweb/7.0.x/appdev/jbossweb.html Thanks, On Fri, Jul 3, 2015 at 3:36 PM, Sameera Jayasoma <same...@wso2.com> wrote: > +1 for this. > > How about wso2as.xml? > > Thanks, > Sameera. > > On Thu, Jul 2, 2015 at 7:14 PM, KasunG Gajasinghe <kas...@wso2.com> wrote: > >> *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 >> >> >> > > > > -- > Sameera Jayasoma, > Software Architect, > > WSO2, Inc. (http://wso2.com) > email: same...@wso2.com > blog: http://blog.sameera.org > twitter: https://twitter.com/sameerajayasoma > flickr: http://www.flickr.com/photos/sameera-jayasoma/collections > Mobile: 0094776364456 > > Lean . Enterprise . Middleware > > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Kishanthan Thangarajah* Associate Technical Lead, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>* Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>*
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
