As for the orininal question: you cannot support scriplets without
compiling. I know Kin-Man has entertained the idea of using straight
code generation for tags-only pages, but assuming the
super-duper-compiler from the JCP shows up, the incentive isn't very big.
Rémy
Thanks - this is exactly
Rick Knowles wrote:
Yoav,
I think you read it correctly, and interpreted it correctly. It's a
distinction between the Servlet and JSP specifications. You just have
to be careful to mention those sort of things up front, as people might
expect those features from a "Servlet v2.4 container" (becaus
Yoav,
I think you read it correctly, and interpreted it correctly. It's a
distinction between the Servlet and JSP specifications. You just have
to be careful to mention those sort of things up front, as people might
expect those features from a "Servlet v2.4 container" (because all other
servlet
Hi,
>
>The following additional elements exist in the Web application
deployment
>descriptor to meet the requirements of Web containers that are JSP
pages
>enabled or part of a J2EE application server. They are not required to
be
>supported by containers wishing to support only the servlet
specif
Yoav,
You know Servlet Spec compatibility requires env-entry/resource-ref
support and therefore at least a slim JNDI implementation...
Yoav Shapira
Millennium Research Informatics
Thanks for the reply.
I've only just (as in this morning) received a reply from the JCP people saying I'd be sent
Hi,
Never mind, I see the note about JNDI support now... ;)
Yoav Shapira
Millennium Research Informatics
>-Original Message-
>From: Shapira, Yoav
>Sent: Thursday, June 03, 2004 9:03 AM
>To: 'Tomcat Developers List'
>Subject: RE: Hypothetical
>
>Hi,
&g
Hi,
I personally am not aware of JSP compilers that use BCEL or another
bytecode modification library to generate their class files.
You know Servlet Spec compatibility requires env-entry/resource-ref
support and therefore at least a slim JNDI implementation...
Yoav Shapira
Millennium Research I
