Howdy, >When you say a JNDI server accessible "from outside clients", what do you >mean exactly?
I mean you can't have another JVM or another process use tomcat's JNDI services. >Are you saying with a JNDI server(properly configured), you can >access a DataSource or any files within the container? Because based on >Servlet specification, no resource within the WEB-INF directory can be >served directly >to a client. Are you talking about files outside of WEB-INF directory but >with the web-app? Yes, and no, respectively ;) I'm familiar with the servlet specification and its restrictions on resources within WEB-INF, but that's not relevant. The resources defined and accessed via JNDI services rarely reside as static content within the WEB-INF directory: they're usually remote beans, databases, or things like mail and JMS sessions, queues, topics. With a JNDI server that supports external connections, other processes including remote ones can connect to the server and access whatever JNDI services are defined, e.g. the database or JMS queue above. This provides an abstraction layer in that the remote app doesn't have to know the database URL or connection information, just the JNDI's server's location and the JNDI name for the resource. This is pretty basic JNDI stuff. There are ample resources on the web to help with JNDI. Yoav Shapira 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]
