DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33753>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33753 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2005-03-02 12:00 ------- Please allow me to clarify with references to the Servlet 2.4 specification. Page 104. SRV.13.1.2: --- CUT HERE --- 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) The syntax for these elements is now held in the JavaServer Pages specification version 2.0, and the J2EE specification version 1.4. ---CUT HERE--- The key phrase is "JSP pages enabled or part of a J2EE application server." Tomcat does support JSPs. Tomcat 5.5 does claim to support JSP 2.0. Therefore, according to the spec it should support the <service-ref/> tag. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
