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?
yes, it would. you'd get an UnsatisfiedLinkError if it was missing,
or any one of a variety of errors if it wasn't binary compatible with
the one you compiled against.
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?
the particular implementation you've seen would be broken on such a
VM, yes. so that wouldn't be what shipped with that VM.
_______________________________________________
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
