3 Replies Latest reply on Mar 19, 2008 11:53 AM by Pete Muir

    Not found: jndi.properties?

    jeff liu Newbie

      Hey Everyone


      When I start the seam app with debug log, the following message pops up



      16:31:15,656 DEBUG Initialization not found: 
      /jndi.properties



      And


      16:31:15,656 DEBUG Initialization not found:/seam-jndi.properties



      Later on, when I access the stateful session bean, following exception is throw


      Caused by: javax.naming.NameNotFoundException: Name ManagerAction is not bound in this Context



      But, after I move the project back to seam 1.2.1.GA, it works fine without exception.


      Do I need to add jndi.properties into my project???


      Thank you very much





        • 1. Re: Not found: jndi.properties?
          Norman Richards Expert

          Are you running on JBoss?  On JBoss, Seam should be finding the server-widejndi.properties in server/default/conf.  

          • 2. Re: Not found: jndi.properties?
            jeff liu Newbie

            Hey Thank you much for your reply


            It helps. I found out that there is jndi.properties under server/default/conf.


            I found out that the difference in jndi.properties files is following:
            My Seam 1.2 Config


            java.naming.factory.initial=org.jnp.interfaces.LocalOnlyContextFactory
            java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces




            My Seam 2.0 Config


            java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
            java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces



            When jndi sitting is
            org.jnp.interfaces.NamingContextFactory




            It results following:


            Caused by: javax.naming.NameNotFoundException: MyStatefulBean not bound




            Do you have any idea why?

            • 3. Re: Not found: jndi.properties?
              Pete Muir Master

              You shouldn't need any jndi.properties deployed with your project. Are you deploying to a clean install of JBoss 4.2?