[
https://issues.apache.org/jira/browse/TOMEE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14362326#comment-14362326
]
Mark Struberg commented on TOMEE-1524:
--------------------------------------
No Romain, even the JavaEE umbrella spec and the deployment spec clearly
separates between application deployment and application startup.
At deployment time we have to copy/unzip the artifacts of course. But it also
will create default resources and has to validate available resources, JNDI
locations etc. According to the EE spec those things have to validated before
the application starts. See the current EE spec discussion about how to handle
these requirements when CDI comes to play.
I agree that most of those requirements are 'nice to have' but no requirements.
E.g. you cannot finally verify JNDI resources before the application got
started. Nor should we fail a deployment just because a DataSource is not _yet_
defined.
Still there is a clear distinction between deployment and startup. _Especially_
when it comes to clusters! In a cluster I would expect a 'deploy' to also
distribute my binary to all my cluster nodes, do a fully automated
ripple-restart (to avoid downtime), etc
Of course I'm not sure if this should be part of TomEE or if the users have to
deal with this themselves (as it really depends on how your cluster setup does
look like).
> 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)
