Stuart Roebuck wrote:
> 
> Having downloaded the latest CVS version of James and JNDI 1.2.1 I've been trying to 
>get it up and running on my system (MacOS X Beta).
> 
> I put jndi.jar into the lib directory and altered the build.xml to include it:
> 
> Index: build.xml
> ===================================================================
> RCS file: /products/cvs/master/james/build.xml,v
> retrieving revision 1.30
> diff -r1.30 build.xml
> 43c43
> <       <property name="classpath" 
>value="./lib/AvalonAware.jar;./lib/activation.jar;./lib/mail_1_1_3.jar;./lib/xerces.jar;./lib/dnsjava.jar;./lib/town.jar"/>
> ---
> >       <property name="classpath" 
>value="./lib/AvalonAware.jar;./lib/activation.jar;./lib/mail_1_1_3.jar;./lib/xerces.jar;./lib/dnsjava.jar;./lib/town.jar;./lib/jndi.jar"/>
> 
> This allowed me to build without any errors.

Makes sense.

> 
> Then I had problems with the res/run.sh script.  It appears to me to be missing a 
>lot of the libraries from the classpath including the newly built "JAMES.jar" and 
>"mailet.jar", but I don't really know what needs to be there.  There also appears to 
>be an inconsistency in the referencing to the "Loader.jar" compared with all the 
>rest.  Assuming that (for me) I was happy to always call "res/run.sh" from the home 
>directory of James, I altered the "run.sh" file to use absolute file paths and 
>include all the jars as follows:

I don't think your version will work.
run.sh works (for me!) if I cd to the bin directory and then go:
./run.sh . One issue here is that Loader.jar looks for blocks and
conf.xml files relative to where it is.
The only change you should need is to add ../lib/jndi.jar to the
classpath. 

Alternatively, and better, you can add the jndi jar to the directory
lib/ext in your jre - ie make it an installed extension, then you don't
need to fiddle with classpaths for build or run.

See how that goes,

Charles


> 
> Index: res/run.sh
> ===================================================================
> RCS file: /products/cvs/master/james/res/run.sh,v
> retrieving revision 1.9
> diff -r1.9 run.sh
> 14c14
> < 
>LOCAL_CLASSPATH=Loader.jar:../lib/AvalonAware.jar:../lib/xerces.jar:../lib/mail_1_1_3.jar:../lib/activation.jar
> ---
> > 
>LOCAL_CLASSPATH=$PWD/lib/Avalon.jar:$PWD/lib/Loader.jar:$PWD/lib/AvalonAware.jar:$PWD/lib/xerces.jar:$PWD/lib/mail_1_1_3.jar:$PWD/lib/activation.jar:$PWD/lib/dnsjava.jar:$PWD/lib/town.jar:$PWD/build/JAMES.jar:$PWD/build/mailet.jar:$PWD/lib/jndi.jar
> 
> This was enough to get things running a little, but whereas the documentation talks 
>about it automatically generating a configuration file, this was not happening.  So I 
>copied the file "src/org/apache/james/JAMES.conf.xml" into a new directory "conf" and 
>altered the DNS references as required.
> 
> This allowed me to get as far as the following output:
> 
> Avalon runner
> 
> parser            : org.apache.xerces.parsers.SAXParser
> configurationPath : ../conf/
> logFile           : ../logs/avalon.log
> libPath           : ../lib/
> blockPath         : ./blocks/
> 
> Scanning jars for new Blocks...
> Unknown Exception null
> java.lang.NullPointerException
>         at 
>org.apache.avalon.loader.AvalonConfiguration.getAvalonConfiguration(AvalonConfiguration.java:39)
>         at org.apache.avalon.loader.Main.main(Main.java:80)
> 
> I assumed this was because it wasn't finding my configuration file.  So I tried 
>running it with:
> 
> res/run.sh -c $PWD/conf/
> 
> but this didn't help, so now I'm stuck.
> 
> Any suggestions - am I doing something wrong or is it my fault for trying the latest 
>CVS?
> 
> Stuart.
> 
> -------------------------------------------------------------------------
> Stuart Roebuck, BSc, MBA        Tel.: 0131 228 4853 / Fax.: 0870 054 8322
> Managing Director                       Alpha Numeric Pager: 07654 588898
> ADOLOS                                             http://www.adolos.com/
> 
> ------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Archives:  <http://www.mail-archive.com/james%40list.working-dogs.com/>
> Problems?:           [EMAIL PROTECTED]


------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives:  <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?:           [EMAIL PROTECTED]

Reply via email to