Costin,
- I have a
bean:define id=a name=foo/
The generated code is:
a = (java.lang.Object) pageContext.findAttribute(a);
a = (java.lang.Object) pageContext.findAttribute(a);
a = (java.lang.Object) pageContext.findAttribute(a);
( i.e. 3 times the same line ).
Not a bug, but
On Thu, 27 Jun 2002, Jan Luehe wrote:
Costin,
- I have a
bean:define id=a name=foo/
The generated code is:
a = (java.lang.Object) pageContext.findAttribute(a);
a = (java.lang.Object) pageContext.findAttribute(a);
a = (java.lang.Object) pageContext.findAttribute(a);
( i.e.
Costin,
- I have a
bean:define id=a name=foo/
The generated code is:
a = (java.lang.Object) pageContext.findAttribute(a);
a = (java.lang.Object) pageContext.findAttribute(a);
a = (java.lang.Object) pageContext.findAttribute(a);
( i.e. 3 times the same line ).
On Thu, 27 Jun 2002, Jan Luehe wrote:
And I would bet most jsp implementations in use are doing exactly
what jasper1 is doing - and changing this will create big problems
( while still beeing non-compiant with the spec, and completely
counterintuitive )
But there also could be
I tried again, and it worked. There is still one error ( i.e. a page that
worked before but no longer does ), but that may be legitimate.
2 more problems:
- I have a
bean:define id=a name=foo/
The generated code is:
a = (java.lang.Object) pageContext.findAttribute(a);
a = (java.lang.Object)
On Wed, 26 Jun 2002, Jan Luehe wrote:
- in the same case, the 'a' variable is declared at the top
of the file, even if it is AT_END. That brakes previous iterate
that used the 'a' id. I believe this is a bug.
According to the spec, the scope of an AT_END variable spans
from the end
- in the same case, the 'a' variable is declared at the top
of the file, even if it is AT_END. That brakes previous iterate
that used the 'a' id. I believe this is a bug.
According to the spec, the scope of an AT_END variable spans
from the end element of the tag exposing it to
Costin,
On Fri, 21 Jun 2002, Kin-Man Chung wrote:
Use of scripting varibles in nested tag never work before, so obviously
no body uses it much. I think the whole scripting variable in JSP1.2 is
poorly designed, and not well understood.
The failures are from an app that worked
On Mon, 24 Jun 2002, Kin-Man Chung wrote:
Use of scripting varibles in nested tag never work before, so obviously
no body uses it much. I think the whole scripting variable in JSP1.2 is
poorly designed, and not well understood.
The failures are from an app that worked perfectly
My problem is that code that worked with jasper1 no longer works with
jasper2.
And I believe the use case is valid and within the spec, and quite
common.
The latest failure is just 2 iterate tags and a condition tag -
I think it should work.
Costin
With the Jan's patch last
On Mon, 24 Jun 2002, Kin-Man Chung wrote:
With the Jan's patch last Friday, jasper 2 should handle those cases
that used to work for japser1, as well as those those that cannot be
handled by jasper1. If this is not the case, please let me know.
The current failing case is ( used to work
Costin,
If those variable declaration problems are fixed, I'll release a new
4.1.6 milestone as soon as I can fix the JNDI problems.
Not yet...
I attached the failed jsp.
Costin
[...]
%@ page language=java %
%@
Hi Costin,
But there is still a problem - now if you have:
logic:iterate id='i'
/logic:iterate
logic:iterate id='i'
/logic:iterate
( i.e. the same variable name ), it will fail with duplicated declaration,
the code will be:
Object i;
...
Object i;
( id is
Jan Luehe wrote:
Hi Costin,
But there is still a problem - now if you have:
logic:iterate id='i'
/logic:iterate
logic:iterate id='i'
/logic:iterate
( i.e. the same variable name ), it will fail with duplicated declaration,
the code will be:
Object i;
...
Object i;
(
On Fri, 21 Jun 2002, Remy Maucherat wrote:
If those variable declaration problems are fixed, I'll release a new
4.1.6 milestone as soon as I can fix the JNDI problems.
Not yet...
I attached the failed jsp.
Costin
package JspServ;
import javax.servlet.*;
import javax.servlet.http.*;
Thanks, I'll try it out.
I'm a bit worried here - most of the stuff is pretty basic and
common use of tags. Watchdog and the test suite was supposed
to detect that withou any problems.
I'll vote for 'alpha' status for the next build,
and I hope more people will check their apps against it -
Costin,
I'm a bit worried here - most of the stuff is pretty basic and
common use of tags. Watchdog and the test suite was supposed
to detect that withou any problems.
Use of scripting varibles in nested tag never work before, so obviously
no body uses it much. I think the whole
On Fri, 21 Jun 2002, Kin-Man Chung wrote:
Use of scripting varibles in nested tag never work before, so obviously
no body uses it much. I think the whole scripting variable in JSP1.2 is
poorly designed, and not well understood.
The failures are from an app that worked perfectly fine with
On Fri, 21 Jun 2002, Jan Luehe wrote:
the current approach should be able to handle a NESTED 'foo' in 2
different tags, with different declared types, as long as one tag
isn't nested inside the other. The current approach will generate code
like this:
{
Integer foo;
}
{
Hi Costin,
More info:
The page is:
%@ taglib uri=/WEB-INF/struts-logic.tld prefix=logic %
logic:iterate id=id1 name=name1 property=prop1
logic:iterate id=id2 name=name2 property=prop2
Foo
/logic:iterate
/logic:iterate
I get:
a$jsp.java:75:25:75:25: Error:
Many thanks Jan and Kin-Man.
But there is still a problem - now if you have:
logic:iterate id='i'
/logic:iterate
logic:iterate id='i'
/logic:iterate
( i.e. the same variable name ), it will fail with duplicated declaration,
the code will be:
Object i;
...
Object i;
( id
for a few extra {}'s?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 18 June 2002 06:44
To: Tomcat Developers List; Kin-Man Chung
Subject: Re: Jasper2: serious problem with tag declarations
On Mon, 17 Jun 2002, Kin-Man Chung wrote:
Costin,
I am not aware
Date: Tue, 18 Jun 2002 11:04:10 +0100
From: [EMAIL PROTECTED]
Subject: RE: Jasper2: serious problem with tag declarations
To: [EMAIL PROTECTED]
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.0.5762.3
Content-transfer-encoding: quoted-printable
Content-class: urn:content
PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 18 June 2002 06:44
To: Tomcat Developers List; Kin-Man Chung
Subject: Re: Jasper2: serious problem with tag declarations
On Mon, 17 Jun 2002, Kin-Man Chung wrote:
Costin,
I am not aware that id attribute is handled differently
24 matches
Mail list logo
