There is no way "around". The whole idea of "final" is to prevent
you form modifying class behavior in any shape or form.
Why don't you create proxy class which will wrap around Boolean and
encapsulate your special behavior in this class letting Boolean
object do the rest?
On Aug 27, 2006, at 10:28 AM, Ken Anderson wrote:
OK, I'm a little annoyed here because I find the whole concept of
'final' to be ridiculous.
I would like to subclass Boolean so that I can initialize it (class
method) with a short string (valueOf:"t" instead of valueOf:"f")
and also to return "t" and "f" for toString (or some other method
like toShortString()).
Unfortunately, java.lang.Boolean is marked as final. Is there any
way to get around that?
To give a little background, I would like to have a custom
WebObjects type where I can declare the factory method to create
the instance, and the method to call to get back the string
instance. I want to make it a single character so that I can use a
string field with length=1 instead of length=5 (saving a lot of
space).
Oh, and yet another reason I want categories from Objective-C in
Java...
Thanks,
Ken
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
