1 Reply Latest reply on Jul 7, 2003 9:22 AM by adrian.brock

    eXcelon XIS on jboss 3.2.1

    pvamstel

      Hi all,

      It has been a long time, but i have a problem regarding the connector from eXcelon with jboss 3.2.1.

      The connector worked on the jboss 3.0.x but now does bot work on the new jboss. Here is the old service file.

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


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

      <!--more hack-->
      <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=Excelon DXE Remote Connector


      <config-property name="ServerName" type="java.lang.String">xxxx.anachron.nl</config-property>
      <config-property name="PortNumber" type="java.lang.Integer">1050</config-property>


      eis/DXERemoteConnector


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

      0
      50
      5000
      15
      ByContainer


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



      Here is the ra.xml supplied by eXcelon.

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

      <!DOCTYPE connector PUBLIC '-//Sun Microsystems, Inc.//DTD Connector 1.0//EN' 'http://java.sun.com/dtd/connector_1_0.dtd'>


      <display-name>Excelon DXE Remote Connector</display-name>
      <vendor-name>Excelon Corporation</vendor-name>
      <spec-version>1.0</spec-version>
      <eis-type></eis-type>
      1.0

      <managedconnectionfactory-class>com.exln.dxe.jca.RemoteManagedConnectionFactory</managedconnectionfactory-class>
      <connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface>
      <connectionfactory-impl-class>com.exln.dxe.jca.RemoteConnectionFactory</connectionfactory-impl-class>
      <connection-interface>javax.resource.cci.Connection</connection-interface>
      <connection-impl-class>com.exln.dxe.jca.ConnectionImpl</connection-impl-class>
      <transaction-support>NoTransaction</transaction-support>
      <config-property>
      DXE admin server name
      <config-property-name>ServerName</config-property-name>
      <config-property-type>java.lang.String</config-property-type>
      <config-property-value>sydney.anachron.nl</config-property-value>
      </config-property>
      <config-property>
      DXE admin host port
      <config-property-name>PortNumber</config-property-name>
      <config-property-type>java.lang.Integer</config-property-type>
      <config-property-value>1050</config-property-value>
      </config-property>
      <authentication-mechanism>
      Authentication mechanism
      <authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
      <credential-interface>javax.resource.security.PasswordCredential</credential-interface>
      </authentication-mechanism>
      <reauthentication-support>false</reauthentication-support>



      I've been decompiling changing and reconfiguring the code. I'm stuck. I think it has something to do with CORBA. The eXeclon application uses it's own implementation of that.

      Is it true that jboss now has it's own CORBA thing?
      What is changed between the 3.0.x and the 3.2.x
      distribution. All help is welcome.

      grt Patrick

        • 1. Re: eXcelon XIS on jboss 3.2.1

          The managed connection factory name is now a property
          on the pool. Just move the block.
          You might want to investigate the -ds.xml format
          that will help you avoid changes to the underlying
          implementation.

          Regards,
          Adrian