admin@glassfish.java.net

Re: change AMX package names for V3?

From: Lloyd Chambers <Lloyd.Chambers_at_Sun.COM>
Date: Thu, 25 Sep 2008 14:22:58 -0700

June,

No, they were not.

However, my current view is that they *should* be changed because of
enough incompatible changes.

Also, an additional package name *is* being used: org.glassfish.api.amx

Finally, other modules can use whatever package name they want for AMX
interfaces.

Lloyd



On Sep 25, 2008, at 1:37 PM, June.Parks_at_Sun.COM wrote:

> Lloyd,
>
> Were the package names changed? I don't remember hearing anything
> about it after this message.
>
> June
>
> On 04/15/08 15:16, Lloyd L Chambers wrote:
>> It turns out there there are going to be many incompatibilities
>> with V3 in AMX.
>>
>> This starts with our change to <applications> in domain.xml, the
>> need to generically support elements like <configs>, <servers>,
>> <clusters>, etc, and various other little things that "add up" to a
>> fair number of changes.
>>
>> PROPOSAL:
>>
>> Change package names for the entire AMX API:
>>
>> com.sun.appserv.management => org.glassfish.admin.amx
>>
>> There are a number of sub-packages underneath
>> com.sun.appserv.management.
>>
>> Lloyd
>>
>>
>> ---
>> Lloyd L Chambers
>> lloyd.chambers_at_sun.com
>> Sun Microsystems, Inc
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>