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 b
Costin,
> > > - I have a
> > >
> > >
> > > 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:
> Costin,
>
> > - I have a
> >
> >
> > 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
Costin,
> - I have a
>
>
> 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 strange.
this t
On Wed, 26 Jun 2002, Kin-Man Chung wrote:
> That's true, but the value of those variables are still synchronized
> with the corresponding pageContext attributes at the locations
> specified by the spec, so using these variables before they are
> synchronized is meaningless.
>
> The spec as is to
> > > - in the same case, the 'a' variable is declared at the top
> > > of the file, even if it is AT_END. That brakes previous
> > > 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
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
> > 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 el
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
The generated code is:
a = (java.lang.Object) pageContext.findAttribute("a");
a = (java.lang.Object) pageContext.findAttribut
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 f
> 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 pat
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
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 w
Costin,
> How do we deal with nested tags of different type ? I don't have
> a test case, but I assume someone may have a NESTED tag
> 'foo' in 2 different tags, with different declared types ( String and
> Integer ). The current generator seems to not create { },
> and I'm not sure how this
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
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;
> }
>
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
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 scri
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 -
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.*;
Jan Luehe wrote:
> Hi Costin,
>
>
>>But there is still a problem - now if you have:
>>
>>
>>
>>
>>
>>
>>( i.e. the same variable name ), it will fail with duplicated declaration,
>>the code will be:
>> Object i;
>> ...
>> Object i;
>>
>>( id is nested ).
>
>
> The above code f
Hi Costin,
> But there is still a problem - now if you have:
>
>
>
>
>
>
> ( i.e. the same variable name ), it will fail with duplicated declaration,
> the code will be:
>Object i;
>...
>Object i;
>
> ( id is nested ).
The above code fragment compiles fine for me.
I
Many thanks Jan and Kin-Man.
But there is still a problem - now if you have:
( i.e. the same variable name ), it will fail with duplicated declaration,
the code will be:
Object i;
...
Object i;
( id is nested ).
As I mentioned, the 4.1.4 milestone doesn't have this pro
Hi Costin,
> More info:
>
> The page is:
>
> <%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic" %>
>
>
>
> Foo
>
>
>
> I get:
>
> a$jsp.java:75:25:75:25: Error: No entity named "id2" was found in this
> environment.
>
> And the generated code is:
> .
om directly ).
Costin
>
>
> > -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
> >
>
> 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-prin
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,
>
>
26 matches
Mail list logo
