2009/3/20 Neil Bartlett <[email protected]>: > > One word of caution. It sounds like this approach would not work in a > variety of classloading scenarios, such as J(2)EE or OSGi, since you > make some assumptions about JAR files and the visibility of the > application "classpath" etc. > > I do a lot of work in OSGi and the proposal from John to get all > classes in a package according to one classloader would probably work > well, since OSGi strongly discourages "split packages", i.e. packages > provided by more than one module and therefore classloader.
Certainly it is not possible to answer the question "Please give me the names of all the classes in this package" in all cases. I have a ClassLoader which dynamically generate classes "on demand" (it's producing adapter classes with characteristics determined by the name of the class asked for). This results in a package with an infinite number of classes. John Wilson --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
