1 Reply Latest reply on Oct 9, 2002 8:26 PM by David Jencks

    MIgration form 2.x to 3.x

    Rob Newbie

      I am migrating from JBoss 2.4.6 to JBoss 3.03, and have a couple of questions.

      1) where do you set them up ? (is it the deploy directory)

      2) can you have multiple datasource references in one "blah-service.xml" file? In 2.X I had multiple org.jboss.jdbc.JDBCDataSourceLoader's within the JCML, Some deployments numerous of the same type of connections (ie 3 SQLServer pools),

      3) can you mix and match your datasource references. For example a deployment may have numerous, but different datasource types (ie 1 oracle, and 2 hypersonic pools), I could do that in the old JCML.. is this still possible? Or do I create a "blah-service.xml" per datasource type.

      4) What dependencies if any do I have to declare in my MBeans that might be using the datasources I create ?

      5) What is the intital context look up String for the DefaultDS.. everythig I try seems to die... I get NameNotFound

        • 1. Re: MIgration form 2.x to 3.x
          David Jencks Master

          > I am migrating from JBoss 2.4.6 to JBoss 3.03, and
          > have a couple of questions.
          >
          > 1) where do you set them up ? (is it the deploy
          > directory)
          >
          yes
          > 2) can you have multiple datasource references in one
          > "blah-service.xml" file? In 2.X I had multiple
          > org.jboss.jdbc.JDBCDataSourceLoader's within the
          > JCML, Some deployments numerous of the same type of
          > connections (ie 3 SQLServer pools),
          yes
          >
          > 3) can you mix and match your datasource references.
          > For example a deployment may have numerous, but
          > different datasource types (ie 1 oracle, and 2
          > hypersonic pools), I could do that in the old JCML..
          > is this still possible? Or do I create a
          > "blah-service.xml" per datasource type.

          You can put them all in one *-service.xml file with any other mbeans you may need. It's the same format as jboss.jcml was (with some extensions), just now you can have as many of them as you want.
          >
          > 4) What dependencies if any do I have to declare in
          > my MBeans that might be using the datasources I
          > create ?

          You can depend on the connection manager mbean:


          jboss.jca:service=LocalTxCM,name=MyDS


          If your mbean has lifecycle methods, this will make them wait until the cm is created and started.
          >
          > 5) What is the intital context look up String for the
          > DefaultDS.. everythig I try seems to die... I get
          > NameNotFound

          only from jboss vm... lookup("java:/DefaultDS")