Hi, Peter
What kind of error did you get? Did this just stop working
recently or it has never worked?
We don't have an upload option in the DeployCommandParameters in
the server side (the upload option for admin cli case is handled by the
client side). This is probably why the url with the upload option does
not work.
Thanks,
- Hong
Peter Williams wrote:
> I'm working on remote (or just archive) deploy to V3 from NetBeans and
> having trouble with the deploy command
>
> I've been given the impression that the format is as follows -- is
> correct?
>
> URL - no rules - I'm guessing at this point but I would have thought
> something like
> "http://$server:$port/__asadmin/deploy?name=$name&upload=true" would
> have been sufficient. And since it's a POST request, perhaps even
> upload is redundant.
> Request type - POST
> Content type - application/zip
> Body - binary zip file containing the archive to be deployed (e.g war
> file, ear file, etc).
>
> I haven't been able to get this to work --
>
> The CLI deploy command has a "upload" option documented, but including
> this over the HTTP api causes an error.
> The HTTP api is requiring a path parameter though what that could
> possibly mean for remote deployment escapes me. If I refer to a valid
> local (to the server) file, the server cheats but if I refer to an
> invalid file, the command is failed.
>
> Does anyone know if this works and/or what the requirements are?
>
> -Peter
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>