[
https://issues.apache.org/jira/browse/TOMEE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360535#comment-14360535
]
Romain Manni-Bucau commented on TOMEE-1524:
-------------------------------------------
[~jlmonteiro] 2 is wrong, 4 is fixed, 3 is what you do (real issue is we skip
the deployment where we should fail so nothing to do on this jira for it).
About 1 - writing here since needs few more words: setting this flag to true by
default has several issues breaking existing applications not relying on it:
a- transient deployments (cloud)
b- cluster (default behavior is not this one and you can now get propagated the
deployments)
c- some IDE integrations
That said and even if I tend to agree on the "should be" part we can't today
cause this is too late + we just need to document this advanced usage flag in
system.properties.- for real environments I think relying on it is a sign you
miss something in your infra (maybe just my opinion).
> 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)
