[jboss-as7-dev] how to access the management model?

[Max Rydahl Andersen]

> I have a simple Maven plug-in using the Java API. It's probably not 100% complete yet, but it works for now. https://github.com/jamezp/jboss-as-deploy-plugin
> 
> Anyway, you'll see how simple the Java API is for deploying, redeploying and undeploying. I'm sure the API does a lot more than what I'm doing with it, but it's a simple example.

There is no doubt that the Java API is better - our concern is if that Java API will be back/forward compatible with releases of AS 7.x/EAP 6.x or if tools need to have a separate bundle compiled
for each version (biggest problems we've seen previously is that even when the api's didnt change the serialization did and boom - tools are broken).

>From what I understand the only way "out" of this is to use http or dmr api's since that is/should be stable and does not break as easily as a java library dependency.
There could of course still be changes/dependencies but the tools could handle that without having to bundle N versions of AS client jars.

That's why we are looking for and asking how to do operations like deployment and other operations via the http/dmr api.

/max


> --
> James R. Perkins
> 
> 
> On Wed, Mar 23, 2011 at 13:19, André Dietisheim <adietish at redhat.com> wrote:
> Hi Jason
> 
> thanks for the further insights!
> 
> > There is an HTTP interface that can take requests in either JSON or in
> > base64 encoded dmr binary format. We don't call it REST though because
> > "invoking" an arbitrary management operation (e.g. "clear auth cache")
> > does not meet the REST purity definition.
> 
> hmm, to be honest I dont really understand why a RESTy semantic (ex.
> post to or delete to the uri of the cache resource) would not allow this
> operation. But I might miss something here since I do not have the same
> background.
> 
> >
> > Keep in mind that the remote Java API will be the easiest to use from
> > Java, since it will handle all the transport stuff for you, and
> > exposes a nice API for working with detyped data. The main focus of
> > the HTTP interface is supporting non-Java clients (i.e. scripting
> > languages, and the console which is JavaScript based)
> >
> 
> oh, looks like I missed this one. Guess using the java API would be the
> better choice for me then. Is there any documentation about it?
> 
> Cheers
> André
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> 
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

/max
http://about.me/maxandersen