User: d_jencks
Date: 01/12/21 08:34:12
Modified: src/xdocs jbossdocs.xml resource.xml
Added: src/xdocs jbosscx-feature-matrix.xml
Log:
Changed jca docs to reflect depends element replacing mbean-ref element. Added
jbosscx feature matrix
Revision Changes Path
3.3 +3 -1 manual/src/xdocs/jbossdocs.xml
Index: jbossdocs.xml
===================================================================
RCS file: /cvsroot/jboss/manual/src/xdocs/jbossdocs.xml,v
retrieving revision 3.2
retrieving revision 3.3
diff -u -r3.2 -r3.3
--- jbossdocs.xml 2001/11/29 01:27:32 3.2
+++ jbossdocs.xml 2001/12/21 16:34:12 3.3
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!-- $Id: jbossdocs.xml,v 3.2 2001/11/29 01:27:32 dsundstrom Exp $ -->
+<!-- $Id: jbossdocs.xml,v 3.3 2001/12/21 16:34:12 d_jencks Exp $ -->
<!DOCTYPE book SYSTEM "file:@oasis.docbook.xml.root@/docbookx.dtd" [
<!ENTITY preface.xml SYSTEM "preface.xml">
<!ENTITY jbossintro.xml SYSTEM "jbossintro.xml">
@@ -40,6 +40,7 @@
<!ENTITY howtossl.xml SYSTEM "howto/howtossl.xml">
<!ENTITY howtoclustering.xml SYSTEM "howto/howtoclustering.xml">
<!ENTITY faq.xml SYSTEM "faq.xml">
+ <!ENTITY jbosscxfeaturematrix.xml SYSTEM "jbosscx-feature-matrix.xml">
]>
<book>
@@ -57,6 +58,7 @@
&jbossintro.xml;
&basicconfiguration.xml;
&resource.xml;
+ &jbosscxfeaturematrix.xml;
&cmp.xml;
&customizingjaws.xml;
&advconfig.xml;
3.5 +30 -22 manual/src/xdocs/resource.xml
Index: resource.xml
===================================================================
RCS file: /cvsroot/jboss/manual/src/xdocs/resource.xml,v
retrieving revision 3.4
retrieving revision 3.5
diff -u -r3.4 -r3.5
--- resource.xml 2001/12/01 02:17:42 3.4
+++ resource.xml 2001/12/21 16:34:12 3.5
@@ -1,4 +1,11 @@
<?xml version="1.0" encoding="UTF-8"?>
+<!--DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
+
+ "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"-->
+
+<!--DOCTYPE chapter SYSTEM
"file://usr/java/jboss/co6/jboss-all/thirdparty/oasis/docbook-xml/docbookx.dtd"-->
+
+
<chapter id="resource">
<title>Using Databases and other Enterprise Resources</title>
<para>
@@ -13,10 +20,10 @@
<title>Introduction</title>
<section id="resource-intro-access">
<title>Access to Resource Managers</title>
- <para>This chapter is primarily relevant to jboss 3.0 (rabbithole)</para>
+ <para><emphasis>THIS CHAPTER IS PRIMARILY RELEVANT TO JBOSS 3
(RABBITHOLE)</emphasis></para>
<para>In order for your ejbs to do much useful work, they will need to
communicate with a transactional resource manager such as a relational database,
transactional message queue, or other enterprise information system. Jboss now
supports all such communication using Resource Adapters following the <ulink url =
"http://java.sun.com/j2ee/connector/";><citetitle>jca 1.0
specification</citetitle></ulink>. This technology provides a uniform way to combine
the application server's transaction management and connection pooling functionalities
with a resource adapter's ability to connect to and do work with a resource
manager.</para>
- <para>Jboss provides the ability to deploy any compliant resource adapter,
and connections from any adapter may be pooled by jboss, obtained from connection
factories bound in jndi, and used by client code. At the moment, however, only
connection factories implementing javax.sql.DataSource and connections implementing
java.sql.Connection may be used with CMP beans and JAWS to automate database
access.</para>
- <para>Since few database vendors have supplied resource adapters for their
database products, the usual strategy for accessing relational databases consists of
using a generic resource adapter that wraps a jdbc driver into a jca resource adapter.
Jboss comes with two such adapters, one for jdbc 1 drivers without xa transaction
support, and one for jdbc 2 drivers implementing xa support with XADataSource and
XAConnection.</para>
+ <para>Jboss provides the ability to deploy any compliant resource adapter,
and connections from any adapter may be pooled by jboss, obtained from connection
factories bound in jndi, and used by client code. At the moment, however, only
connection factories implementing javax.sql.DataSource and connections implementing
java.sql.Connection may be used with CMP beans and the jboss ejb persistence manager
to automate database access.</para>
+ <para>Since few database vendors have supplied resource adapters for their
database products, the usual strategy for accessing relational databases consists of
using a generic resource adapter that wraps a jdbc driver into a jca resource adapter.
Jboss comes with two such adapters, one for jdbc 1 drivers without xa transaction
support, and one for jdbc 2 drivers implementing xa support with XADataSource,
XAResource, and XAConnection.</para>
<para>As well as providing a systematic, well thought out framework for
pooling and transaction control that can be used for relational databases, jca also
provides another specification ("cci") for connection factories and connections
unrelated to jdbc. An adaptor could use these to provide predefined access to stored
procedures in a relational database, or these could be used to access a message que,
or enterprise information system such as CICS or SAP. Although there are no
particular conceptual difficulties in using such resource adapters to automatically
manage persistence of CMP beans, support for this is not yet integrated into jboss.
</para>
</section>
<section id="resource-intro-pooling">
@@ -87,12 +94,12 @@
<listitem>
<formalpara>
<title>(attribute)TransactionManagerName</title>
- <para>This is the jndi name of the transaction manager to hook up
transactions from. Normally it is java:/TransactionManager. This may concievably be
changed to an mbean-ref at some time in the future.</para>
+ <para>This is the jndi name of the transaction manager to hook up
transactions from. Normally it is java:/TransactionManager. This may concievably be
changed to an depends at some time in the future.</para>
</formalpara>
</listitem>
<listitem>
<formalpara>
- <title>(mbean-ref)ResourceAdapterName</title>
+ <title>(depends)ResourceAdapterName</title>
<para>This is the (string representation of) the ObjectName of
the RARDeployment set up by the RARDeployer when it deploys the needed rar. The
connection factory loader will not be started until this mbean is present. The object
names look like this: JCA:service=RARDeployment,name=[display name of rar]. </para>
</formalpara>
</listitem>
@@ -104,7 +111,7 @@
</listitem>
<listitem>
<formalpara>
- <title>(mbean-ref)ConnectionManagerFactoryLoaderName</title>
+ <title>(depends)ConnectionManagerFactoryLoaderName</title>
<para>This is the mbean ObjectName of a
ConnectionManagerFactoryLoader. By specifying the ConnectionManagerFactoryLoader, you
are specifying what kind of connection manager you want to use. There are three
choices supplied with JBoss providing different levels of transaction support: none,
local, and xa. They all rely on the same pooling code, although they will behave
differently when receiving multiple requests for a connection from within the same
transaction. If you wish to provide alternate pooling or other ConnectionManager
functionality, you must provide both a ConnectionManager and a
ConnectionManagerFactory, and provide a ConnectionManagerFactoryLoader configuration
section in jboss.jcml to make the factory available. The ConnectionFactoryLoader will
not be started until the ConnectionManagerFactoryLoader is available. The three
supplied ConnectionManagerFactoryLoaders have ObjectNames:
JCA:service=ConnectionManagerFactoryLoader,name=MinervaNoTransCMFactory,
JCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory, and
JCA:service=ConnectionManagerFactoryLoader,name=MinervaXACMFactory.</para>
</formalpara>
</listitem>
@@ -231,6 +238,7 @@
<section id="resource-db-specific">
<title>Examples for specific databases</title>
<para>Please contribute your working example now!</para>
+ <para><emphasis>IMPORTANT: THESE EXAMPLES ARE FOR POST JBOSS3.0ALPHA ONLY!
THEY WILL NOT WORK ON JBOSS 2.4.x. TO ADAPT THEM TO JBOSS3.0ALPHA, REPLACE "depends"
WITH "mbean-ref" AND "optional-attribute-name=" WITH "name="</emphasis></para>
<section id="firebirdsql">
<title>firebirdsql</title>
@@ -266,8 +274,8 @@
<attribute
name="ManagedConnectionFactoryProperties">Database=localhost/3050:/usr/java/jboss/co6/jboss-all/build/output/jboss-3.0.0alpha/db/firebirdsql/jbosstest.gdb</attribute>
<attribute name="JndiName">DefaultDS</attribute>
<attribute name="TransactionManagerName">java:/TransactionManager</attribute>
- <mbean-ref name="ResourceAdapterName">JCA:service=RARDeployment,name=Firebird
Database Connector</mbean-ref>
- <mbean-ref
name="ConnectionManagerFactoryLoaderName">JCA:service=ConnectionManagerFactoryLoader,name=MinervaXACMFactory</mbean-ref>
+ <depends
optional-attribute-name="ResourceAdapterName">JCA:service=RARDeployment,name=Firebird
Database Connector</depends>
+ <depends
optional-attribute-name="ConnectionManagerFactoryLoaderName">JCA:service=ConnectionManagerFactoryLoader,name=MinervaXACMFactory</depends>
<attribute name="ConnectionManagerProperties">#
BlockingTimeoutMillis=500000
IdleTimeoutMinutes=30
@@ -332,9 +340,9 @@
</attribute>
<attribute name="JndiName">MSSQL2000DS</attribute>
<attribute name="TransactionManagerName">java:/TransactionManager</attribute>
- <mbean-ref name="ResourceAdapterName">JCA:service=RARDeployment,name=Minerva
-JDBC LocalTransaction ResourceAdapter</mbean-ref>
- <mbean-ref
name="ConnectionManagerFactoryLoaderName">JCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory</mbean-ref>
+ <depends
optional-attribute-name="ResourceAdapterName">JCA:service=RARDeployment,name=Minerva
+JDBC LocalTransaction ResourceAdapter</depends>
+ <depends
optional-attribute-name="ConnectionManagerFactoryLoaderName">JCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory</depends>
<attribute name="ConnectionManagerProperties">#
#Wed Aug 15 16:17:29 EDT 2001
BlockingTimeoutMillis=50000
@@ -375,7 +383,7 @@
<!-- -->
<!-- ===================================================================== -->
-<!-- $Id: resource.xml,v 3.4 2001/12/01 02:17:42 d_jencks Exp $ -->
+<!-- $Id: resource.xml,v 3.5 2001/12/21 16:34:12 d_jencks Exp $ -->
<server>
@@ -396,8 +404,8 @@
UserName=</attribute>
<attribute name="JndiName">fooDS</attribute>
<attribute name="TransactionManagerName">java:/TransactionManager</attribute>
- <mbean-ref name="ResourceAdapterName">JCA:service=RARDeployment,name=Minerva
JDBC LocalTransaction ResourceAdapter</mbean-ref>
- <mbean-ref
name="ConnectionManagerFactoryLoaderName">JCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory</mbean-ref>
+ <depends
optional-attribute-name="ResourceAdapterName">JCA:service=RARDeployment,name=Minerva
JDBC LocalTransaction ResourceAdapter</depends>
+ <depends
optional-attribute-name="ConnectionManagerFactoryLoaderName">JCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory</depends>
<attribute name="ConnectionManagerProperties">#
#Wed Aug 15 16:17:29 EDT 2001
BlockingTimeoutMillis=500000
@@ -455,8 +463,8 @@
</attribute>
<attribute name="JndiName">OracleDS</attribute>
<attribute name="TransactionManagerName">java:/TransactionManager</attribute>
- <mbean-ref name="ResourceAdapterName">JCA:service=RARDeployment,name=Minerva
JDBC LocalTransaction ResourceAdapter</mbean-ref>
- <mbean-ref
name="ConnectionManagerFactoryLoaderName">JCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory</mbean-ref>
+ <depends
optional-attribute-name="ResourceAdapterName">JCA:service=RARDeployment,name=Minerva
JDBC LocalTransaction ResourceAdapter</depends>
+ <depends
optional-attribute-name="ConnectionManagerFactoryLoaderName">JCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory</depends>
<attribute name="ConnectionManagerProperties">#
#Wed Aug 15 16:17:29 EDT 2001
BlockingTimeoutMillis=50000
@@ -493,7 +501,7 @@
<!-- -->
<!-- ===================================================================== -->
-<!-- $Id: resource.xml,v 3.4 2001/12/01 02:17:42 d_jencks Exp $ -->
+<!-- $Id: resource.xml,v 3.5 2001/12/21 16:34:12 d_jencks Exp $ -->
<server>
@@ -513,8 +521,8 @@
Password=postgres</attribute>
<attribute name="JndiName">FooPostgresDS</attribute>
<attribute name="TransactionManagerName">java:/TransactionManager</attribute>
- <mbean-ref name="ResourceAdapterName">JCA:service=RARDeployment,name=Minerva
JDBC LocalTransaction ResourceAdapter</mbean-ref>
- <mbean-ref
name="ConnectionManagerFactoryLoaderName">JCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory</mbean-ref>
+ <depends
optional-attribute-name="ResourceAdapterName">JCA:service=RARDeployment,name=Minerva
JDBC LocalTransaction ResourceAdapter</depends>
+ <depends
optional-attribute-name="ConnectionManagerFactoryLoaderName">JCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory</depends>
<attribute name="ConnectionManagerProperties">#
#Wed Aug 15 16:17:29 EDT 2001
BlockingTimeoutMillis=500000
@@ -562,9 +570,9 @@
<attribute name="TransactionManagerName">java:/TransactionManager</attribute>
- <mbean-ref name="ResourceAdapterName">JCA:service=RARDeployment,name=Minerva
-JDBC LocalTransaction ResourceAdapter</mbean-ref>
- <mbean-ref
name="ConnectionManagerFactoryLoaderName">JCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory</mbean-ref>
+ <depends
optional-attribute-name="ResourceAdapterName">JCA:service=RARDeployment,name=Minerva
+JDBC LocalTransaction ResourceAdapter</depends>
+ <depends
optional-attribute-name="ConnectionManagerFactoryLoaderName">JCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory</depends>
<attribute name="ConnectionManagerProperties">#
#Wed Aug 15 16:17:29 EDT 2001
3.1 manual/src/xdocs/jbosscx-feature-matrix.xml
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
