http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26444
It won't be fixed. You'll need to send an email to the jsp feedback group to
address this. (The email is on the cover page of the spec)
-Tim
Antonio Fiol Bonnín wrote:
I don't agree or disagree.
But this will break many apps. Mine for exa
I don't agree or disagree.
But this will break many apps. Mine for example.
Couldn't that be detected at jsp->java time? I believe that would not
hurt that much. In fact... (not having read the spec) ...what's the
whole point of creating the object at that time? IMHO, if it doesn't
exist, just
Tim
I realise the spec says it's ok to use new, however it's a fairly
restrictive implementation.
In fact it means that you can only pass objects through to the JSP page
that have an empty constructor. It is no longer 'all objects'.
Is the performance hit of using reflection 'that much'?
Chee
Sehr geehrte Damen und Herren
Wir haben Ihre Nachricht dankend erhalten und werden diese so schnell wie möglich
bearbeiten.
Mit "internetten" Grüssen
Ihr Shoppingcity.ch-Team
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For a
The spec says using new() is OK. So tomcat does since it is *much* faster
than reflection.
-Tim
Rupert Jones wrote:
Hi there
[Running Tomcat 5.0.19]
I have a servlet which forwards a Boolean object resource
(request.setAttribute("someBoolean", someBoolean);) on to a jsp page. As
you know the
