On Fri, Sep 11, 2015 at 3:33 PM, Harshan Liyanage <[email protected]> wrote:
> adding @architecture. > > Harshan Liyanage > Software Engineer > Mobile: *+94724423048* > Email: [email protected] > Blog : http://harshanliyanage.blogspot.com/ > *WSO2, Inc. :** wso2.com <http://wso2.com/>* > lean.enterprise.middleware. > > On Fri, Sep 11, 2015 at 3:26 PM, Harshan Liyanage <[email protected]> > wrote: > >> Hi all, >> >> We have a requirement to read some configuration parameters when a >> web-app gets deployed to initiate the dynamic-client authentication >> process. We have both JAVA webapps and jaggery webapps. Currently I'm using >> a LifecycleListener and reading the required context-params using the >> ServletContext. This approach works well for JAVA webapps. >> >> But this method can not be used for jaggery webapps as the existing >> implementation of TomcatJaggeryWebappsDeployer [1] does not support >> defining and using the context-parameters in jaggery-conf file (it only >> supports *displayName* and *logLevel *parameters). However as the >> jaggery.conf file is designed to serve the same purpose as the web.xml file >> of a web-app, I think its necessary to have the context-parameter support >> in jaggery.conf file. >> >> Is it ok to have context-params defined in jaggery.conf file or are there >> any better solution for this issue? Please share your opinions. >> > IMO, what's proposed is what needs to be done. In other words, each webapp, irrespective of the fact that it is a regular webapp or jaggery app, has to have a descriptor of some sort, which is used to configure the runtime behaviour of it. If the deployment behaviour of a jaggery app is something like, reading all configs from its own jaggery.conf and putting them into a runtime representation of a web.xml, then rather than going for any non-standard configuration file, etc, I believe, the same config can be used to implement certain application specific context parameters as well. Therefore, +1 for the proposed functionality. Appreciate some feedback from the rest of the community as well. Cheers, Prabath > >> >> [1]. >> https://github.com/wso2/jaggery/blob/8c58180f541f110609b9c0c66cc3e0c62c8caa39/components/jaggery-core/org.jaggeryjs.jaggery.app.mgt/src/main/java/org/jaggeryjs/jaggery/app/mgt/TomcatJaggeryWebappsDeployer.java >> >> Thanks, >> >> Harshan Liyanage >> Software Engineer >> Mobile: *+94724423048* >> Email: [email protected] >> Blog : http://harshanliyanage.blogspot.com/ >> *WSO2, Inc. :** wso2.com <http://wso2.com/>* >> lean.enterprise.middleware. >> > > -- Prabath Abeysekara Technical Lead WSO2 Inc. Email: [email protected] Mobile: +94774171471
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
