[jboss-as7-dev] HTTP API Status & DMR GWT Prototype

[Jason T. Greene]

On 2/10/11 8:36 AM, Brian Stansberry wrote:
> On 2/9/11 11:36 PM, Jason T. Greene wrote:
>> Last week Brian merged my http api patch into his detyped2; however, the
>> most current iteration is here:
>>
>> https://github.com/n1hility/jboss-as/tree/detyped2
>>
>> Currently JSON read operations via GET are supported, POST is coming
>> soon, now that Jonathan Pearlin, a new contributor, recently completed
>> the JSON parser patch he was working on (Thanks Jonathan!). In addition
>> a special base64 encoded binary representation is also supported;
>> however, I will explain its purpose in another email.
>>
>> The GET URL form is a mapping of operation addresses, with a few
>> supported read operations, and support for mapping top level values via
>> query parameters. The default operation is read-resource. So in
>> otherwords you can dump the whole management tree like so:
>>
>> http://localhost:9990/domain-api?recursive
>>
>> The lack of additional /'s defaults to the root node.
>> The lack of an "operation" defaults to the read-resource operation.
>> The "recursive" is mapped to the recursive as a boolean, a lack of an
>> assignment defaults to "true"
>>
>
> In the native API, "recursive" defaults to "false".

It does in the HTTP API as well. What I mean is that if you put a 
boolean name in the query it's assumed that you are specifying it to be 
true. If recurisve is not specified it defaults to false. You can also 
say recursive=true|false. It's basically equivalent to the way -D works 
in ant/maven.

-- 
Jason T. Greene
JBoss, a division of Red Hat