> 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.
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?
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
