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 pr
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'.
