Vince Kraemer wrote:
> Prashanth Abbagani wrote:
>> [snip]
>>>
>>>
>> Its picking up the file from your current working directory, which is
>> definitely not the way its been explained in docs. How can this be
>> fixed, As I own this functionality for V3, I am interested to see if
>> the behavior can be fixed (Please file a bug in Sailfin separately)...
>
> I already have
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=4423 filed...
>
>>
>> Now there are two scenarios.
>> One where asadmin is invoked from a remote machine w.r.t DAS. Ideally,
>> the file if located on the same machine, should be uploaded to the DAS
>> machine and continue from there. We can do this the way deploy command
>> does, with an --upload option, default is true. So the file is assumed
>> to be on the local machine by default.
>> Other, when the file resides on the DAS machine. Which means the user
>> has to specify --upload=false and should give an absolute path. This
>> is again inline with how 'deploy' behaves.
>
> please add a '--force' option to add-resources, too.
>
> It is really painful to have to unregister each resource in a
> sun-resources.xml file "one by one", if you want to run add-resources a
> second time... (say you add a new resource to the file or correct a
> typo, etc...)
Good point. And what should the default value be (probably false)?
How about other create- commands, e.g. create-http-listener,
create-virtual-server etc.?
Can you file an RFE for this?
>