You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Chris Christo (JIRA)" <ji...@apache.org> on 2014/02/27 11:40:19 UTC

[jira] [Commented] (OPENEJB-2077) Do not require openejb.json/openejb.xml

    [ https://issues.apache.org/jira/browse/OPENEJB-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914363#comment-13914363 ] 

Chris Christo commented on OPENEJB-2077:
----------------------------------------

Regarding 2) is this something that could always be done? or something you patched just now?

> Do not require openejb.json/openejb.xml
> ---------------------------------------
>
>                 Key: OPENEJB-2077
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-2077
>             Project: OpenEJB
>          Issue Type: Wish
>          Components: configuration
>    Affects Versions: 4.6.1
>            Reporter: Chris Christo
>            Assignee: Romain Manni-Bucau
>            Priority: Minor
>             Fix For: 4.6.1
>
>
> I think it would be great if for OpenEJB standalone, we didn't require an openejb.xml | openejb.json file to be in the conf folder. If there isn't any, then no openejb.xml should be created automatically either. At present you can configure everything via a properties file (system.properties) sitting in the conf folder except for one thing; The Deployments tag. If the deployments directory is not set, then OpenEJB will not scan the apps folder (I think by default it should scan the special name 'apps' or 'webapps' anyway). 
> In summary:
> 1) Do not require openejb.xml | .json (and do not produce one automatically if none is present)
> 2) Add the ability to configure the Deployments as a system property.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)