Gomez Henri wrote:
>
> > > If you take a look at Ajp14 documentation, you'll see
> > > the JkAutoMount directive :
> > >
> > > Rigth now it at the following synthax :
> > >
> > > JkAutoMount workername [virtualhost]
> >
> > Having virtualhost there is not very good because there is already a
> > <VirtualHost> in Apache, having information in 2 different places
> > makes configuration complicated.
>
> Make sense.
>
> >
> > >
> > > This tell mod_jk to ask for ALL contexts available on
> > > the servlet-engine corresponding to workername.
> > >
> > > In tomcat 3.x current case you'll get all stuff under
> > > /examples, /admin, / .....
> > >
> > > The second parameter, virtualhost, will be used to have
> > > ONLY the URLs handled by the server-engine for a virtualhost.
> > >
> > > Wouldn't it be more wise to use instead :
> > >
> > > JkAutoMount workername context context-mount-uri
> >
> > What will be the differences beetween JkAutoMount and JkMount?
>
> In JkMount you'll need to indicate ALL the URL handled under the given context,
> ie /myapp/servlet/* /myapp/*.jsp. With JkAutoMount if you provide the
> base context, the servlet-engine will give them to web-servlet.
> Imagine you install cocoon on myapp, it's will handle also the .xml.
> servlet-engine is allready aware that it should handle the .xml, so
> just let him inform the web-server. (less works)
Ok:
JkAutoMount workername cocoon /cocoon
Is a least:
JkMount /cocoon workername
JkMount /*.xml workername
Correct?
>
> > >
> > > ie:
> > >
> > > JkAutoMount workername examples /examples
> > >
> > > which will make the servlet-engine respond :
> > >
> > > /examples/servlet/* /examples/*.jsp
> > >
> > > A way to keep autoconf features but under the web-server
> > > admin staff.... Then you could have JkAutoMount directives
> > > in all your virtual hosts part of your web-server :
> > >
> > > <VirtualHost myaltside:80>
> > > JkAutoMount myworker examples /examples
> > > </VirtualHost>
> > >
> > > <VirtualHost myaltside:443>
> > > JkAutoMount myworker admin /admin
> > > </VirtualHost>
> >
> > I prefer this one, it is more like the WebAppDeploy of mod_webapp.
> >
> > WebAppDeploy examples warpConnection /examples
> > JkMount /examples examples
> > JkAutoMount examples examples /examples
> > Confusing no?
>
> No more confusion if we use :
>
> mod_jk today :
>
> JkMount /examples ajpworkername
>
> mod_jk could use also now :
>
> JkAutoMount examples ajpworkername /examples
>
> What about ?
Well I was just thinking we could use the same order.
WebAppDeploy /examples warpConnection examples
JkMount /examples ajpworkername
JkAutoMount /examples ajpworkername examples
>
> -
> Henri Gomez ___[_]____
> EMAIL : [EMAIL PROTECTED] (. .)
> PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
> PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
