Re: [jboss-as7-dev] Remote deployment through deployment API

The design issue we need to decide on (thanks for the thread to do it ;) ) is how to upload content to the DC or standalone AS. The client-side API in Alpha1 included a method that was used for this: /** * Add the content for a deployment to the domain controller. * * @param name The deployment name * @param runtimeName The runtime name * @param stream The data stream for the deployment * @return The unique hash for the deployment */ byte[] addDeploymentContent(String name, String runtimeName, InputStream stream); The client side impl of that API then read from the stream and pushed the bytes to the server. (There were convenience utilities as well, but that's another topic.) The current detyped client side API[1] has no such stream-based method. With what it exposes, users would have to create operation requests using ModelNode, and either a) pass the content as a byte[] param in the operation request or b) pass a String param that represents a URL from which the server can read the content (URL must be accessible to the server). The simplest solution is just to add "byte[] addDeploymentContent(String name, String runtimeName, InputStream stream)" back into the client side API. That's what I'll do unless we reach a different decision in the next day or two. All the other operations used in Alpha1 for deployment can easily be mapped to detyped requests using [1]. That should be done for the standalone mode case today or tomorrow. - Brian [1] https://github.com/bstansberry/jboss-as/blob/detyped2/controller-client/s... On 1/24/11 6:39 AM, Heiko Braun wrote: -- Brian Stansberry Principal Software Engineer JBoss by Red Hat