Re: Hypothetical
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 the kind of gotcha I was hoping someone would point out. Much appreciated. Rick - Servlet v2.4 container in a single 140KB jar file ? Try Winstone (http://winstone.sf.net/) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Hypothetical
Tomcat dev types, This is not a request for enhancement or change in any way, just seeking an opinion on an idea. Has BCEL ever been considered for use with in a JSP compiler like Jasper ? I'm currently toying with trying to start a new JSP compiler project to go with Winstone (servlet engine), and so started looking at things like XSLTC for ideas. I noticed it was using BCEL, and in doing so avoided the need for more than a JRE. Do any of you know of a JSP compiler already existing that uses this approach ? More importantly do any of you know of a reason why this would be a bad idea ? Any comments would be appreciated. Thanks in advance, Rick Knowles - Servlet v2.4 container in a single 140KB jar file ? Try Winstone (http://winstone.sf.net/) http://winstone.sourceforge.net/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Hypothetical
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 Informatics -Original Message- From: Rick Knowles [mailto:[EMAIL PROTECTED] Sent: Thursday, June 03, 2004 8:59 AM To: Tomcat Developers List Subject: Hypothetical Tomcat dev types, This is not a request for enhancement or change in any way, just seeking an opinion on an idea. Has BCEL ever been considered for use with in a JSP compiler like Jasper ? I'm currently toying with trying to start a new JSP compiler project to go with Winstone (servlet engine), and so started looking at things like XSLTC for ideas. I noticed it was using BCEL, and in doing so avoided the need for more than a JRE. Do any of you know of a JSP compiler already existing that uses this approach ? More importantly do any of you know of a reason why this would be a bad idea ? Any comments would be appreciated. Thanks in advance, Rick Knowles - Servlet v2.4 container in a single 140KB jar file ? Try Winstone (http://winstone.sf.net/) http://winstone.sourceforge.net/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Hypothetical
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, 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 Informatics -Original Message- From: Rick Knowles [mailto:[EMAIL PROTECTED] Sent: Thursday, June 03, 2004 8:59 AM To: Tomcat Developers List Subject: Hypothetical Tomcat dev types, This is not a request for enhancement or change in any way, just seeking an opinion on an idea. Has BCEL ever been considered for use with in a JSP compiler like Jasper ? I'm currently toying with trying to start a new JSP compiler project to go with Winstone (servlet engine), and so started looking at things like XSLTC for ideas. I noticed it was using BCEL, and in doing so avoided the need for more than a JRE. Do any of you know of a JSP compiler already existing that uses this approach ? More importantly do any of you know of a reason why this would be a bad idea ? Any comments would be appreciated. Thanks in advance, Rick Knowles - Servlet v2.4 container in a single 140KB jar file ? Try Winstone (http://winstone.sf.net/) http://winstone.sourceforge.net/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Hypothetical
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 a TCK soon. Until then, I figure it's ok to say it's spec compliant as long as it works with all the apps I've tested, and I tell everyone I haven't run the TCK tests yet. Maybe in another month the JCP people will send me the TCK ... until then though, not much I can do. Interesting though - the spec says: quote from p104 section 13.1 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 specification: jsp-config Syntax for looking up JNDI objects (env-entry, ejb-ref, ejb-local-ref, resource-ref, resource-env-ref) Syntax for specifying the message destination (message-destination, message-destination-ref) Reference to a Web service (service-ref) /quote from p104 section 13.1 I wasn't planning for Winstone to be a full J2EE compliant container, so I took this to mean resource-ref, et al were optional. Did I read it wrong ? Rick Knowles - Servlet v2.4 container in a single 140KB jar file ? Try Winstone (http://winstone.sf.net/) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Hypothetical
Hi, quote from p104 section 13.1 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 specification: * jsp-config * Syntax for looking up JNDI objects (env-entry, ejb-ref, ejb-local-ref, resource-ref, resource-env-ref) * Syntax for specifying the message destination (message-destination, message-destination-ref) * Reference to a Web service (service-ref) /quote from p104 section 13.1 I wasn't planning for Winstone to be a full J2EE compliant container, so I took this to mean resource-ref, et al were optional. Did I read it wrong ? 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 containers I know of do support these features, and very few people know the spec by heart). Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Hypothetical
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 containers I know of do support these features, and very few people know the spec by heart). This is a fair point. I'll change the doc to something a little clearer. Or maybe I'll just implement the remaining pieces as components for the full jar set only (ie the non-lite version). Thanks again, Rick - Servlet v2.4 container in a single 140KB jar file ? Try Winstone (http://winstone.sf.net/) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Hypothetical
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 (because all other servlet containers I know of do support these features, and very few people know the spec by heart). This is a fair point. I'll change the doc to something a little clearer. Or maybe I'll just implement the remaining pieces as components for the full jar set only (ie the non-lite version). Even if it's not required in the spec, many webapps will use JNDI. 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
