Hi,
> > * secondly when we have two different apps that have the same name .sar,
> it
> > will not install the secon one. ie imagine there was a foo.sar in the
> > ${phoenix.home}/apps and we executed the following
> >
> > ./run.sh --application /some/other/dir/foo.sar
> >
> > This would not work because there is already an app named "foo". So we
> need
> > to think of a way to work around that.
>
> Yeah, I know! I guess we have to pick a re-naming convensions. The ones
that
> I can come up are:
>
> a) "app-name", "app-name~", "app-name~~".....
>
> b) "app-name", "app-name-1", "app-name-3".....
>
> I prefer a) but, maybe there is a better one?!
Ahh, I don't think this is right. If we change the name of the deployed
application will make things more complicated. Let's suppose we have two
applications having the same name "foo". When deploying the applications the
result will be: first application (1) will be deployed in "apps/foo"
directory and the second one (2) in "apps/foo~". Now if we reboot Phoenix
and re-deploy only the application (2) the Deployer will deploy application
(2) in application's (1) directory "apps/foo"!!!! Things get worse if we
would use PersistentDeploymentRecorder (as you said already).
So the simple solution would be to just print a message saying that an
application with the same name is already deployed. We could also have an
"--application-name" parameter passed at CLI.
Another problem is about "--application" parameter which I think is
redundant. Its functionality could be achieved by starting Phoenix with a
different deployment path using "--apps-path" (and having the .sar in that
path).
Mircea
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
