[
https://issues.apache.org/jira/browse/SYNCOPE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14080957#comment-14080957
]
Guido Wimmel commented on SYNCOPE-538:
--------------------------------------
I've had a look at the commit and observed the following (not sure if it's
justified):
* the mail templates still seem to be loaded only from the classpath
* why is conf.directory set in syncope-archetype only in console's pom.xml and
only for profile embedded? when one executes mvn -Pembedded in the console dir,
the value set for conf.directory is only applied for syncope-console.war; for
syncope-core.war the conf.directory value from the Syncope parent pom is used.
(maybe this is intentional)
In addition, there is maybe a small difference in the semantics of
persistence.properties when used in AuditConnectionFactory and for the normal
localDataSource. I think if the external persistence.properties file does not
specify all properties, the defaults from the classpath are used for
localDataSource (same as with the other properties files), but not for
AuditConnectionFactory. I'm not sure though, I haven't tested, and probably
this can be ignored.
> Externalize all WAR configuration
> ---------------------------------
>
> Key: SYNCOPE-538
> URL: https://issues.apache.org/jira/browse/SYNCOPE-538
> Project: Syncope
> Issue Type: Improvement
> Components: console, core
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Fix For: 1.2.0, 1.3.0
>
>
> The main webapps (core and console) require several configuration files
> (.properties) to work properly.
> Currently such configuration files need to reside into webapps' classpath.
> Ideally it should be possible to define a configuration directory, defined
> via a Maven property, where all such files can be loaded from: this would
> allow to implement some handful deployment scenarios (e.g. deploy the same
> .war files either in test and production environments).
> The same idea is to apply to e-mail templates.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
