[
https://issues.apache.org/jira/browse/OPENEJB-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295079#comment-13295079
]
Andy Gumbrecht commented on OPENEJB-1791:
-----------------------------------------
It is more a case maintaining legacy installations that get updated with 'new'
services and the default location of files in a new installation.
If the jars are updated in an existing installation then the default action is
to create a new service.properties with the disabled option set to true. The
location of this properties file was 'conf', and is now 'conf/conf.d'. This is
not currently documented anywhere (apart from here), so it was a surprise. The
change should be transparent. In this case it means that 'conf.d' should not be
the default (I don't mind that it is though).
Now I know that I have to physically create the new service file where I want
it during a patch (or re-write some code), and not let the system automatically
create it (which is what I was expecting), it is not an issue. I just wonder if
I am the only one that had an issue?
I also have applications and or installers that have been written to 'expect'
these files to be in conf (as they have been for a very long time), and also
users have become accustomed to to editing files at that location, to promote
any change is not trivial.
An example (maybe a bad one), if the default location of the tomcat
'server.xml' changed from one edition to the next then I am sure that thousands
of developers would literally explode on the spot.
> managing a conf.d folder as under unix for services
> ---------------------------------------------------
>
> Key: OPENEJB-1791
> URL: https://issues.apache.org/jira/browse/OPENEJB-1791
> Project: OpenEJB
> Issue Type: Improvement
> Reporter: Romain Manni-Bucau
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
