Thanks so much for the information - it worked just fine.

Mark

On Fri, 26 Mar 1999, Damian Fauth wrote:

> [EMAIL PROTECTED] wrote:
> > 
> > Fine, but does merely putting mod_jserv.so in installdir/libexec do everything the 
>install is supposed to > do?  Does apache look into the install directory libexec 
>during build time?? This does not seem to work
> > for me. When you build apache, do you use --enable-module --enable-shared or 
>--add-module?
> 
> When you build apache use 
> 
> $ ./configure --prefix=/path/to/apache --enable-shared=max
> 
> This will build and statically link mod_so which is needed to implement
> the DSO module functionality. The "--enable-shared=max" option loads all
> other modules as DSO modules. By default, JServ is not included as one
> of these, so  you must then compile JServ as
> 
> $ ./configure --with-apache-install=/path/to/apache/installation
> --with-jdk-home=/path/to/jdk --with-jsdk=/path/to/jsdk
> 
> copy mod_jserv.so  to libexec as you describe above, then add the
> following lines to your httpd.conf:
> 
> --
> 
> # load JServ DSO
> LoadModule jserv_module       libexec/mod_jserv.so
> 
> # Force Apache to recognise JServ
> AddModule mod_jserv.c
> 
> --
> 
> and then put your normal JServ config options within a set of <IfModule
> mod_jserv.c> </IfModule> tags in httpd.conf. This is from an Apache
> 1.3.4, JServ 1.0b3 installation on Solaris 2.51
> 
> Damian
> 
> 
> 
> 
> 



----------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives and Other:  <http://java.apache.org/main/mail.html/>
Problems?:           [EMAIL PROTECTED]

Reply via email to