On Sat, Sep 27, 2008 at 1:54 PM, David Leangen <[EMAIL PROTECTED]> wrote: > >> Nope. If your Google search was right, it said that the classes must >> be in the same classloader. I.e. The javax.activation looked like it >> was sitting either in the Framework's classloader, or more likely, in >> a classloader higher up, such as the System Classloader (the one >> specified by -cp and/or CLASSPATH), mean it won't see the javax.mail >> classes. > > But I thought that... ohhh, ok... never mind.
Well, I am not sure how javax.activation works, nor javax.mail, under the hood. I am just interpreting the clues that you have found and provided here. > So then one of two possible solutions would be: > > 1. Provide javax.activation together with my > javax.mail, or > > 2. Move javax.mail to the system classloader > > I don't like (2). > > I was doing (1) before, and that was causing headaches... > > So I guess I need to go back to the first solution... Would you agree? I think a javax.mail bundle with javax.activation internally (no import, no export) is the way to go. Feel free to create a Pax project for it. Cheers Niclas _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
