2 Replies Latest reply on Sep 17, 2001 2:18 PM by Joel Shellman

    Private JNDI per application

    Joel Shellman Newbie

      We are working on offering shared jetty/jboss hosting services and so obviously security is critical.

      The big challenge is that many application servers seem to be written to the one JVM one app mentality with much of the services being set up globally for the whole app server as opposed to just specific to an application.

      This especially goes for DataSources--and I've been trying to figure out how to get around that. But I realized it also goes for JNDI itself. A user doesn't want to be able to see or especially not be able to overwrite another user's JNDI values.

      Is there a way to set up so that the JNDI registry an application sees is it's own and no other application would have access to it?

      Thanks!

        • 1. Re: Private JNDI per application
          Scott Stark Master

          Any ear receives a private java:comp JNDI context that is only accessible by its components.

          Your basically asking for a heirarchical configuration capability with shared global services along with application specific services. JBoss does not have support for this type of configuration in 2.4.x

          Look at the 3.0 stuff and get involved with making this a reality in that release as the configuration is being completely redone.

          • 2. Re: Private JNDI per application
            Joel Shellman Newbie

            > Any ear receives a private java:comp JNDI context that is only acceAny ear receives a private java:comp JNDI context that is only accessible by its components.ssible by its components.

            But I think that's all we need.

            Now, is there a way, then to create a datasource that is only accessible under that JNDI context so each ear can have it's own private datasource(s)?