>> 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).
Yes, that's the whole point of the detyped API. It makes long-term
compatibility much more practical.
Good so my understanding still matches reality ;)
Then we are still looking for how to actually perform and query deployments with this
detyped API.
For now I've just seen links/refs to the higher level Java API.
Is the answer "reverse engineer/read the source" of the java client api ? :)
/max