You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Torsten Fohrer <to...@dcsi.de> on 2003/08/13 13:49:53 UTC
[Q] Different handling tagfiles and normal tags classes
Tagfiles and tags get a jspcontext from the container at runtime.
Tags get directly a normal pagecontext reference from the current jsp page.
TagFiles instead get a wrapper around the pagecontext that wraps all
set/get/findAttribute for the page scope to a local set of stored
attributes.
When i declare an attribute in jsp with page scope, i never see it in a tag
file, but i see it in a 'normal' tag.
Interesting files:
org.apache.jasper.runtime.JspContextWrapper -> see
getAttribute(String)/getAttribute(String/int)
org.apache.jasper.compiler.Generator -> search for setJspContext
Is there a reason why, i don't know?
Best greeting
Torsten Fohrer
Re: [Q] Different handling tagfiles and normal tags classes
Posted by Bill Barker <wb...@wilshire.com>.
----- Original Message -----
From: "Torsten Fohrer" <TF...@t-online.de>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Sent: Wednesday, August 13, 2003 9:32 PM
Subject: Re: [Q] Different handling tagfiles and normal tags classes
>
> What about a seperate TAGFILE_SCOPE?
Not something that is under Tomcat's control. You'd need to suggest it to
jsp-spec-comments@eng.sun.com.
>
> Best greeting
> Torsten Fohrer
>
> On Wednesday 13 August 2003 22:02, you wrote:
> > Torsten,
> >
> > see JSP.8.3 ("Semantics of Tag Files"), 3rd bullet:
> >
> > For each invocation to the tag, the JSP Context Wrapper must present
a
> > clean page scope containing no initial elements. All scopes other
than
> > the page scope must be identical to those in the Invoking JSP Context
> > and must be modified accordingly when updates are made to those
scopes
> > in the JSP Context Wrapper. Any modifications to the page scope,
> > however, must not affect the Invoking JSP Context.
> >
> > Hope this helps.
> >
> > Jan
> >
> > Torsten Fohrer wrote:
> > > Tagfiles and tags get a jspcontext from the container at runtime.
> > > Tags get directly a normal pagecontext reference from the current jsp
> > > page. TagFiles instead get a wrapper around the pagecontext that wraps
> > > all set/get/findAttribute for the page scope to a local set of stored
> > > attributes.
> > > When i declare an attribute in jsp with page scope, i never see it in
a
> > > tag file, but i see it in a 'normal' tag.
> > >
> > > Interesting files:
> > > org.apache.jasper.runtime.JspContextWrapper -> see
> > > getAttribute(String)/getAttribute(String/int)
> > > org.apache.jasper.compiler.Generator -> search for setJspContext
> > >
> > > Is there a reason why, i don't know?
> > >
> > > Best greeting
> > > Torsten Fohrer
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
Re: [Q] Different handling tagfiles and normal tags classes
Posted by Torsten Fohrer <TF...@t-online.de>.
What about a seperate TAGFILE_SCOPE?
Best greeting
Torsten Fohrer
On Wednesday 13 August 2003 22:02, you wrote:
> Torsten,
>
> see JSP.8.3 ("Semantics of Tag Files"), 3rd bullet:
>
> For each invocation to the tag, the JSP Context Wrapper must present a
> clean page scope containing no initial elements. All scopes other than
> the page scope must be identical to those in the Invoking JSP Context
> and must be modified accordingly when updates are made to those scopes
> in the JSP Context Wrapper. Any modifications to the page scope,
> however, must not affect the Invoking JSP Context.
>
> Hope this helps.
>
> Jan
>
> Torsten Fohrer wrote:
> > Tagfiles and tags get a jspcontext from the container at runtime.
> > Tags get directly a normal pagecontext reference from the current jsp
> > page. TagFiles instead get a wrapper around the pagecontext that wraps
> > all set/get/findAttribute for the page scope to a local set of stored
> > attributes.
> > When i declare an attribute in jsp with page scope, i never see it in a
> > tag file, but i see it in a 'normal' tag.
> >
> > Interesting files:
> > org.apache.jasper.runtime.JspContextWrapper -> see
> > getAttribute(String)/getAttribute(String/int)
> > org.apache.jasper.compiler.Generator -> search for setJspContext
> >
> > Is there a reason why, i don't know?
> >
> > Best greeting
> > Torsten Fohrer
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [Q] Different handling tagfiles and normal tags classes
Posted by Torsten Fohrer <TF...@t-online.de>.
What about a seperate TAGFILE_SCOPE?
Best greeting
Torsten Fohrer
On Wednesday 13 August 2003 22:02, you wrote:
> Torsten,
>
> see JSP.8.3 ("Semantics of Tag Files"), 3rd bullet:
>
> For each invocation to the tag, the JSP Context Wrapper must present a
> clean page scope containing no initial elements. All scopes other than
> the page scope must be identical to those in the Invoking JSP Context
> and must be modified accordingly when updates are made to those scopes
> in the JSP Context Wrapper. Any modifications to the page scope,
> however, must not affect the Invoking JSP Context.
>
> Hope this helps.
>
> Jan
>
> Torsten Fohrer wrote:
> > Tagfiles and tags get a jspcontext from the container at runtime.
> > Tags get directly a normal pagecontext reference from the current jsp
> > page. TagFiles instead get a wrapper around the pagecontext that wraps
> > all set/get/findAttribute for the page scope to a local set of stored
> > attributes.
> > When i declare an attribute in jsp with page scope, i never see it in a
> > tag file, but i see it in a 'normal' tag.
> >
> > Interesting files:
> > org.apache.jasper.runtime.JspContextWrapper -> see
> > getAttribute(String)/getAttribute(String/int)
> > org.apache.jasper.compiler.Generator -> search for setJspContext
> >
> > Is there a reason why, i don't know?
> >
> > Best greeting
> > Torsten Fohrer
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [Q] Different handling tagfiles and normal tags classes
Posted by Jan Luehe <Ja...@Sun.COM>.
Torsten,
see JSP.8.3 ("Semantics of Tag Files"), 3rd bullet:
For each invocation to the tag, the JSP Context Wrapper must present a
clean page scope containing no initial elements. All scopes other than
the page scope must be identical to those in the Invoking JSP Context
and must be modified accordingly when updates are made to those scopes
in the JSP Context Wrapper. Any modifications to the page scope,
however, must not affect the Invoking JSP Context.
Hope this helps.
Jan
Torsten Fohrer wrote:
> Tagfiles and tags get a jspcontext from the container at runtime.
> Tags get directly a normal pagecontext reference from the current jsp page.
> TagFiles instead get a wrapper around the pagecontext that wraps all
> set/get/findAttribute for the page scope to a local set of stored
> attributes.
> When i declare an attribute in jsp with page scope, i never see it in a tag
> file, but i see it in a 'normal' tag.
>
> Interesting files:
> org.apache.jasper.runtime.JspContextWrapper -> see
> getAttribute(String)/getAttribute(String/int)
> org.apache.jasper.compiler.Generator -> search for setJspContext
>
> Is there a reason why, i don't know?
>
> Best greeting
> Torsten Fohrer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
Re: [Q] Different handling tagfiles and normal tags classes
Posted by Jan Luehe <Ja...@Sun.COM>.
Torsten,
see JSP.8.3 ("Semantics of Tag Files"), 3rd bullet:
For each invocation to the tag, the JSP Context Wrapper must present a
clean page scope containing no initial elements. All scopes other than
the page scope must be identical to those in the Invoking JSP Context
and must be modified accordingly when updates are made to those scopes
in the JSP Context Wrapper. Any modifications to the page scope,
however, must not affect the Invoking JSP Context.
Hope this helps.
Jan
Torsten Fohrer wrote:
> Tagfiles and tags get a jspcontext from the container at runtime.
> Tags get directly a normal pagecontext reference from the current jsp page.
> TagFiles instead get a wrapper around the pagecontext that wraps all
> set/get/findAttribute for the page scope to a local set of stored
> attributes.
> When i declare an attribute in jsp with page scope, i never see it in a tag
> file, but i see it in a 'normal' tag.
>
> Interesting files:
> org.apache.jasper.runtime.JspContextWrapper -> see
> getAttribute(String)/getAttribute(String/int)
> org.apache.jasper.compiler.Generator -> search for setJspContext
>
> Is there a reason why, i don't know?
>
> Best greeting
> Torsten Fohrer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org