so the console is ignoring case while the REST API does not ?
On Apr 15, 2010, at 11:53 AM, Jason Lee wrote:
> On 4/14/10 5:24 PM, Jerome Dochez wrote:
>> it depends on what ConfigBean these REST APIs are mapped to. For the most part the REST API to alter the ConfigBeans directly but there are cases (like deployment) where you don't want to just alter the configuration, you want to deploy so it makes more sense to redirect the REST APIs to a command class rather than changing the config bean directly.
>>
>> which ones were creating issue for you ?
>>
>
> Hrm. That's a good point. The resource in question, at the moment, is JdbcConnectionPoolResource.
>
> OK. So I understand the why of the command class, and that makes sense. I still prefer, I think, to see mixed case on property names returned by the REST API. Anyone have thoughts on that? Would it be unwise to change what the REST API returns? Should be try to address the case issue on the console side?
>
> --
> Jason Lee
> Senior Member of Technical Staff
> GlassFish Administration Console
>
> Oracle Corporation
> Phone x31197/+1 405-343-1964
> Blog http://blogs.steeplesoft.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>