You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Miles Sabin <ms...@cromwellmedia.co.uk> on 2000/01/10 13:53:19 UTC
Any interest in comments on the servlet 2.2 API?
A while ago I mailed a bunch of comments on the 2.2 API to Sun
(mostly on buffering and localization). I didn't get any
feedback and none of them appear to have been taken up for the
final 2.2 spec.
I don't know to what extent the current spec is carved in stone
now, but I still think the issues are worthy of attention.
Would it be of any interest to readers of this list? If so I'll
repost the comments here.
Cheers,
Miles
--
Miles Sabin Cromwell Media
Internet Systems Architect 5/6 Glenthorne Mews
+44 (0)20 8817 4030 London, W6 0LJ, England
msabin@cromwellmedia.com http://www.cromwellmedia.com/
Re: Any interest in comments on the servlet 2.2 API?
Posted by Eduardo Pelegri-Llopart <Ed...@eng.sun.com>.
you are right. It is a left-over from JSP 1.0, and even then it was
wrong. Will clarify it.
Thanks for catching this.
- eduard/o
Danno Ferrin wrote:
>
> p. 66, under the description for the name attribute.
>
> ----- Original Message -----
> From: "Eduardo Pelegri-Llopart" <Ed...@eng.sun.com>
> To: <to...@jakarta.apache.org>
> Cc: <Ed...@eng.sun.com>
> Sent: Friday, January 14, 2000 12:37 AM
> Subject: Re: Any interest in comments on the servlet 2.2 API?
>
> > Yes, we will have something like this.
> >
> > I think we have already covered the first 2. I need to send something
> > about the last one. But, where is the parenthetical "only jsp:useBean"
> > comment? The only one I can find in my copy of the spec says
> > "(>>usually<< via a useBean action)", not >>only<< [[yes, it should have
> > said jsp:useBean, not just useBean]]
> >
> > - eduard/o
> >
> > Danno Ferrin wrote:
> > >
> > > How about a normative addendum, released in paralell with the specs?
> Three
> > > issues come to mind immediatly that should be addressed there.
> > >
> > > * relative nested includes. Having the includes relative to the
> translation
> > > element that holds the <%@include %> directive seems to be a popular
> choice.
> > > Relative to the original translation unit seems ok by the spec too,
> although
> > > it is not quite as polular (but you can do some cool tricks with it).
> > >
> > > * XML document not being intermixed with a JSP document.
> > >
> > > *getProperty... remove or elabortate on the "only jsp:useBean"
> parentetical
> > > comment.
> > >
> > > --Danno
> > >
> >
> > ---------------------------------------------------------------------
> > 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: Any interest in comments on the servlet 2.2 API?
Posted by Danno Ferrin <sh...@earthlink.net>.
p. 66, under the description for the name attribute.
----- Original Message -----
From: "Eduardo Pelegri-Llopart" <Ed...@eng.sun.com>
To: <to...@jakarta.apache.org>
Cc: <Ed...@eng.sun.com>
Sent: Friday, January 14, 2000 12:37 AM
Subject: Re: Any interest in comments on the servlet 2.2 API?
> Yes, we will have something like this.
>
> I think we have already covered the first 2. I need to send something
> about the last one. But, where is the parenthetical "only jsp:useBean"
> comment? The only one I can find in my copy of the spec says
> "(>>usually<< via a useBean action)", not >>only<< [[yes, it should have
> said jsp:useBean, not just useBean]]
>
> - eduard/o
>
> Danno Ferrin wrote:
> >
> > How about a normative addendum, released in paralell with the specs?
Three
> > issues come to mind immediatly that should be addressed there.
> >
> > * relative nested includes. Having the includes relative to the
translation
> > element that holds the <%@include %> directive seems to be a popular
choice.
> > Relative to the original translation unit seems ok by the spec too,
although
> > it is not quite as polular (but you can do some cool tricks with it).
> >
> > * XML document not being intermixed with a JSP document.
> >
> > *getProperty... remove or elabortate on the "only jsp:useBean"
parentetical
> > comment.
> >
> > --Danno
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
Re: Any interest in comments on the servlet 2.2 API?
Posted by Eduardo Pelegri-Llopart <Ed...@eng.sun.com>.
Yes, we will have something like this.
I think we have already covered the first 2. I need to send something
about the last one. But, where is the parenthetical "only jsp:useBean"
comment? The only one I can find in my copy of the spec says
"(>>usually<< via a useBean action)", not >>only<< [[yes, it should have
said jsp:useBean, not just useBean]]
- eduard/o
Danno Ferrin wrote:
>
> How about a normative addendum, released in paralell with the specs? Three
> issues come to mind immediatly that should be addressed there.
>
> * relative nested includes. Having the includes relative to the translation
> element that holds the <%@include %> directive seems to be a popular choice.
> Relative to the original translation unit seems ok by the spec too, although
> it is not quite as polular (but you can do some cool tricks with it).
>
> * XML document not being intermixed with a JSP document.
>
> *getProperty... remove or elabortate on the "only jsp:useBean" parentetical
> comment.
>
> --Danno
>
Re: Any interest in comments on the servlet 2.2 API?
Posted by Assaf Arkin <ar...@exoffice.com>.
Stefano Mazzocchi wrote:
>
> Assaf Arkin wrote:
> >
> > Was there any discussion regarding producing results through the SAX API
> > instead of directly printing to the writer?
>
> Don't worry, the part of "XML pain in the ass" dude in the servlet.next
> play is already taken by me :)
>
> You guys (expecially Eduardo) have been warned.
So that's being taken care of :-)
> Arkin, I'll try hard to make all the XSP issues incorporated into JSP. I
> don't really care if I loose control on the spec, the name or those
> stuff, but I won't give up until all the XML-related problems are
> solved.
+1
> Hard, I know. Will probably create a lot of "back-incompatibility
> friction", but I promise to take my diplomacy skill out of my closet :)
Can't make the omlete without breaking the eggs.
arkin
> And, also, I'm pushing Sun to change a little the JCP so that it's
> splitted into three things:
>
> 1) a "people house" -> a public mail list (open to everyone)
> 2) a "company house" -> a company mail list (closed)
> 3) a "government" -> a mail list composed by 20 people, x from the
> people, 20-x from the companies. And one elected spec governor.
>
> This way, we get better public coverage and a better specification
> process.
>
> --
> Stefano Mazzocchi One must still have chaos in oneself to be
> able to give biX-Mozilla-Status: 0009
> <st...@apache.org> Friedrich Nietzsche
> --------------------------------------------------------------------
> Come to the first official Apache Software Foundation Conference!
> ------------------------- http://ApacheCon.Com ---------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Any interest in comments on the servlet 2.2 API?
Posted by Assaf Arkin <ar...@exoffice.com>.
Eduardo Pelegri-Llopart wrote:
>
> See intermixed...
>
> Stefano Mazzocchi wrote:
> >
> > Assaf Arkin wrote:
> > >
> > > Was there any discussion regarding producing results through the SAX API
> > > instead of directly printing to the writer?
>
> A number of people have suggested things in this space in different
> public and private conversations. But I think the most concrete ideas
> I've seen posted were in the cocoon space. I am not tracking very well
> some forums like xml-dev, though.
Cocoon was implied. No need to spell it out :-)
arkin
>
> > Don't worry, the part of "XML pain in the ass" dude in the servlet.next
> > play is already taken by me :)
>
> Sure thing, that is what I expect you to do. And you won't be the only
> one :-)
>
> > You guys (expecially Eduardo) have been warned.
> >
> > Arkin, I'll try hard to make all the XSP issues incorporated into JSP. I
> > don't really care if I loose control on the spec, the name or those
> > stuff, but I won't give up until all the XML-related problems are
> > solved.
> >
> > Hard, I know. Will probably create a lot of "back-incompatibility
> > friction", but I promise to take my diplomacy skill out of my closet :)
> >
> > And, also, I'm pushing Sun to change a little the JCP so that it's
> > splitted into three things:
> >
> > 1) a "people house" -> a public mail list (open to everyone)
> > 2) a "company house" -> a company mail list (closed)
> > 3) a "government" -> a mail list composed by 20 people, x from the
> > people, 20-x from the companies. And one elected spec governor.
>
> I'm all for having feedback from as many sources as possible.
>
> I am a bit more slow/cautious/whatever than some of you, so it may take
> me a bit longer to post specific suggestions for things like "how to run
> the process". But I hear you, and you can always send me mail, and I
> will try to reply to it prompty (yes, I still owe a reply to Sam -
> sorry!).
>
> The big picture I have is one of several forums feeding requirements,
> ideas, comments into an expert group that can, with some regularity,
> generate documents to the forums for further feedback. Specific forums
> that are interesting include open-source forums based on tomcat, cocoon,
> turbine, as well as vendor-specific forums in this space (some of these
> vendors are also using Open Source licenses).
>
> I am planning to put some ideas together in the near future and run them
> by key people inside and outside of Sun and then send a suggestion (not
> final!) to this forum. Don't expect proposals (from me) that are not
> compatible with the JCP. The spec lead has a fair amount of flexibility
> in how to run the process, so I think that most concerns can be
> accomodated, but things like "elected spec governor" are not part of
> this flexibility. Sorry, but I want to spend my cycles in things I can
> affect effectively, and changing the basic parameters of JCP is not one
> of them.
>
> Note that we are very early in the JCP process, the JSR I sent around
> tomcat-dev is not even a formal public document. To be fair to all the
> people in the Java platform we need to give them time to respond, and
> some of them react a bit slower than your typical tomcat-dev
> participant. But, given time constraints, we will have to do some
> things in parallel.
>
> Back to Stefano's 1-2-3 list, I am don't understand why 2) and 3) are
> separate. I have always had representatives of big companies, small
> companies, and plain lone individuals in my expert groups; as long as
> they are good team players and have good ideas, they are all welcome,
> appreciated, and influential.
>
> - eduard/o
>
> > This way, we get better public coverage and a better specification
> > process.
> >
> > --
> > Stefano Mazzocchi One must still have chaos in oneself to be
> > able to give birth to a dancing star.
> > <st...@apache.org> Friedrich Nietzsche
> > --------------------------------------------------------------------
> > Come to the first official Apache Software Foundation Conference!
> > ------------------------- http://ApacheCon.Com ---------------------
> >
> > ---------------------------------------------------------------------
> > 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: Any interest in comments on the servlet 2.2 API?
Posted by Eduardo Pelegri-Llopart <Ed...@eng.sun.com>.
See intermixed...
Stefano Mazzocchi wrote:
>
> Assaf Arkin wrote:
> >
> > Was there any discussion regarding producing results through the SAX API
> > instead of directly printing to the writer?
A number of people have suggested things in this space in different
public and private conversations. But I think the most concrete ideas
I've seen posted were in the cocoon space. I am not tracking very well
some forums like xml-dev, though.
> Don't worry, the part of "XML pain in the ass" dude in the servlet.next
> play is already taken by me :)
Sure thing, that is what I expect you to do. And you won't be the only
one :-)
> You guys (expecially Eduardo) have been warned.
>
> Arkin, I'll try hard to make all the XSP issues incorporated into JSP. I
> don't really care if I loose control on the spec, the name or those
> stuff, but I won't give up until all the XML-related problems are
> solved.
>
> Hard, I know. Will probably create a lot of "back-incompatibility
> friction", but I promise to take my diplomacy skill out of my closet :)
>
> And, also, I'm pushing Sun to change a little the JCP so that it's
> splitted into three things:
>
> 1) a "people house" -> a public mail list (open to everyone)
> 2) a "company house" -> a company mail list (closed)
> 3) a "government" -> a mail list composed by 20 people, x from the
> people, 20-x from the companies. And one elected spec governor.
I'm all for having feedback from as many sources as possible.
I am a bit more slow/cautious/whatever than some of you, so it may take
me a bit longer to post specific suggestions for things like "how to run
the process". But I hear you, and you can always send me mail, and I
will try to reply to it prompty (yes, I still owe a reply to Sam -
sorry!).
The big picture I have is one of several forums feeding requirements,
ideas, comments into an expert group that can, with some regularity,
generate documents to the forums for further feedback. Specific forums
that are interesting include open-source forums based on tomcat, cocoon,
turbine, as well as vendor-specific forums in this space (some of these
vendors are also using Open Source licenses).
I am planning to put some ideas together in the near future and run them
by key people inside and outside of Sun and then send a suggestion (not
final!) to this forum. Don't expect proposals (from me) that are not
compatible with the JCP. The spec lead has a fair amount of flexibility
in how to run the process, so I think that most concerns can be
accomodated, but things like "elected spec governor" are not part of
this flexibility. Sorry, but I want to spend my cycles in things I can
affect effectively, and changing the basic parameters of JCP is not one
of them.
Note that we are very early in the JCP process, the JSR I sent around
tomcat-dev is not even a formal public document. To be fair to all the
people in the Java platform we need to give them time to respond, and
some of them react a bit slower than your typical tomcat-dev
participant. But, given time constraints, we will have to do some
things in parallel.
Back to Stefano's 1-2-3 list, I am don't understand why 2) and 3) are
separate. I have always had representatives of big companies, small
companies, and plain lone individuals in my expert groups; as long as
they are good team players and have good ideas, they are all welcome,
appreciated, and influential.
- eduard/o
> This way, we get better public coverage and a better specification
> process.
>
> --
> Stefano Mazzocchi One must still have chaos in oneself to be
> able to give birth to a dancing star.
> <st...@apache.org> Friedrich Nietzsche
> --------------------------------------------------------------------
> Come to the first official Apache Software Foundation Conference!
> ------------------------- http://ApacheCon.Com ---------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Any interest in comments on the servlet 2.2 API?
Posted by Stefano Mazzocchi <st...@apache.org>.
Assaf Arkin wrote:
>
> Was there any discussion regarding producing results through the SAX API
> instead of directly printing to the writer?
Don't worry, the part of "XML pain in the ass" dude in the servlet.next
play is already taken by me :)
You guys (expecially Eduardo) have been warned.
Arkin, I'll try hard to make all the XSP issues incorporated into JSP. I
don't really care if I loose control on the spec, the name or those
stuff, but I won't give up until all the XML-related problems are
solved.
Hard, I know. Will probably create a lot of "back-incompatibility
friction", but I promise to take my diplomacy skill out of my closet :)
And, also, I'm pushing Sun to change a little the JCP so that it's
splitted into three things:
1) a "people house" -> a public mail list (open to everyone)
2) a "company house" -> a company mail list (closed)
3) a "government" -> a mail list composed by 20 people, x from the
people, 20-x from the companies. And one elected spec governor.
This way, we get better public coverage and a better specification
process.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give biX-Mozilla-Status: 0009
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Come to the first official Apache Software Foundation Conference!
------------------------- http://ApacheCon.Com ---------------------
Re: Any interest in comments on the servlet 2.2 API?
Posted by Stefano Mazzocchi <st...@apache.org>.
Assaf Arkin wrote:
>
> Was there any discussion regarding producing results through the SAX API
> instead of directly printing to the writer?
Don't worry, the part of "XML pain in the ass" dude in the servlet.next
play is already taken by me :)
You guys (expecially Eduardo) have been warned.
Arkin, I'll try hard to make all the XSP issues incorporated into JSP. I
don't really care if I loose control on the spec, the name or those
stuff, but I won't give up until all the XML-related problems are
solved.
Hard, I know. Will probably create a lot of "back-incompatibility
friction", but I promise to take my diplomacy skill out of my closet :)
And, also, I'm pushing Sun to change a little the JCP so that it's
splitted into three things:
1) a "people house" -> a public mail list (open to everyone)
2) a "company house" -> a company mail list (closed)
3) a "government" -> a mail list composed by 20 people, x from the
people, 20-x from the companies. And one elected spec governor.
This way, we get better public coverage and a better specification
process.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Come to the first official Apache Software Foundation Conference!
------------------------- http://ApacheCon.Com ---------------------
Re: Any interest in comments on the servlet 2.2 API?
Posted by Eduardo Pelegri-Llopart <Ed...@eng.sun.com>.
I think that:
> * a command line tool, JSP->servlet (already in the TODO list)
and
> * removing the XML notation from the standard JSP syntax
> thus brining it in line with the spec.
make a lot of sense to do in the main branch right away.
These next ones:
> and JSP<->(XML of the JSP) (uses the first command line, just
> with diffrent JSPParseEventListener subclasses)
> * adding an adapter/code bridge that eats SAX parse events
> and feeds them to a JSPParseEveltListener
> * code to reset the parse mode of a translation unit into XML
> mode if it sees a properly formed jsp:root element. So a "plain"
> jsp could include a JSP in the XML syntax and vice versa, thus
> requiring that only individual translation units (usually files)
> need to be consistant as to wether or not they are XML or "plain"
> JSP.
may be worth prototpying first in a separate branch to get an idea of
what is their performance cost (translation time). The JSP 1.1 spec
really does not need them since there is no requirement that the
equivalent XML doc can be given to the JSP container, but it would be
great to understand these issues when we talk about them in the dot.next
spec.
- eduard/o
Danno Ferrin wrote:
>
> Actually, once I get settlened from my move I am plannig on presenting a
> proposal to add full XML support to jasper. From what I have read from the
> standard and what Edward(o) has said the XML version and the "normal"
> version of a JSP document are paralell and not co-existing in the same
> instantiation. Once I get my ducks in a row I'll start that, and that is
> primarily what the second bullet represents.
>
> Roughly what I plan on is:
> * a command line tool, JSP->servlet (already in the TODO list)
> and JSP<->(XML of the JSP) (uses the first command line, just
> with diffrent JSPParseEventListener subclasses)
> * removing the XML notation from the standard JSP syntax
> thus brining it in line with the spec.
> * adding an adapter/code bridge that eats SAX parse events
> and feeds them to a JSPParseEveltListener
> * code to reset the parse mode of a translation unit into XML
> mode if it sees a properly formed jsp:root element. So a "plain"
> jsp could include a JSP in the XML syntax and vice versa, thus
> requiring that only individual translation units (usually files)
> need to be consistant as to wether or not they are XML or "plain"
> JSP.
>
> --Danno
Re: Any interest in comments on the servlet 2.2 API?
Posted by Danno Ferrin <sh...@earthlink.net>.
Actually, once I get settlened from my move I am plannig on presenting a
proposal to add full XML support to jasper. From what I have read from the
standard and what Edward(o) has said the XML version and the "normal"
version of a JSP document are paralell and not co-existing in the same
instantiation. Once I get my ducks in a row I'll start that, and that is
primarily what the second bullet represents.
Roughly what I plan on is:
* a command line tool, JSP->servlet (already in the TODO list)
and JSP<->(XML of the JSP) (uses the first command line, just
with diffrent JSPParseEventListener subclasses)
* removing the XML notation from the standard JSP syntax
thus brining it in line with the spec.
* adding an adapter/code bridge that eats SAX parse events
and feeds them to a JSPParseEveltListener
* code to reset the parse mode of a translation unit into XML
mode if it sees a properly formed jsp:root element. So a "plain"
jsp could include a JSP in the XML syntax and vice versa, thus
requiring that only individual translation units (usually files)
need to be consistant as to wether or not they are XML or "plain"
JSP.
--Danno
----- Original Message -----
From: "Assaf Arkin" <ar...@exoffice.com>
To: <to...@jakarta.apache.org>
Sent: Tuesday, January 11, 2000 12:49 PM
Subject: Re: Any interest in comments on the servlet 2.2 API?
> Was there any discussion regarding producing results through the SAX API
> instead of directly printing to the writer?
>
> arkin
>
>
> Danno Ferrin wrote:
> >
> > How about a normative addendum, released in paralell with the specs?
Three
> > issues come to mind immediatly that should be addressed there.
> >
> > * relative nested includes. Having the includes relative to the
translation
> > element that holds the <%@include %> directive seems to be a popular
choice.
> > Relative to the original translation unit seems ok by the spec too,
although
> > it is not quite as polular (but you can do some cool tricks with it).
> >
> > * XML document not being intermixed with a JSP document.
> >
> > *getProperty... remove or elabortate on the "only jsp:useBean"
parentetical
> > comment.
> >
> > --Danno
> >
> > ----- Original Message -----
> > From: "Eduardo Pelegri-Llopart" <Ed...@eng.sun.com>
> > To: <to...@jakarta.apache.org>
> > Sent: Monday, January 10, 2000 10:40 AM
> > Subject: Re: Any interest in comments on the servlet 2.2 API?
> >
> > > Could you please (re)send us those to me? Danny Coward and I are
> > > beginning to collect all of this material for the next version of the
> > > spec.
> > >
> > > Servlet 2.2 and JSP 1.1 are final and nothing more than simple obvious
> > > errors can be fixed, and that probably only in an errata (we are
looking
> > > into how to do that). Discussions of features are always useful,
> > > although eventually they should be forwarded to the expert group,
> > > otherwise it is too easy to lose track of them.
> > >
> > > Also, apologies for lack of feedback on comments, times were pretty
> > > hectic towards the end of the previous release cycle.
> > >
> > > - eduard/o
> > >
> > > Miles Sabin wrote:
> > > >
> > > > A while ago I mailed a bunch of comments on the 2.2 API to Sun
> > > > (mostly on buffering and localization). I didn't get any
> > > > feedback and none of them appear to have been taken up for the
> > > > final 2.2 spec.
> > > >
> > > > I don't know to what extent the current spec is carved in stone
> > > > now, but I still think the issues are worthy of attention.
> > > > Would it be of any interest to readers of this list? If so I'll
> > > > repost the comments here.
> > > >
> > > > Cheers,
> > > >
> > > > Miles
> > > >
> > > > --
> > > > Miles Sabin Cromwell Media
> > > > Internet Systems Architect 5/6 Glenthorne Mews
> > > > +44 (0)20 8817 4030 London, W6 0LJ, England
> > > > msabin@cromwellmedia.com http://www.cromwellmedia.com/
> > > >
> > >
> ---------------------------------------------------------------------
> > > > 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
Re: Any interest in comments on the servlet 2.2 API?
Posted by Assaf Arkin <ar...@exoffice.com>.
Was there any discussion regarding producing results through the SAX API
instead of directly printing to the writer?
arkin
Danno Ferrin wrote:
>
> How about a normative addendum, released in paralell with the specs? Three
> issues come to mind immediatly that should be addressed there.
>
> * relative nested includes. Having the includes relative to the translation
> element that holds the <%@include %> directive seems to be a popular choice.
> Relative to the original translation unit seems ok by the spec too, although
> it is not quite as polular (but you can do some cool tricks with it).
>
> * XML document not being intermixed with a JSP document.
>
> *getProperty... remove or elabortate on the "only jsp:useBean" parentetical
> comment.
>
> --Danno
>
> ----- Original Message -----
> From: "Eduardo Pelegri-Llopart" <Ed...@eng.sun.com>
> To: <to...@jakarta.apache.org>
> Sent: Monday, January 10, 2000 10:40 AM
> Subject: Re: Any interest in comments on the servlet 2.2 API?
>
> > Could you please (re)send us those to me? Danny Coward and I are
> > beginning to collect all of this material for the next version of the
> > spec.
> >
> > Servlet 2.2 and JSP 1.1 are final and nothing more than simple obvious
> > errors can be fixed, and that probably only in an errata (we are looking
> > into how to do that). Discussions of features are always useful,
> > although eventually they should be forwarded to the expert group,
> > otherwise it is too easy to lose track of them.
> >
> > Also, apologies for lack of feedback on comments, times were pretty
> > hectic towards the end of the previous release cycle.
> >
> > - eduard/o
> >
> > Miles Sabin wrote:
> > >
> > > A while ago I mailed a bunch of comments on the 2.2 API to Sun
> > > (mostly on buffering and localization). I didn't get any
> > > feedback and none of them appear to have been taken up for the
> > > final 2.2 spec.
> > >
> > > I don't know to what extent the current spec is carved in stone
> > > now, but I still think the issues are worthy of attention.
> > > Would it be of any interest to readers of this list? If so I'll
> > > repost the comments here.
> > >
> > > Cheers,
> > >
> > > Miles
> > >
> > > --
> > > Miles Sabin Cromwell Media
> > > Internet Systems Architect 5/6 Glenthorne Mews
> > > +44 (0)20 8817 4030 London, W6 0LJ, England
> > > msabin@cromwellmedia.com http://www.cromwellmedia.com/
> > >
> > > ---------------------------------------------------------------------
> > > 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: Any interest in comments on the servlet 2.2 API?
Posted by Danno Ferrin <sh...@earthlink.net>.
How about a normative addendum, released in paralell with the specs? Three
issues come to mind immediatly that should be addressed there.
* relative nested includes. Having the includes relative to the translation
element that holds the <%@include %> directive seems to be a popular choice.
Relative to the original translation unit seems ok by the spec too, although
it is not quite as polular (but you can do some cool tricks with it).
* XML document not being intermixed with a JSP document.
*getProperty... remove or elabortate on the "only jsp:useBean" parentetical
comment.
--Danno
----- Original Message -----
From: "Eduardo Pelegri-Llopart" <Ed...@eng.sun.com>
To: <to...@jakarta.apache.org>
Sent: Monday, January 10, 2000 10:40 AM
Subject: Re: Any interest in comments on the servlet 2.2 API?
> Could you please (re)send us those to me? Danny Coward and I are
> beginning to collect all of this material for the next version of the
> spec.
>
> Servlet 2.2 and JSP 1.1 are final and nothing more than simple obvious
> errors can be fixed, and that probably only in an errata (we are looking
> into how to do that). Discussions of features are always useful,
> although eventually they should be forwarded to the expert group,
> otherwise it is too easy to lose track of them.
>
> Also, apologies for lack of feedback on comments, times were pretty
> hectic towards the end of the previous release cycle.
>
> - eduard/o
>
> Miles Sabin wrote:
> >
> > A while ago I mailed a bunch of comments on the 2.2 API to Sun
> > (mostly on buffering and localization). I didn't get any
> > feedback and none of them appear to have been taken up for the
> > final 2.2 spec.
> >
> > I don't know to what extent the current spec is carved in stone
> > now, but I still think the issues are worthy of attention.
> > Would it be of any interest to readers of this list? If so I'll
> > repost the comments here.
> >
> > Cheers,
> >
> > Miles
> >
> > --
> > Miles Sabin Cromwell Media
> > Internet Systems Architect 5/6 Glenthorne Mews
> > +44 (0)20 8817 4030 London, W6 0LJ, England
> > msabin@cromwellmedia.com http://www.cromwellmedia.com/
> >
> > ---------------------------------------------------------------------
> > 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: Any interest in comments on the servlet 2.2 API?
Posted by Eduardo Pelegri-Llopart <Ed...@eng.sun.com>.
Could you please (re)send us those to me? Danny Coward and I are
beginning to collect all of this material for the next version of the
spec.
Servlet 2.2 and JSP 1.1 are final and nothing more than simple obvious
errors can be fixed, and that probably only in an errata (we are looking
into how to do that). Discussions of features are always useful,
although eventually they should be forwarded to the expert group,
otherwise it is too easy to lose track of them.
Also, apologies for lack of feedback on comments, times were pretty
hectic towards the end of the previous release cycle.
- eduard/o
Miles Sabin wrote:
>
> A while ago I mailed a bunch of comments on the 2.2 API to Sun
> (mostly on buffering and localization). I didn't get any
> feedback and none of them appear to have been taken up for the
> final 2.2 spec.
>
> I don't know to what extent the current spec is carved in stone
> now, but I still think the issues are worthy of attention.
> Would it be of any interest to readers of this list? If so I'll
> repost the comments here.
>
> Cheers,
>
> Miles
>
> --
> Miles Sabin Cromwell Media
> Internet Systems Architect 5/6 Glenthorne Mews
> +44 (0)20 8817 4030 London, W6 0LJ, England
> msabin@cromwellmedia.com http://www.cromwellmedia.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org