> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 15, 2001 11:51 AM
> To: [EMAIL PROTECTED]
> Subject: Native configuration changes.
>
>
> Hi,
>
> Playing with the JNI connector, I found few simple ways to
> make it easier
> to set it up. Larry, Mike - let me know if you're ok ( and if
> you can take
> care of the doc part ).
>
> 1. JniConnector will be included in server.xml ( un-commented
> ). I added
> code inside to detect if tomcat is started in jni mode, and will stay
> silent if not.
>
> 2. If we place all DLLs/SOs in TOMCAT_HOME/bin/native, I've added code
> that will set the library path automatically ( including so/dll/nlm
> extensions ). Also cleaner messages if the file is not there.
>
> 3. Same can be used to simplify mod_jk config, it's easier for
> ApacheConfig to generate this location instead of
> ApacheHome/libexec ( or
> modules/, depends on apache version ).
>
> 4. The user will configure:
> - conf/jk/workers.properties: add 'inprocess' to the list of workers,
> set workers.java_home, ps, etc. ( quite easy IMHO )
> - conf/server.xml: <ApacheConfig jkProtocol="inprocess" />
> - start tomcat ( so it can regenerate auto-config files in jni mode )
> - start apache
+1
>
> IMHO it's much simpler and cleaner - Larry, it's your call,
> the changes
> are easy on the java side - but docs need to be synchronized and we're
> quite late. Is it worth it ?
There is still a lot of documentation that isn't "synchronized", so I think
there is time. I still plan on not releasing beta2 until the documentation
is "reasonable". I'm currently working on tomcat_ug.html. I am in favor of
adding minor feature improvements if it will simplify the documentation
and make usage easier.
Cheers,
Larry
