[
https://jira.jboss.org/jira/browse/EMBJOPR-107?page=com.atlassian.jira.pl...
]
Charles Crouch commented on EMBJOPR-107:
----------------------------------------
I think this would be a useful enhancement in the future. I guess the work flow is
something like:
1) users attempt to deploy a new app with the same name as an existing one
2) DeploymentManager responds with a message saying deployment name is duplicated
3) console responds to the user saying the app already exists, please go and update the
existing app rather than add a new one
EmbJopr should not allow to deploy app that is already deployed
---------------------------------------------------------------
Key: EMBJOPR-107
URL:
https://jira.jboss.org/jira/browse/EMBJOPR-107
Project: Embedded Jopr
Issue Type: Feature Request
Reporter: Ondrej Žižka
Currently, when app is deployed over an identical app of the same name, EmbJopr fails
with an ugly message from JBoss AS (see bellow).
Would be nice if EmbJopr checked if an app of the same name is already deployed, and
then, either show readible error message, without attempting to deploy, or even better,
ask the user if it should try to re-deploy, and eventually do so.
--------------------------------------------------------------------------------
Failed to create Resource hellothere.war - cause:
java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException:
Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS MISSING DEPLOYERS: Name
vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/jbas5-admin-console.war/
-> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of
incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS MISSING DEPLOYERS: Name
vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/jbas5-admin-console.war/
--------------------------------------------------------------------------------
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira