I don't know how to support this behavior in V3.
First of all, the AMX API has never supported the idea of "magic"
values like null to remove things.
Second, is there even an HK2 API to remove an Attribute once it exists?
Third, seems like an HK2 bug to accept 'null' and turn it into the
string "null".
Lloyd
Begin forwarded message:
> From: anilam_at_dev.java.net
> Date: April 1, 2008 10:56:44 PM PDT
> To: llc_at_dev.java.net
> Subject: [Issue 4536] Domain Attribute Locale becomes null after an
> update
>
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=4536
>
>
>
> User anilam changed the following:
>
> What |Old value |New value
> =
> =
> =
> =
> =
> =
> =
> =
> =
> =
> ======================================================================
> Assigned to|anilam |llc
> --------------------------------------------------------------------------------
> Subcomponent|admin_gui |amx
> --------------------------------------------------------------------------------
>
>
>
>
> ------- Additional comments from anilam_at_dev.java.net Wed Apr 2
> 05:56:42 +0000 2008 -------
> This is a general issue in AMX and really needs to be fixed.
> GUI is calling domainConfig.setLocale() with NULL.
> And it ends up written out to domain.xml as "null".
> This problem is not limited to only this attribute, but for ALL
> optional attributes.
> I believe the correct behavior is to actually removed that optional
> attribute
> from domain.xml.
>
> transfer to AMX
---
Lloyd L Chambers
lloyd.chambers_at_sun.com
Sun Microsystems, Inc