Henri Gomez wrote: >>> Make the bridge class a parameter. >> >> >> That was the idea but we could have also to change method call > > Or may be a little better and more secure will be to specify bridge > target ie : > > tomcat 3.2, tomcat 3.3, tomcat 4.0, tomcat 4.1 or tomcat 5.0. > > The reason is that it may not be very safe to have people settings > there own bridge class. Also changing the name is only part of > the business, you may have to also update signature calls. > > worker.wrkjni.target=tomcat32/tomcat33/tomcat40/tomcat41/tomcat5 > > And we could adjust the bridge class and method call accordingly, > or send an error message if the target is still unrecognized. > > What do you think ? > > I know that jk2 will handle TC 4.X/5 but jk should have support > for at least TC 3.2/3.3
Reading old mail: there are other issues besides the name to support 4.x ( like starting, etc ). mod_jk2 will support it ( and already has this configurability ). In any case, this can't be considered 'release quality' ( i.e. what jk1.2 is ), nobody tested it. But if you need it - +1. -- Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
