if you're too impatient to wait for Apple, back-port it to Java 5.
Is there any reason I cannot use sun.misc.Service like
javax.naming.spi does? After unzipping the src.jar file in java
home, that appears to be how the standard java SPI's are locating
class names. Once I've got the names, I think I can figure out how
to get a classloader to produce an instance for me... I mean, I
could read through every jar file in the classpath looking for /
META-INF/Service myself, but it seems like a bit of a waste if all
I want to do is find the class names and this thing does the
trick. Is using a sun.* class a bad idea for any reason?
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.
_______________________________________________
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
