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

Jean-Louis MONTEIRO commented on TOMEE-1524:
--------------------------------------------

Thanks Mark for reporting. I just went into the same issue.

My 2 cents ...

1. We currently don't save deployments out of the box.
--> I don't understand why we need to say tomee, yes I deployed a webapp and I want you to keep it after the server cycles.
I would have expect the flag to be by default it's saved.

2. By default we deploy to java.io.tmp and add an entry to conf/deployments.xml
--> it's good, but the tmp directory (as it's named) is temporary
So after restarting TomEE there is an high chance the directory is empty. Then, the entry is still in the deployments.xml and so TomEE fails to restart.

3. When undeploying and deploying again a webapp, the file gets a new entry, but the previous one is never removed

4. When undeploying a webapp, the deployments.xml file does not seem to be updated.

To many issues in my opinion to get this feature really "production" ready

> 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)