its in the distribution.
jboss/docs/examples/jca
I've used it for Oracle and it works. See attached.
Bill
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Eric Kaplan
> Sent: Tuesday, June 18, 2002 4:23 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] 3.0 a moving target?
>
>
> David
>
> As you had originally suggested, I got the jboss-all nightly snapshot from
> the jboss "Source Code and CVS" page. The oracle-service.xml I
> got was from
> jboss-all/connector/src/etc/example-config, though below you suggest a
> slightly different directory. The problem I'm having here is I
> can't figure
> out the right download. Where would docs/examples/jca be, I feel
> like I've
> searched everywhere.
>
> Sorry about this.
>
> Regards
>
> Eric
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of David Jencks
> Sent: Tuesday, June 18, 2002 3:49 PM
> To: Eric Kaplan
> Cc: Jboss-User
> Subject: Re: [JBoss-user] 3.0 a moving target?
>
>
> I don't think you started with the oracle-service.xml from
> docs/examples/jca, since yours references the minerva jdbc
> wrapper which is
> no longer present.
>
>
> optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDe
> ployment,n
> > ame=Minerva JDBC LocalTransaction ResourceAdapter</depends>
>
> is wrong. There are other changes as well, please get an updated starting
> point.
>
> david jencks
>
> On 2002.06.18 13:39:20 -0400 Eric Kaplan wrote:
> > David
> >
> > I see what you mean, and I took the example and modified it by changing
> > the
> > jndi name,
> > putting in my user id and password and db url. I get ABPDevPool not
> > bound,
> > which is
> > the jndi name I'm using. I really would like to upgrade from 3.0.0RC to
> > 3.0.0, any
> > light you could shed would be key.
> >
> > Thanks
> >
> > My jboss.xml says:
> >
> > <resource-managers>
> > <resource-manager res-class="org.jboss.ejb.deployment.JDBCResource">
> > <res-name>jdbc/dmfiDB</res-name>
> > <res-jndi-name>java:/ABPDevPool</res-jndi-name>
> > </resource-manager>
> > </resource-managers>
> >
> > My oracle-service.xml says:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> >
> > <!--
> >
> ===================================================================== -->
> > <!--
> > -
> > ->
> > <!-- JBoss Server
> > -->
> > <!--
> > -
> > ->
> > <!--
> >
> ===================================================================== -->
> >
> > <server>
> >
> > <!--
> > ==================================================================== -->
> > <!-- ConnectionManager setup for Oracle
> > -->
> > <!-- Build jmx-api (build/build.sh all) and view for config
> > documentation -->
> > <!-- Thanks to Steven
> > -->
> > <!--
> > ==================================================================== -->
> >
> > <mbean
> > code="org.jboss.resource.connectionmanager.LocalTxConnectionManager"
> > name="jboss.jca:service=LocalTxCM,name=OracleDS">
> > <!--make the rar deploy! hack till better deployment-->
> > <depends>jboss.jca:service=RARDeployer</depends>
> >
> >
> > <depends optional-attribute-name="ManagedConnectionFactoryName">
> > <!--embedded mbean-->
> > <mbean code="org.jboss.resource.connectionmanager.RARDeployment"
> > name="jboss.jca:service=LocalTxDS,name=OracleDS">
> > <!--hack-->
> > <depends
> >
> optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDe
> ployment,n
> > ame=Minerva JDBC LocalTransaction ResourceAdapter</depends>
> >
> > <!--real attributes-->
> > <attribute name="ManagedConnectionFactoryProperties">
> > <properties>
> > <config-property>
> > <config-property-name>ConnectionURL</config-property-name>
> >
> <config-property-type>java.lang.String</config-property-type>
> >
> >
> <config-property-value>jdbc:oracle:thin:@localhost:1521:dev</confi
> g-property
> > -value>
> > </config-property>
> > <config-property>
> > <config-property-name>DriverClass</config-property-name>
> >
> <config-property-type>java.lang.String</config-property-type>
> >
> >
> <config-property-value>oracle.jdbc.driver.OracleDriver</config-pro
> perty-valu
> > e>
> > </config-property>
> > <!--It is recommended that you use the JAAS security
> > facilities
> > instead of exposing your security info here-->
> > <config-property>
> > <config-property-name>UserName</config-property-name>
> >
> <config-property-type>java.lang.String</config-property-type>
> > <config-property-value>abpdev</config-property-value>
> > </config-property>
> > <config-property>
> > <config-property-name>Password</config-property-name>
> >
> <config-property-type>java.lang.String</config-property-type>
> > <config-property-value>abpdev</config-property-value>
> > </config-property>
> > </properties>
> >
> > </attribute>
> > <attribute name="JndiName">ABPDevPool</attribute>
> > </mbean>
> > </depends>
> >
> > <depends optional-attribute-name="ManagedConnectionPool">
> > <!--embedded mbean-->
> > <mbean
> > code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool"
> > name="jboss.jca:service=LocalTxPool,name=OracleDS">
> >
> > <attribute name="MinSize">0</attribute>
> > <attribute name="MaxSize">50</attribute>
> > <attribute name="BlockingTimeoutMillis">5000</attribute>
> > <attribute name="IdleTimeoutMinutes">15</attribute>
> > <!--criteria indicates if Subject (from security domain) or app
> > supplied
> > parameters (such as from getConnection(user, pw))
> are used to
> > distinguish
> > connections in the pool. Choices are
> > ByContainerAndApplication (use both),
> > ByContainer (use Subject),
> > ByApplication (use app supplied params only),
> > ByNothing (all connections are equivalent, usually
> if adapter
> > supports
> > reauthentication)-->
> > <attribute name="Criteria">ByContainer</attribute>
> > </mbean>
> >
> > </depends>
> > <depends
> >
> optional-attribute-name="CachedConnectionManager">jboss.jca:servic
> e=CachedCo
> > nnectionManager</depends>
> >
> >
> > <!-- Include a login module configuration named OracleDbRealm.
> > Update your login-conf.xml, here is an example for a
> > ConfiguredIdentityLoginModule:
> >
> > <application-policy name = "OracleDbRealm">
> > <authentication>
> > <login-module code =
> > "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag =
> > "required">
> > <module-option name =
> "principal">yourprincipal</module-option>
> > <module-option name =
> "userName">yourusername</module-option>
> > <module-option name =
> "password">yourpassword</module-option>
> > <module-option name =
> >
> "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=Or
> acleDS</mo
> > dule-option>
> > </login-module>
> > </authentication>
> > </application-policy>
> >
> > NOTE: the application-policy name attribute must match the part of
> > SecurityDomainJndiName after java:/jaas/, and the
> > module-option name = "managedConnectionFactoryName"
> > must match the object name of the ConnectionManager you are
> > configuring
> > here.
> > -->
> > <!--comment out this line if you want component managed security or
> > want
> > to use the default values in the
> > ManagedConnectionFactoryProperties -->
> > <attribute
> > name="SecurityDomainJndiName">java:/jaas/OracleDbRealm</attribute>
> >
> > <attribute
> > name="TransactionManager">java:/TransactionManager</attribute>
> >
> > </mbean>
> >
> >
> > </server>
> >
> > -----Original Message-----
> > From: David Jencks [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, June 14, 2002 1:53 PM
> > To: Eric Kaplan
> > Subject: Re: [JBoss-user] 3.0 a moving target?
> >
> >
> > Neither the examples in the location mentioned nor the quickstart guide
> > existed when jboss 3 RC1 was released. I'm a little unsure of the
> > chronology but I think I replaced the jca implementation after RC1.
> >
> > david jencks
> >
> > On 2002.06.14 13:08:23 -0400 Eric Kaplan wrote:
> > > David
> > >
> > > I think that's where I originally looked when I ported to 3.0RC. My
> > real
> > > question is, if i had it working under 3.0RC, did it change going to
> > 3.0?
> > >
> > > Regards
> > >
> > > Eric
> > >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]]On Behalf Of David
> > Jencks
> > > Sent: Friday, June 14, 2002 12:58 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: [JBoss-user] 3.0 a moving target?
> > >
> > >
> > > docs/examples/jca or in cvs at connector/etc/example-config
> > >
> > > Also read the quickstart guide from sourceforge download page.
> > >
> > > david jencks
> > >
> > > On 2002.06.14 12:26:39 -0400 Eric Kaplan wrote:
> > > > jdbc access has changed from 3.0RC to 3.0? if so, where are the NEW
> > > > examples?
> > > >
> > > > and yes, i am on jdk1.4. any news about this bug getting fixed?
> > > >
> > > > regards
> > > >
> > > > eric
> > > >
> > > > -----Original Message-----
> > > > From: [EMAIL PROTECTED]
> > > > [mailto:[EMAIL PROTECTED]]On Behalf Of Burkhard
> > > > Vogel
> > > > Sent: Friday, June 14, 2002 12:08 PM
> > > > To: [EMAIL PROTECTED]
> > > > Subject: Re: [JBoss-user] 3.0 a moving target?
> > > >
> > > >
> > > > Hi,
> > > > JDBC-access has changed, see the provided examples. As for
> > > > "portableremoteobject.narrow": if you are on JDK 1.4, this
> is a known
> > > sun
> > > > bug.
> > > > Regards,
> > > > Burkhard
> > > > ----- Original Message -----
> > > > From: "Eric Kaplan" <[EMAIL PROTECTED]>
> > > > To: "Jboss-User" <[EMAIL PROTECTED]>
> > > > Sent: Friday, June 14, 2002 10:22 AM
> > > > Subject: [JBoss-user] 3.0 a moving target?
> > > >
> > > >
> > > > > I was happily using jboss3.0.0RC1_tomcat-4.0.3. However, I
> > stumbled
> > > > across
> > > > > a problem with hot re-deploy in which it seemed that after i hot
> > > > re-deployed
> > > > > by .ear i got a classcastexception on the server when trying to
> > > lookup
> > > > a
> > > > > bean that had worked before. It was almost as if the jndi mapping
> > > for
> > > > one
> > > > > bean somehow got configured with another and when I cast the
> > > > > portableremoteobject.narrow the exception occured.
> > > > >
> > > > > I thought maybe this might have been addressed with the latest
> > > version
> > > > of
> > > > > jboss, so i downloaded jboss3.0.0_tomcat-4.0.3. Now my problem is
> > > > worse.
> > > > I
> > > > > put my changed oracle-service.xml in server/default/conf (as i had
> > > done
> > > > > before), but now i get that my jdbc resource is not bound (even
> > > though
> > > > this
> > > > > worked before!). what has changed from rc1 that would cause this?
> > > > >
> > > > > Eric Kaplan
> > > > > Armanta, Inc.
> > > > > 55 Madison Ave.
> > > > > Morristown, NJ 07960
> > > > > Phone: (973) 326-9600
> > > > >
> > > > >
> > > >
> > > >
> > > > _______________________________________________________________
> > > >
> > > > Don't miss the 2002 Sprint PCS Application Developer's Conference
> > > > August 25-28 in Las Vegas -
> > > > http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
> > > >
> > > > _______________________________________________
> > > > JBoss-user mailing list
> > > > [EMAIL PROTECTED]
> > > > https://lists.sourceforge.net/lists/listinfo/jboss-user
> > > >
> > > >
> > > > _______________________________________________________________
> > > >
> > > > Don't miss the 2002 Sprint PCS Application Developer's Conference
> > > > August 25-28 in Las Vegas -
> > > http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
> > > >
> > > > _______________________________________________
> > > > JBoss-user mailing list
> > > > [EMAIL PROTECTED]
> > > > https://lists.sourceforge.net/lists/listinfo/jboss-user
> > > >
> > > >
> > >
> > > _______________________________________________________________
> > >
> > > Don't miss the 2002 Sprint PCS Application Developer's Conference
> > > August 25-28 in Las Vegas -
> > > http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
> > >
> > > _______________________________________________
> > > JBoss-user mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/jboss-user
> > >
> > >
> > >
> >
> >
> >
>
> ------------------------------------------------------------------
> ----------
> Bringing you mounds of caffeinated joy
> >>> http://thinkgeek.com/sf <<<
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
> ------------------------------------------------------------------
> ----------
> Bringing you mounds of caffeinated joy
> >>> http://thinkgeek.com/sf <<<
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
<?xml version="1.0" encoding="UTF-8"?>
<!-- ===================================================================== -->
<!-- -->
<!-- JBoss Server Configuration -->
<!-- -->
<!-- ===================================================================== -->
<server>
<!-- ==================================================================== -->
<!-- ConnectionManager setup for Oracle dbs -->
<!-- Build jmx-api (build/build.sh all) and view for config documentation -->
<!-- Thanks to Steven Coy -->
<!-- ==================================================================== -->
<mbean code="org.jboss.resource.connectionmanager.LocalTxConnectionManager" name="jboss.jca:service=LocalTxCM,name=OracleDS">
<!-- Include a login module configuration named OracleDbRealm.
Update your login-conf.xml, here is an example for a
ConfiguredIdentityLoginModule:
<application-policy name = "OracleDbRealm">
<authentication>
<login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
<module-option name = "principal">yourprincipal</module-option>
<module-option name = "userName">yourusername</module-option>
<module-option name = "password">yourpassword</module-option>
<module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=OracleDS</module-option>
</login-module>
</authentication>
</application-policy>
NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
module-option name = "managedConnectionFactoryName"
must match the object name of the ConnectionManager you are configuring here.
-->
<!--uncomment out this line if you are using the OracleDbRealm above
<attribute name="SecurityDomainJndiName">OracleDbRealm</attribute>
-->
<depends optional-attribute-name="ManagedConnectionFactoryName">
<!--embedded mbean-->
<mbean code="org.jboss.resource.connectionmanager.RARDeployment" name="jboss.jca:service=LocalTxDS,name=OracleDS">
<attribute name="JndiName">OracleDS</attribute>
<attribute name="ManagedConnectionFactoryProperties">
<properties>
<config-property name="ConnectionURL" type="java.lang.String">jdbc:oracle:thin:@localhost:1521:FABCONWB</config-property>
<config-property name="DriverClass" type="java.lang.String">oracle.jdbc.driver.OracleDriver</config-property>
<config-property name="UserName" type="java.lang.String">plm</config-property>
<config-property name="Password" type="java.lang.String">plm</config-property>
</properties>
</attribute>
<!--Below here are advanced properties -->
<!--hack-->
<depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper</depends>
</mbean>
</depends>
<depends optional-attribute-name="ManagedConnectionPool">
<!--embedded mbean-->
<mbean code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool" name="jboss.jca:service=LocalTxPool,name=OracleDS">
<attribute name="MinSize">0</attribute>
<attribute name="MaxSize">50</attribute>
<attribute name="BlockingTimeoutMillis">5000</attribute>
<attribute name="IdleTimeoutMinutes">15</attribute>
<!--criteria indicates if Subject (from security domain) or app supplied
parameters (such as from getConnection(user, pw)) are used to distinguish
connections in the pool. Choices are
ByContainerAndApplication (use both),
ByContainer (use Subject),
ByApplication (use app supplied params only),
ByNothing (all connections are equivalent, usually if adapter supports
reauthentication)-->
<attribute name="Criteria">ByContainer</attribute>
</mbean>
</depends>
<depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager</depends>
<depends optional-attribute-name="JaasSecurityManagerService">jboss.security:name=JaasSecurityManager</depends>
<attribute name="TransactionManager">java:/TransactionManager</attribute>
<!--make the rar deploy! hack till better deployment-->
<depends>jboss.jca:service=RARDeployer</depends>
</mbean>
</server>
