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]
