sun.* classes aren't part of the specification. any given VM may or
may not have them. Sun can add/remove/change them arbitrarily at will.
java.util.Service basically *is* sun.misc.Service, but made stable
and public. search the bug parade for more information.
Sorry if this is a dumb question... But lacking sun.misc.Service will
not preclude those VMs from making use of my library? It will only
keep them from being able to compile the SPI source itself, no?
Otherwise, wouldn't javax.naming.spi be broken on any VM that does
not have sun.misc.Service? I like the idea of dropping a plugin/
codec/whatnot anywhere in the classpath and having it *just work*.
I'm not so concerned about anyone wanting to improve on my framework.
If they really care, they can get a Mac too ;-) I won't mind tweaking
it when 1.6 arrives. As long as people are able to use apps built on
it and develop code that plugs into it, that's all I really care
about at the moment.
_______________________________________________
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
