Same thing... Jeff Tulley wrote:
> It is done through server.xml. I don't know what web server connector > you were using, but if it was Apache and mod_jk, you can still use it. > > On Tomcat's side, comment out the Coyote connector, which looks like: > <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" > port="8009" minProcessors="5" maxProcessors="75" > enableLookups="true" redirectPort="8443" > acceptCount="10" debug="0" connectionTimeout="0" > useURIValidationHack="false" > > protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/> > > Instead, use: > <Connector className="org.apache.ajp.tomcat4.Ajp13Connector" > port="8009" minProcessors="5" maxProcessors="75" > acceptCount="10" debug="0"/> > > The problem is that this connector is deprecated and probably will give > you an MBean exception. > > If you want to just verify the problem, you can try it out on an older > but still functional HTTP connector. Comment out the connector that > looks like: > <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" > port="8080" minProcessors="5" maxProcessors="75" > enableLookups="true" redirectPort="8443" > acceptCount="100" debug="0" connectionTimeout="20000" > useURIValidationHack="false" disableUploadTimeout="true" > /> > > And uncomment the one that looks like: > > <Connector > className="org.apache.catalina.connector.http.HttpConnector" > port="8083" minProcessors="5" maxProcessors="75" > enableLookups="true" redirectPort="8443" > acceptCount="10" debug="0" /> > > You might want to change the port to 8080 and/or change some of the > tuning parameters, max and minProcessors to be the same as they were on > your other connector. > > If you form parameters are preserved, then you know that it is the same > issue. > > Jeff Tulley ([EMAIL PROTECTED]) > (801)861-5322 > Novell, Inc., The Leading Provider of Net Business Solutions > http://www.novell.com > > >>> [EMAIL PROTECTED] 4/1/03 9:59:07 AM >>> > Ok. > > For configuration and some implementation, I am still a newbie here. > How > do you change the connector to a non-Coyote one? Which one would you > recomend? Where can I find it? > > Jeff Tulley wrote: > > > I just found out that this is a known problem with the Coyote > > connectors, both the HTTP connector and the JkHandler connector. > > There is some code not implemented or something, and there is already > a > > bug report in bugzilla. > > > > To verify if we are talking about the same thing, go back to using > an > > old non-Coyote connector and see if your form parameters > > are preserved across the login. > > > > This really needs to be fixed. You can vote on the bug, it is > #10229 > > > > Jeff Tulley ([EMAIL PROTECTED]) > > (801)861-5322 > > Novell, Inc., The Leading Provider of Net Business Solutions > > http://www.novell.com > > > > >>> [EMAIL PROTECTED] 4/1/03 8:40:36 AM >>> > > It returns "null". > > > > I noticed that it places all the POST/GET information into a session > to > > be > > re-submitted to the actual page after successful login. Know of a > way > > that I can > > access the session information to extract a specific string in it? > > > > Henning Heil wrote: > > > > > Hi Michael, > > > > > > ++++ Michael D. Kirkpatrick wrote on 01.04.2003 17:05 ++++ > > > > > > >I am not quite sure if this question is suitable for this mailing > > list. If > > > >not, please forgive me. > > > > > > > >[snip] > > > > > > > >So here is my question. How can I capture the original query > string > > or make > > > >the query string in web.xml dynamic? > > > > > > > in general I would not recommend to set the string in the web.xml. > > > first part of your question: you can read out any parameter of a > post > > or > > > get string by request.getParameter(String parametername); > > > second part: there are multiple ways to manipulate the request > > > parameters: java -> request.setAttribute(String attributename, > > String > > > value); or by hidden fields in html forms or with select-fields > > which > > > are submitted . . . > > > > > > I would suggest: > > > > > > read out the site the user is coming from with > > > > > > String mysite = request.getParameter("site"); > > > > > > (of course you have to add this to the string somewhere on the > > original > > > page) > > > > > > write it to newly generated links: > > > > > > out.println("passwordsubmitter.jsp?site=" + mysite); > > > > > > or sth like this . . . > > > > > > >I am also looking for mailing lists for the following: > > > > Struts Questions > > > > > > > there's one on the apache.org site I think -> struts . . . > > > > > > > General Java Questions > > > > J2EE Questions > > > > > > > no mailing but extremely cool & helpful people there and also > > mailing > > > mechanisms to keep track of your threads: > > > http://forums.java.sun.com/ > > > > > > >If anyone can point me in the right direction, it would be > greatly > > > >appreciated. > > > > > > > >Thanks in advance. > > > > > > > > > > > Have fun, > > > > > > Henning > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
