1 Reply Latest reply on Jul 26, 2002 12:33 PM by David Jencks

    MSAccess DS - problem with -service.xml - FIX

    Feroz Newbie

      Hi All,

      I thought it'd be a good idea to share this with all of you. I was trying to configure an MS Access DS using JBoss 3.0 (Jdk 1.4.0, NT) and downloaded the msaccess-service.xml file from the CVS. Then I struggled for 2-3 days to get it working. Everytime I try to access the DS, I'd get a NameNotFoundException. The DS was not registering in the JNDI tree. After a lot of juggling, finally got it working. Here's the file that's working :

      <?xml version="1.0" encoding="UTF-8"?>

      <depends optional-attribute-name="ManagedConnectionFactoryName">


      <config-property name="ConnectionURL" type="java.lang.String">jdbc:odbc:MSAccessDSN</config-property>
      <config-property name="DriverClass" type="java.lang.String">sun.jdbc.odbc.JdbcOdbcDriver</config-property>

      <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper

      <depends optional-attribute-name="ManagedConnectionPool">


      <depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager
      <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:name=JaasSecurityManager


      The problem I think was with the JaasSecurityManagerService config. It said jboss:security:service. But I got it working by modifying to jboss:security:name. Being a newbie, I'm not sure what this means but it sure works :). Also the JNDI name should appear under RARDeployment MBean which was outside in the original file. Someone please update the CVS tree so that others don't struggle the way I had to.


        • 1. Re: MSAccess DS - problem with -service.xml - FIX
          David Jencks Master

          You need to check the cvs tags on the different versions to see what goes with your jboss version. Unfortunately I can't put a tag for a released version of jboss on a file that was not present for that release, so there is no way of including this update in cvs in a way consistent with the other tags. I believe the cvs versions of this file work with the cvs versions of jboss, and that the Branch_3_0 version works with 3.0.1