Ralph, Using the Class.forName alone will not suffice, you'll also have to AOT compile your code, I guess.
OSGi environments like Eclipse or other OSGi containers will more and more separate things into "bundle" class loaders, and in this context using JVM wide utilities or the context classloader may not help, since they may either be the wrong ones, either be irrelevant (At least that's my current understanding of the whole stuff, after having played with it a while trying to solve some classloader problems). So using Class.forName() is an easy way to ensure that you get the ClassLoader the most "close" to your class than possible. 2010/5/3 Stuart Sierra <[email protected]>: > On May 3, 11:16 am, Ralph <[email protected]> wrote: >> Yes, but I don't believe that it guarantees that you will get the >> manifest for the enclosing JAR file if you have more than one. > > I don't think that's possible in the general sense. Application > containers like OSGI may provide this functionality. > -S > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to [email protected] > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en
