Hi Tim,
Looking at the code, it's not clear to me how this can be leveraged unless
the admin command takes an option like --upload. This is something I am
struggling with. Before your code changes, --upload (and --deploymentplan)
triggered an upload functionality. Has that remained the same after your
changes?
Also, a few other questions:
- What is a "payload"? Isn't it just a file or set of files?
- How does the "download" work? Does the generic download of the so-called
payload "save" the files in the payload on disk?
Regards,
Kedar
Tim Quinn wrote:
> Hi, everyone.
>
> I have just checked in several changes. I wanted to let everyone know
> what I've changed, not only so you can use it in your own work but also
> so you're alert to any odd failures you might see. I have tested quite
> thoroughly so I do not expect people to see problems.
>
> [Ludo and Vince: I have tested deploying and running an app with
> NetBeans 6.5 and it works fine with these changes in place, as it
> should. When only the status report comes back in the payload the data
> in the payload should look exactly as it has up until now.]
>
> These changes make it much easier for an admin client and for the
> server-side implementations of admin commands to work with any data
> passed back and forth as the payloads of the http request and response.
> If you need to add a command that uses the request or response payload
> please look at the Javadoc for the new org.glassfish.api.admin.Payload
> interface. I will probably blog about this in the near future and
> provide a few more details about how to use the Payload interface if you
> are building a new command.
>
> - Tim
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>