User: d_jencks
Date: 02/02/06 08:16:04
Modified: src/xdocs resource.xml
Log:
added SAP R/3 example
Revision Changes Path
3.9 +9 -3 manual/src/xdocs/resource.xml
Index: resource.xml
===================================================================
RCS file: /cvsroot/jboss/manual/src/xdocs/resource.xml,v
retrieving revision 3.8
retrieving revision 3.9
diff -u -r3.8 -r3.9
--- resource.xml 2002/01/14 01:14:43 3.8
+++ resource.xml 2002/02/06 16:16:04 3.9
@@ -270,6 +270,12 @@
<ulink url =
"http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/manual/src/examples/resources/jca/postgres-service.xml";><citetitle>Postgres
database</citetitle></ulink>
</para>
</listitem>
+
+ <listitem>
+ <para>
+ <ulink url =
"http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/manual/src/examples/resources/jca/sapr3-service.xml";><citetitle>SAP
R/3 ERP system, inqmy connector</citetitle></ulink>
+ </para>
+ </listitem>
</orderedlist>
</para>
@@ -277,9 +283,9 @@
<section id="resource-migration">
<title>Migration from older jboss versions</title>
<para>Previous versions of jboss provided database connectivity and
connection pooling through the XADataSourceLoaderMBean. This was normally used with
the XADataSourceImpl, which provided an xa interface for a non-xa jdbc driver. Of
course, since the underlying driver did not support xa transactions, neither did the
XA wrapper. These drivers can now be used with the Minerva JDBC LocalTransaction
ResourceAdapter, which works with the transaction manager using local, non-xa
transactions, eliminating the confusion of imitating but not implementing xa
semantics. If you have a true XADataSource implementation for your database, you can
instead use the Minerva JDBC XATransaction ResourceAdapter, which provides full xa
support.</para>
- <para>Most of the parameters in an XADataSourceLoader configuration have
direct parallels in a ConnectionFactoryLoader configuration. The table below
indicates the correspondence with notes on areas of non-equivalence.</para>
- <para>COMING SOON.... The following is incomplete.</para>
- <para>The migration results in the following conversions:
+ <para>Most of the parameters in an XADataSourceLoader configuration have
direct parallels in a ConnectionFactoryLoader configuration.</para>
+ <para>Normally the easiest migration path is to select a configuration example
for your database from the provided examples and to modify it until it works. If you
find errors or work out a configuration for a database for which there is no example,
please contribute back to the JBoss community by supplying us with your configuration.
Questions on this subject should be asked in the Database and Persistence
forum.</para>
+ <para>Migration results in the following conversions:
<orderedlist>
<listitem>
<para>An XADataSourceLoader using the XADataSourceImpl wrapper converts
to the LocalTransaction resource adapter and the LocalTransaction pool.</para>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
