thanks alot for your mail. The only solution really seems to be to either
put everything in jre/lib/ext or to specify all jars at server startup via
the command line.
However, I find that when placing pop3.jar in the jre/lib/ext directory, I
also have to put mail.jar and activation.jar there (even though they reside
in the orion install dir). I finally ended up modifying the manifest file...
I think this library business is a pretty annoying problem, especially
considering the time spent to figure out whats going on..
-----Original Message-----
From: Terence Kwan <[EMAIL PROTECTED]>
To: Orion-Interest <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Mittwoch, 1. November 2000 09:20
Subject: RE: accessing javamail provider
See enclosed mail
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Christian Sell
> Sent: Monday, October 30, 2000 5:04 PM
> To: Orion-Interest
> Subject: accessing javamail provider
>
>
> Hello,
>
> I've posted this before on orion-interest:
>
> I am using JavaMail to access a pop3 mailbox. No matter where I place the
> pop3.jar file (from sun, or poppers.jar) in the system, I always get a
> NoSuchProviderException saying thath no pop3 provider was
> available. I have
> tried the following locations for the pop3.jar:
>
> <orion-install>,
> <orion-install>/lib
> WEB-INF/lib
> any other path referenced through <library path=> in orion-application.xml
>
> The problem happens even though I am able to load classes from the jar via
> Class.forName().
>
> To verify this problem further, I deployed the same application
> on JRun 3.0.
> With JRun, I have to place the jar file in <jrun-install>/lib/ext
> (actually
> thats where the one that comes with JRun is located), and everything works
> fine.
>
> thanks,
> Christian Sell
>
>
>
