It really shouldn't be a problem to make 'em final, but as with all API
changes, there needs to be at least *some* consideration given ;-)
- James Snell
IBM Emerging Technologies
[EMAIL PROTECTED]
(559) 587-1233 (office)
(700) 544-9035 (t/l)
Programming Web Services With SOAP
O'Reilly & Associates, ISBN 0596000952
Have I not commanded you? Be strong and courageous.
Do not be terrified, do not be discouraged, for the Lord your
God will be with you whereever you go. - Joshua 1:9
Tom Jordahl <[EMAIL PROTECTED]>
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 names in MessageContext?
--
Tom Jordahl
Macromedia Server Development
-----Original Message-----
From: Steve Loughran [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 07, 2003 3:38 AM
To: 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 everything out there
break?
If we cannot change the existing strings, we can at least put a block on
adding new non-final strings through comments and self control.
-steve
