- This topic has 3 replies, 2 voices, and was last updated 16 years, 5 months ago by
.
-
Posts
-
I have been having problems with getting the classpaths working correctly for JavaMail.
In Junit everything works. During Debug I can see that I am using “DEBUG: setDebug: JavaMail version 1.4ea”
However, when I run JRun from within ME it always fails. It is always coming up with ” JavaMail version 1.3.1″ , I have tried many different things to force Jrun to use the same version of Java Mail that Junit is.
I have placed the “pop3.jar” and “mailapi.jar” in the “WEB-INF\lib” directory.
I have tried to define them in the ME, project properties, Java Build Path.
I have tried to define the above two JAR files in the Paths section of the JRUN Application Server page.
I have also tried to add the “Launch Configuration” in the JRUN Application Server page.
I am not sure what else to try – so any suggestions would be appreicated.
Whale, it sounds like JRun ships JavaMail already (which is normal, J2EE/Java EE servers *have* to ship that spec) and when the server starts up it loads it’s own server JARs (JavaMail 1.3). So regardless of what you deploy with your project, it’s possible the server will just load it’s own versions of those Classes once.
Some servers allow you to specify a precedence of loading-order in cases like these, telling the server to load the web-app’s JARs first, then it’s own. I don’t know if JRun does support that, but it’s a server-specific setting you’d have to dig up out of the docs.
I am also not sure if you will be able to run JavaMail 1.4 on JRun 4… JRun 4 is an old J2EE 1.3 compliant server (http://www.adobe.com/products/jrun/) I doubt that you’ll be able to replace core Java enterprise spec libraries gracefully, iit may break portions of the server.
Thanks Riyad,
It is my understanding that from Jrun V4 Updater 7 that it supports newer version of Java. I am running JDK V5(i.e. V1.5) but I think Updater 7 also supports V6 (i.e. V1.6)?
