[jboss-jira] [JBoss JIRA] Commented: (JBAS-6697) provide API in DeploymentManager for specifying which dir the file should be deployed to (e.g. to deploy to farm dir, rather than deploy dir)
Ian Springer (JIRA)
jira-events at lists.jboss.org
Sun Mar 29 10:34:24 EDT 2009
[ https://jira.jboss.org/jira/browse/JBAS-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12459510#action_12459510 ]
Ian Springer commented on JBAS-6697:
------------------------------------
That sounds close to what we need, but not exactly. In the Jopr jboss-as-4 plugin, when a user creates a new WAR or EAR via Jopr, they are prompted to enter the deploy directory, which is a path relative to the AS configSet dir. They would usually enter "deploy" or "farm", but we had a couple users who deployed to "my.custom.deploy" or something (e.g. when they wanted to keep their deploy dir on a different filesystem). We were hoping to provide this same option at app create time in the jboss-as-5 plugin. Prompting for a deployment profile name seems like it might be too low-level for an end-user; it might be more intuitive to them to just specify the directory they want to deploy to. What do you think? Charles, any thoughts?
> provide API in DeploymentManager for specifying which dir the file should be deployed to (e.g. to deploy to farm dir, rather than deploy dir)
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBAS-6697
> URL: https://jira.jboss.org/jira/browse/JBAS-6697
> Project: JBoss Application Server
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: ProfileService
> Reporter: Ian Springer
> Assignee: Emanuel Muckenhuber
>
> I could also use an API that tells me which deployment directories are available, e.g.:
> Set<URL> getDeploymentDirectories();
> I need this for the EAR/WAR create functionality in the jboss-as-5 plugin, because I want to throw an Exception if an EAR/WAR with the same name is already deployed. I suppose this could also be accomplished with an additional parameter to distribute(), e.g.:
> DeploymentProgress distribute(String name, URL contentURL, boolean copyContent, boolean overwriteIfAlreadyExists) throws Exception;
> i.e. where it would throw an exception if overwriteIfAlreadyExists=false and an app with the same name is already deployed.
--
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
More information about the jboss-jira
mailing list