tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Manni-Bucau (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TOMEE-1524) tomee doesn't start up deployments on restart
Date Sun, 15 Mar 2015 17:25:38 GMT

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

Romain Manni-Bucau commented on TOMEE-1524:
-------------------------------------------

[~struberg] get it better with your last comment but then this has no link with the original
issue. As a side note: EE defines deployment and "start" but most of the time it defines deployment
as part of what I called start ie deployment = deployment phase + start (check management
API). Deployment = copy of binaries with nothing more is never defined - of course since I
know as I almost know as much way of working as applications. We can discuss it on the list,
in tomee doing this 2 steps deployment would be quite easy (1- create info tree, 2- create
*Context objects) but I doubt it would be in DeployerEjb. I clearly see it as an internal/tool
solution rather than a prod one (where provisioning solutions have my preference until now)

> tomee doesn't start up deployments on restart
> ---------------------------------------------
>
>                 Key: TOMEE-1524
>                 URL: https://issues.apache.org/jira/browse/TOMEE-1524
>             Project: TomEE
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Mark Struberg
>             Fix For: 2.0.0
>
>
> We should set
> {quote}
> openejb.deployer.save-deployments = true
> {quote}
> in conf/system.properties as a default.
> This is needed for EAR deployments not getting 'lost' during server restarts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message