You are right. Broken depends on your perspective.
So, the question of, "why did this (the syntax) get changed?" remains
unanswered.
Can anyone answer that question?
In the case of directory deployed web apps, etc... the user has entered
the name and the path to deploy the app, right?
The domain.xml has the correct path associated with the name and should
just use that, if there is no path argument given.
I think the new "correct" syntax is actually asking tools and users to
reenter data. (I cannot really tell, since I don't see any definitive
reference for redeploy through the web admin interface)That seems like
it will make mistakes easier to make... not harder...
vbk
PS: I also noticed that Ludo's original question was not answered
directly... "what is the real syntax for redeploy or a dir deployed
app?" (which I think is really... what is the real syntax for redeploy
of a dir deployed app?)
Jane Young wrote:
> Hi Vince,
>
> It's not broken... the syntax has changed for redeploy :-)
>
> Jane
>
>
> Vince Kraemer wrote:
>
>> It seems like a bad idea to break something that has been working...
>>
>> Why did this get changed?
>>
>> vbk
>> Jane Young wrote:
>>
>>> Hi Ludo,
>>>
>>> The correct syntax for redeply is to use the full path.
>>> "redeploy" is the same as "deploy --force=true <path>".
>>>
>>> Jane
>>>
>>> Ludovic Champenois wrote:
>>>
>>>> so what is the real syntax for redeploy or a dir deployed app?
>>>>
>>>> With TP1, this used to work:
>>>>
>>>> http://localhost:8080/__asadmin/redeploy?name=WebApplication18
>>>>
>>>> Since the name 'WebApplication18' is known and it's location is
>>>> known (see the list-application), then this command should work for
>>>> dir deployed app, no?
>>>> Should I do instead:
>>>>
>>>> http://localhost:8080/__asadmin/redeploy?path=FULLPATH
>>>> ?
>>>> Ludo