[
https://wso2.org/jira/browse/ESBJAVA-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27279#action_27279
]
Ruwan Linton commented on ESBJAVA-545:
--------------------------------------
Hi Eric,
Thanks a lot for your very valuable contribution, and this aspect seems to be
fixed on the Carbon based ESB (2.0 afterwards), where you have all the
configurations in the conf directory (except for the log4j.properties file,
which resides in the root lib directory) which can be configured using the
carbon.home system property.
Thanks,
Ruwan
> Separate configuration from software installation
> -------------------------------------------------
>
> Key: ESBJAVA-545
> URL: https://wso2.org/jira/browse/ESBJAVA-545
> Project: WSO2 ESB
> Issue Type: Improvement
> Affects Versions: 1.7
> Reporter: Eric Hubert
> Assignee: Ruwan Linton
> Attachments: conf.patch, core.patch, startup.patch
>
>
> It should be possible to separate the configuration from rest of the software
> installation. This allows to use different configurations to for multiple
> instances of one central software installation of WSO2 ESB (the same way it
> can be down with Bea Weblogic or JBoss).
> Current Situation:
> ------------------------
> The WSO2 ESB configuration resides in the following two directories and is
> split over various files.
> <ESB_INSTALLATION>/webapp/WEB-INF/classes/conf
> <ESB_INSTALLATION>/tomcat/conf
> This design is driven by the deployment of Synapse as a (exploded) web
> archive. Some configuration files are grabbed from the classpath, while
> others are read as file resources depending on system properties and/or init
> parameters specified in the web.xml.
> Requirement/Aim:
> -------------------------
> Ideally I would like to pass an option specifying the configuration location
> (any directory outside the webapp) to a server start script. Of course the
> synapse configuration plays a special role and any user should be able to put
> this file to a location outside this configuration folder. Right now this is
> already possible via using the System-Property "synapse.xml".
> Possible Solution:
> -------------------------
> Use system property to be able to specify configuration directory containing
> what's currently in the config directories. I no property is specified the
> current behavior should be preserved. Also the classpath needs to be changed
> to contain this folder.
> The attached patches demonstrate the changes which would be required to
> introduce such a variable to the WSO2 ESB code. It has been created against
> the 1.7-Tag. The Synapse source code does not need to get touched.
> Limitations:
> ---------------
> - identity.jks, trust.jks and ui-extensions-config.xml need to stay in
> webapp/WEB-INF/classes/conf due to some other code dependencies in Synapse
> (HttpCoreNIOSSListener/'Sender)
> - context.xml, tomcat-users.xml, and web.xml need to stay in tomcat/conf
> (seems to be a requirement of Tomcat-Engine)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Esb-java-dev mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
