On 11/12/2012 22:00, Christopher Schultz wrote:
> Can you start a new thread with a different subject? Something
> like "Tomcat prefers TC JSTL implementation to webapp-packaged one"
> and ask about it? I know there are some folks here who can describe
> how that's supposed to work. Once you've got
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Juha,
On 12/11/12 3:29 PM, Juha Laiho wrote:
> first, thanks for your answers, and also for the nits, they did
> hit some good points. Then on with some answers to the further
> questions you placed;
>
>
> On Tue, Dec 11, 2012 at 12:58 AM, Christ
Chirs,
first, thanks for your answers, and also for the nits, they did hit
some good points. Then on with some answers to the further
questions you placed;
On Tue, Dec 11, 2012 at 12:58 AM, Christopher Schultz
wrote:
> On 12/10/12 5:40 PM, Christopher Schultz wrote:
>> I'll take a look. You def
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Juha,
On 12/10/12 5:40 PM, Christopher Schultz wrote:
> On 12/10/12 4:14 PM, Juha Laiho wrote:
>
>> Any comments? Did I come across a but in Tomcat, or a "lucky
>> bug" in the application (i.e. something that worked by luck in
>> the previous conta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Juha,
On 12/10/12 4:14 PM, Juha Laiho wrote:
> I encountered an odd situation with request dispatching.
>
> In short, if the same request is first redirected using servlet
> API RequestDispatcher.forward(), and then via JSTL c:redirect using
> a re
Hello,
I encountered an odd situation with request dispatching.
Environment:
Java platform: Oracle 1.7 (7u9)
Tomcat platform: 7.0.32, 7.0.33
Operating systems: Linux, Windows (likely irrelevant)
Browser: Firefox 17
In short, if the same request is first redirected using servlet API
RequestDispat
