quot; <[EMAIL PROTECTED]>
cc
bcc
Subject
Re: MessageContext and final static strings
the eclipse doc says that "Making an API field final breaks compatibility
with pre-existing binaries that attempt to assign new values to the
field.".
assuming nobody tried to do this, I think making th
the eclipse doc says that "Making an API field final breaks compatibility
with pre-existing binaries that attempt to assign new values to the field.".
assuming nobody tried to do this, I think making the fields final should be
OK.
on a related topic, any reason why these bunnies in JWSHandler are
]>
01/08/2003 07:29 AM
Please respond to axis-dev
To
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc
bcc
Subject
RE: MessageContext and final static strings
Make 'em final.
How would it break anyone? Do we think that someone is overriding the
property na
axis-dev
Subject: MessageContext and final static strings
MessageContext has a lot of public static strings, but it seems to me that
they should be public final static strings, since their target use is the
various names of properties.
Can we change these to final static strings? Or does every
- Original Message -
From: "James M Snell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 07, 2003 17:06
Subject: Re: MessageContext and final static strings
> Oy ve. I highly doubt changing them to final will break anything, but it
&g
v
To
"axis-dev" <[EMAIL PROTECTED]>
cc
bcc
Subject
MessageContext and final static strings
MessageContext has a lot of public static strings, but it seems to me that
they should be public final static strings, since their target use is the
various names of properties.
Can we chang
MessageContext has a lot of public static strings, but it seems to me that
they should be public final static strings, since their target use is the
various names of properties.
Can we change these to final static strings? Or does everything out there
break?
If we cannot change the existing strin
