RequestDispatcher, wrapper, and file upload - ANSWER
Found the answer to my question.
The call to request.getRequestDispathcher(String aPath) works as it should.
However, this method represents a kind of 'back door', through which query
params may be added.
Since my wrappER doesn't override this method, it does a call forward to the
'wrappEE'. The wrappEE sees the query params, and saves them, but this info is
not made automatically visible to the wrappER. **The wrappER needs to do extra
work to ensure that such 'extra' query params are also made visible to it.**
Roughly, the wrapper should be something like this :
@Override public String getParameter(String aName){
//first try wrapper's internal version of the parameter map
//if not found, try super.getParameter(String), and see if it has any data
for aName
}
That way, when the JSP uses the wrappER, it will see the extra query params in
the usual way.
I have altered the code to reflect the above style, and it now works.
Regards,
John
Re: connection pool maxActive = 0 != unlimited in new version
On Fri, Mar 7, 2008 at 3:41 PM, william kinney [EMAIL PROTECTED] wrote: Hi, After some painful research and code digging, I found that in commons-pool versions 1.2 (ie 1.3 and 1.4), the logic for maxActive changed for unlimited. 0 no longer means unlimited as it did in 1.2 and previous versions. Correct. This was changed in commons pool 1.3 to address JIRA issues DBCP-113, POOL-22. This looks to be contradictory to commons-pool and tomcat documentation however (e.g. http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html ). This seems to effect tomcat versions 5.5.24-26. Are there plans to update said documentation, or is this an issue with commons-pool? Thanks for reporting this. The documentation update to reflect this change for DBCP 1.2.2 was incorrect. This issue is being tracked as DBCP-41 (reopened). The documentation fix will be applied and web site updated shortly. Phil - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
