4 Replies Latest reply on Jul 27, 2011 12:15 PM by Bryan Shepherd

    problems deploying web application (** NOT FOUND Depends on .....

    Bryan Shepherd Newbie

      I am trying to deploy a web application to jboss as6.   I have added all the resource-env-ref references to the jboss-web.xml (this was done based on another error/solution, that had me add the references to the jboss-web.xml file ), now I see the following:

       

      "  Deployment "com.vocollecthealthcare.yosemite.device.OperatorDatastore" is in error due to the following reason(s): ** NOT FOUND Depends on 'com.vocollecthealthcare.yosemite.device.OperatorDatastore' ** "

       

      for what looks like all the references I just added.   The classes are in the classes directory of my war file so I am not sure why this is occurring.  Actually that's not totally true, I think it is a class loading issue but I don't know for sure.

       

      example of resource-env-ref for this particular class.

       

      <resource-env-ref>

      <resource-env-ref-name>operatorDatastore</resource-env-ref-name>

      <jndi-name>com.vocollecthealthcare.yosemite.device.OperatorDatastore</jndi-name>

       

      </resource-env-ref>

       

      There are no other errors or issues in the log just these entries.....

       

      Any insight or help would be greatly appreciated.

        • 1. Re: problems deploying web application (** NOT FOUND Depends on .....
          Wolfgang Knauf Master

          Hi Brian,

           

          what kind of object is "com.vocollecthealthcare.yosemite.device.OperatorDatastore"? Is it an EJB?

           

          Did you bound it to a JNDI name which is identical to the class name? Check the JNDIView in JMXConsole: http://geekzguru.wordpress.com/2008/01/22/howto-view-the-jndi-tree-in-jboss/

           

          Best regards

           

          Wolfgang

          • 2. Re: problems deploying web application (** NOT FOUND Depends on .....
            Bryan Shepherd Newbie

            No ejbs...  That is an interface with bean mappings in a spring context file as are all the problems I am seeing. 

             

            <resource-env-ref>

            <resource-env-ref-name>operatorDatastore</resource-env-ref-name>

            <jndi-name>com.vocollecthealthcare.yosemite.device.OperatorDatastore</jndi-name>

            </resource-env-ref>

             

            These resource references are the only configurations I have done.  The jndi above is the exact interface and package of the resource ref.  Is this not correct?  Should my jndi-name above just be the interface without the package?

             

            One other thing,  I have multiple references to this resource from different classes so here are the additional references

             

            <resource-env-ref>

            <resource-env-ref-name>com.vocollecthealthcare.wc.terminal.HandlerBase/operatorDatastore</resource-env-ref-name>

            <jndi-name>com.vocollecthealthcare.yosemite.device.OperatorDatastore</jndi-name>

            </resource-env-ref>

             

            <resource-env-ref>

            <resource-env-ref-name>com.vocollecthealthcare.yosemite.schedule.PublishTaskStatsAfterShiftJob/operatorDatastore</resource-env-ref-name>

            <jndi-name>com.vocollecthealthcare.yosemite.device.OperatorDatastore</jndi-name>

            </resource-env-ref>

             

            <resource-env-ref>

            <resource-env-ref-name>com.vocollecthealthcare.wc.task.TaskStatsMessageSerializer/operatorDatastore</resource-env-ref-name>

            <jndi-name>com.vocollecthealthcare.yosemite.device.OperatorDatastore</jndi-name>

            </resource-env-ref>

             

            <resource-env-ref>

            <resource-env-ref-name>com.vocollecthealthcare.wc.rest.OperatorResource/operatorDatastore</resource-env-ref-name>

            <jndi-name>com.vocollecthealthcare.yosemite.device.OperatorDatastore</jndi-name>

            </resource-env-ref>

             

            some history:

            We use the @Resourse annotation in some of our classes to point at the interfaces that are mapped in spring.   I was originally seeing the "Neither any mapped-name/lookup/jndi-name specified nor any ResourceProvider could process resource-env-ref"  message when I tried to deploy.  After doing some digging I found something that said I needed to add the references as I noted before, so I did.  Now I have hit this issue.

             

            • 3. Re: problems deploying web application (** NOT FOUND Depends on .....
              Wolfgang Knauf Master

              Hi,

               

              sorry, I don't know Spring, so I cannot help you further. Hopefully, someone else can provide more information, based on the details of your last post.

               

              Best regards

               

              Wolfgang