geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan D. Cabrera" <...@toolazydogs.com>
Subject Re: Incompatible API change in Configuration
Date Mon, 04 Apr 2005 19:28:42 GMT
I tend to agree but, I think that it's a good habit to start getting into.


Regards,
Alan

Dain Sundstrom wrote:

> I personally think this is way way way too early to be worried about 
> binary compatability between configuration objects build with pervious 
> releases and builds.  Also, are you taking only about the official M1, 
> M2 and M3 releases or builds from code?
>
> What do you, the community, think about us spending time thinking 
> about binary compatibility between milestone releases?
>
> -dain
>
> -- 
> Dain Sundstrom
> Chief Architect
> Gluecode Software
> 310.536.8355, ext. 26
>
> On Apr 4, 2005, at 3:08 AM, Gianny Damour wrote:
>
>> My bad :(
>>
>> I must admit that this is a side effect that I have not duly 
>> considered. I considered the source and binary compatibility and I 
>> missed this serialization specific incompatibility.
>>
>> Gianny
>>
>> On 3/04/2005 6:15 AM, Jeremy Boynes wrote:
>>
>>> On 3/22 in revision 158589 the API for Configuration changed in that 
>>> the return type from getConfigurationClassLoader() changed from 
>>> ClassLoader to a ConfigurationClassLoader. This means all 
>>> configurations built before then are now inoperable with the current 
>>> tree as the attribute type in the persisted GBeanData does not match 
>>> the new signature.
>>>
>>> I can't find any discussion on the list around then that would alert 
>>> users to this change. It is critical that we let people know when 
>>> this kind of change is made.
>>>
>>> -- 
>>> Jeremy
>>>


Mime
View raw message