On 2/7/2018 4:37 PM, M. Manna wrote:
If this doesn’t cause pain, I would do the following:
1) Replace all in-body scriptlets and use JSTL core tags in offending
JSPs. Most of the codebloats are caused by using intermediate scriptlets
e.g.
<% if (foo.bar() == jack.jill() ) { %>
// lots of jsp
If this doesn’t cause pain, I would do the following:
1) Replace all in-body scriptlets and use JSTL core tags in offending
JSPs. Most of the codebloats are caused by using intermediate scriptlets
e.g.
<% if (foo.bar() == jack.jill() ) { %>
// lots of jsp code
<%} else <%{ %>
2) use all your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jan,
On 2/7/18 3:13 PM, Mark Thomas wrote:
> On 07/02/18 19:19, Jan Tosovsky wrote:
>> Dear All,
>>
>> I've updated ancient tomcat to 8.0.49 and deployed app now throws
>> '65535 bytes limit' exception for certain JSPs.
>>
>> Following this
On 07/02/18 19:19, Jan Tosovsky wrote:
> Dear All,
>
> I've updated ancient tomcat to 8.0.49 and deployed app now throws '65535
> bytes limit' exception for certain JSPs.
>
> Following this (older) thread
> https://stackoverflow.com/questions/5484253/jspservice-is-exceeding-the-6553
>
Dear All,
I've updated ancient tomcat to 8.0.49 and deployed app now throws '65535
bytes limit' exception for certain JSPs.
Following this (older) thread
https://stackoverflow.com/questions/5484253/jspservice-is-exceeding-the-6553
5-bytes-limit I changed that mappedfile parameter, but it didn't
