Hello,
I never doubted that Tomcat 5.5 supported JSPs using Java5.0's new
syntax and features, until I read the following in the docs:
The Java compiler from Eclipse JDT in included as the default compiler.
[...] This new compiler will be updated to support the Java 5 syntax as
soon as possible.
Hello Mark,
Thank you, and William & Remy for looking at this issue.
The JSP in question has several expressions. I thought the following in
the JSP 2.0 spec (section JSP.1.12.3) would apply:
Expressions are evaluated left-to-right in the JSP page.
This does not apply when expressions are
>> Expressions are evaluated left-to-right in the JSP page.
>>
>> This does not apply when expressions are used in attributes?
>>
>
> well, no. however section 1.14 may apply.
>
> The interpretation of all actions start by evaluating the values given to
> its attributes left to right, and assi
Hello Nikita,
I only recently joined this list so I might have missed your first
message (actually I subscribed that same day).
I think what you wrote should help. If you are going to try it out,
please let us know the result.
Other than that, all I can think of to decrease heap space is to t
Hello,
I'm looking into an issue we ran into when upgrading from Tomcat 4.1 to
Tomcat 5.5.
The time returned by the HttpSession.getLastAccessTime method seems to
have changed.
We believe it should return the time of the previous request from the
same client. It did in Tomcat 4.1. It did so no mat
I wrote and what the spec
writes?
I tried searching the mailing lists about it but could not find any
discussion about it.
Thank again for the reply,
Dies
Jan Luehe wrote:
> Hi Dies,
>
> Dies Koper wrote On 08/16/06 05:28,:
>
>> Hello,
>>
>> I'm looking in
ll
in agreement on this.
I suppose they changed their minds a few times on what this method
should do and that led to the ambiguity. Thank you for double-checking,
I'm looking forward to hearing their reply.
Regards,
Dies Koper
Hello Filip,
In my application I used a pageContext.include which once threw a
JasperException (ServletException) while it was supposed to (according
to the spec) propagate the IOException as-is.
I noticed that setting the "deployment" init param in conf\web.xml to
"false" made it propagate th
