Stephen McConnell wrote on Thursday, October 16, 2003:
>If you have a bind distribution then you already have a jamesXXX.sar 
>file.This is basically a zip archive that holds info for the the Phoenix 
>container plus jar files.  Included in the sar file are a few jar file 
>including jamesXXX.jar, mailet_X-X.jar, activation.jar, etc. If Phoenix 
>has already deplyed a jamesXXX.sar, then somewhere or other wyou will 
>find an equivalent directory with the content unpacked.  In that 
>directory you will probably find a directoy /lib - and that's the 
>directory you should probably include you mail jar files.  Please not 
>that this is totally diofferent to the Phoenix /lib directory which 
>basically contains jar file needed to tun Phoneix (the container). which 
>has nothing to with mailet execution.

That all makes sense.

>1. get james running withou your stuff

Fortunately, I have that.

>2. locate the directory that Phoenix is putting the cached jar file that 
>were in james.ar
>3. add you stuff to that directory (in /lib)

OK, I tried this but didn't have much success.  I found that the .jar files from the 
james.sar were getting extracted into james-1.2/work/james-1066282402475/SAF-INF/lib.  
However, copying my mailet JAR into this directory didn't do much good as Phoenix 
apparently wipes the work folder the next time it starts up.

So, taking Brian's advice

    Brian J. Sayatovic wrote on Wednesday, October 15, 2003:
    >I'm, no expert, but I've been adding my Mailet JARs right into the
    >James.SAR file instead of extracting the SAR and dropping my J AR into
    >the resulting lib directory.

I exploded the james.sar, added my .jar, and jar'd it back up again.

Now everything is working just dandy (except I'm getting ParseExceptions using 
MailAddress -- but that's another problem).  This seems like a tedious way of 
deploying my mailet, but I guess that's what shell scripts are for.  ;)

Thanks everyone for the input.

Cheers,

James

______________________________________________________
James Bucanek       <mailto:[EMAIL PROTECTED]>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to