6 Replies Latest reply on Feb 28, 2002 12:08 PM by davidjencks

    Location of DB Drivers in JBoss 3 Beta

    greathavoc

      Hi,

      It seems that the location for the DB drivers have changed since the Alpha. In the alpha one would put them in the JBoss/lib/ext directory. Now it seems that JBoss looks in JBoss/deploy instead. Anyone know whether this is intentional and whether this can be changed?

      Thanks,

      Jim

        • 1. Re: Location of DB Drivers in JBoss 3 Beta
          zeroman

          You can use XML tag in your file





          It works fine.

          • 2. Re: Location of DB Drivers in JBoss 3 Beta
            davidjencks

            What problem do you have putting driver jars in lib/ext? You should not need the classpath tag with jboss 3 beta or cvs.

            • 3. Re: Location of DB Drivers in JBoss 3 Beta
              chriss

              I've actually got the very same problem that Jim describes. The alpha version didn't have any problem with my jdbc jar in lib/ext/. However with beta this is not the case anymore (see exception).
              Putting the jar in the deploy directory 'solves' the problem. I seem to remember some discussion about external classes etc. that don't work anymore in lib/ext due to a bug introduced into the deployer.

              15:59:33,963 INFO [MainDeployer] Deploying: file:/usr/java/jboss-3.0.0beta/deploy/postgres-service.xml
              15:59:33,994 ERROR [SARDeployer] operation failed
              org.jboss.deployment.DeploymentException: url file:/usr/java/jboss-3.0.0beta/deploy/jdbc7.1-1.2.jar could not be opened, does it exist?
              at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:148)
              at org.jboss.deployment.SARDeployer.parseXMLClasspath(SARDeployer.java:475)
              at org.jboss.deployment.SARDeployer.init(SARDeployer.java:174)
              at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:449)
              at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:413)
              at org.jboss.deployment.MainDeployer.scan(MainDeployer.java:272)
              at org.jboss.deployment.MainDeployer.startService(MainDeployer.java:218)
              at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:160)
              at java.lang.reflect.Method.invoke(Native Method)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              at org.jboss.system.Server.(Server.java:157)
              at org.jboss.Main.boot(Main.java:263)
              at org.jboss.Main.run(Main.java:48)
              at java.lang.Thread.run(Thread.java:484)

              • 4. Re: Location of DB Drivers in JBoss 3 Beta
                greathavoc

                Hi,

                Zeroman is correct, just use the "basedir" attribute and it works. By the way, in Beta2 the external library directory is by default "JBoss\lib". It's no longer Jboss\lib\ext nor Jboss\deploy.

                Jim

                • 5. Re: Location of DB Drivers in JBoss 3 Beta
                  greathavoc

                  Sorry I mean codebase attribute not basedir attribute.

                  • 6. Re: Location of DB Drivers in JBoss 3 Beta
                    davidjencks

                    Ok, now I see what you are doing and why there is a problem. Put the driver in lib AND COMPLETELY REMOVE the codebase tag, it is no longer necessary.