[jboss-cvs] JBossAS SVN: r100196 - projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Feb 1 00:47:49 EST 2010
Author: laubai
Date: 2010-02-01 00:47:48 -0500 (Mon, 01 Feb 2010)
New Revision: 100196
Modified:
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/EJB3.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/FAQ.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Feedback.xml
Log:
Edited FAQ.xml and Feedback.xml.
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/EJB3.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/EJB3.xml 2010-02-01 05:16:21 UTC (rev 100195)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/EJB3.xml 2010-02-01 05:47:48 UTC (rev 100196)
@@ -38,19 +38,19 @@
}
]]>
</programlisting>
-
+ <!--tsuzukeru-->
<para>When you invoke a session bean method, the method execution is automatically managed by the transaction manager and the security manager in the server. You can specify the transactional or security properties for each method using annotations on the method.</para>
<para>A session bean instance can be reused by many clients. Depending on whether the server maintains the bean's internal state between two clients, the session bean can be stateless or stateful. Depending on whether the bean has a remote business interface clients outside of the current JVM can call upon the EJB3 bean. All these are configurable via standard annotations on the beans. Note that the transactional or security properties are only active when the bean is called through a business interface.</para>
<para>After you define a session bean, how does the client get a reference to it? As we discussed, the client does not create or destroy EJB3 components, it merely asks the server for a reference of an existing instance managed by the server. That is done via JNDI. In JBoss Enterprise Web Platform, the default local JNDI name for a session bean is dependent on the deployment packaging of the bean class.</para>
-
+
<itemizedlist>
- <listitem><para>If the bean is deployed in a standalone JAR file in the <literal>JBOSS_DIST/default/deploy</literal> directory, the bean is accessible via local JNDI name <literal>MyBean/local</literal>, where <literal>MyBean</literal> is the implementation class name of the bean as we showed earlier. The "local" JNDI in JBoss AS means that the JNDI name is relative to <literal>java:comp/env/</literal>.</para></listitem>
- <listitem><para>If the JAR file containing the bean is packaged in an EAR file, the local JNDI name for the bean is <literal>myapp/MyBean/local</literal>, where <literal>myapp</literal> is the root name of the EAR archive file (e.g., <literal>myapp.ear</literal>, see later for the EAR packaging of EJB3 beans). </para></listitem>
+ <listitem><para>If the bean is deployed in a standalone JAR file in the <filename>$JBOSS_HOME/server/default/deploy</filename> directory, the bean is accessible via local JNDI name <literal>MyBean/local</literal>, where <literal>MyBean</literal> is the implementation class name of the bean as we showed earlier. A "local" JNDI name is relative to <literal>java:comp/env/</literal>.</para></listitem>
+ <listitem><para>If the JAR file containing the bean is packaged in an EAR file, the local JNDI name for the bean is <literal>myapp/MyBean/local</literal>, where <literal>myapp</literal> is the root name of the EAR archive file (for example, <filename>myapp.ear</filename>). </para></listitem>
</itemizedlist>
- <para>Of course, you should change <literal>local</literal> to <literal>remote</literal> if the bean interface is annotated with <literal>@Remote</literal> and the bean is accessed from outside of the server it is deployed on. Below is the code snippet to get a reference of the MyBean bean in a web application (e.g., in a servlet or a JSF backing bean) packaged in <literal>myapp.ear</literal>, and then invoke a managed method.</para>
+ <para>Of course, you should change <literal>local</literal> to <literal>remote</literal> if the bean interface is annotated with <literal>@Remote</literal> and the bean is accessed from outside of the server it is deployed on. Below is the code snippet to get a reference of the MyBean bean in a web application (for example, in a servlet or a JSF backing bean) packaged in <literal>myapp.ear</literal>, and then invoke a managed method.</para>
<programlisting>
<![CDATA[
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/FAQ.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/FAQ.xml 2010-02-01 05:16:21 UTC (rev 100195)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/FAQ.xml 2010-02-01 05:47:48 UTC (rev 100196)
@@ -4,45 +4,57 @@
<chapter id="faq">
<title>Frequently Asked Questions</title>
- <section><title>I have problems with Oracle XA?</title>
+ <section><title>I have problems with Oracle XA</title>
<para>
- <indexterm><primary>Frequently Asked Questions</primary></indexterm>
- Check that you:
- <orderedlist>
+ <indexterm><primary>Frequently Asked Questions</primary></indexterm>
+ Check the following:
+ </para>
+ <itemizedlist>
<listitem>
- <para> You have pad=true for the XidFactory? in conf/jboss-service.xml.
+ <para>Is <code>pad=true</code> for the <classname>XidFactory</classname> in <filename>conf/jboss-service.xml</filename>?
</para>
</listitem>
<listitem>
- <para>You have <track-connection-by-tx/> in your oracle-xa-ds.xml (not necessarily for JBoss Enterprise Web Platform 5.x where it is enabled by default and the element is deprecated).
+ <para>Is <code><track-connection-by-tx/></code> set in your <filename>oracle-xa-ds.xml</filename>? (This may not be required. The element is deprecated, and enabled by default.)
</para>
</listitem>
<listitem>
- <para>You have <isSameRM-override-value>false</isSameRM-override-value> in your oracle-xa-ds.xml.
+ <para>Is <code><isSameRM-override-value>false</isSameRM-override-value></code> set in your <filename>oracle-xa-ds.xml</filename>?
</para>
</listitem>
<listitem>
- <para>You have <no-tx-separate-pools/> in your oracle-xa-ds.xml.
+ <para>Is <code><no-tx-separate-pools/></code> set in your <filename>oracle-xa-ds.xml</filename>?
</para>
</listitem>
<listitem>
- <para>That your jbosscmp-jdbc.xml is specifying the same version of oracle as the one you use.
+ <para>Does <filename>jbosscmp-jdbc.xml</filename> specify the version of Oracle you are using?
</para>
</listitem>
<listitem>
- <para>That the oracle server you connect to has XA.
+ <para>Does the Oracle server you connect to support XA?
</para>
</listitem>
- </orderedlist>
-
- Configuring Oracle Database for XA Support You can configure Oracle database to support XA resources. This enables you to use JDBC 2.0-compliant Oracle driver. To XA-initialize Oracle database, complete the following steps:
+ </itemizedlist>
+ <para>
+ You can configure Oracle database to support XA resources. This enables you to use JDBC 2.0-compliant Oracle driver. To XA-initialize Oracle database, complete the following steps:
</para>
- <para>
- Make sure that Oracle JServer is installed with your database. If it is not installed, you must add it using Oracle Database Configuration Assistant. Choose "Change an Existing DB" and then select the database to which you want to add Oracle JServer. Choose "Next", then "Oracle JServer" and then "Finish". If the settings you have made to your database previously, are not suitable or insufficient for the Oracle JServer installation, the system prompts you to enter additional parameters. The database configuration file ( init.ora ) is located in <literal>\oracle\admin\<your_db_name>\pfile</literal> directory. Execute initxa.sql over your database. By default, this script file is located in <literal>\oracle\ora81\javavm\install</literal>. If errors occur during the execution of the file, you must execute the SQL statements from the file manually. Use DBA Studio to create a package and package body named JAVA_XA in SYS schema, and a synonym of this package (also named J!
AVA_XA) in PUBLIC schema.
- </para>
- <para>A slightly more detailed set of instructions can be found at <ulink url="http://www.ibm.com/developerworks/websphere/library/techarticles/0407_woolf/0407_woolf.html?ca=dnp-327#oracle_exception">Configuring and using XA distributed transactions in WebSphere Studio - Oracle Exception section</ulink>.</para>
+ <para>
+ Ensure that Oracle JServer is installed with your database. If it is not installed, add it using the <guiitem>Oracle Database Configuration Assistant</guiitem>.
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>Launch the <guiitem>Oracle Database Configuration Assistant</guiitem>. You can do this by typing <command>dbca</command> at the command prompt. In a Windows environment, you can launch it from the <guiitem>Start</guiitem> menu, under <guiitem>Configuration Assistants</guiitem>.</para>
+ </listitem>
+ <listitem><para>Select "Change an Existing DB".</para></listitem>
+ <listitem><para>Select the database to which you wish to add Oracle JServer. Then, click <guibutton>Next</guibutton>.</para></listitem>
+ <listitem><para>Select <guiitem>Oracle JServer</guiitem>, and then click <guibutton>Finish</guibutton>.</para></listitem>
+ </orderedlist>
+ <para>If your previous database settings are not suitable or insufficient for the Oracle JServer installation, you will be prompted to enter additional parameters. The database configuration file, <filename>init.ora</filename>, is located in <filename>\oracle\admin\$DATABASE_NAME\pfile</filename>.
+ </para>
+ <para>
+ Execute <command>initxa.sql</command> over your database. By default, this script is located in <filename>\oracle\ora81\javavm\install</filename>. If errors occur during execution, you must execute the SQL statements in the script manually.
+ </para>
+ <para>Use DBA Studio to create a package and package body named <literal>JAVA_XA</literal> in <literal>SYS</literal> schema, and an identically named <literal>JAVA_XA</literal> in <literal>PUBLIC</literal> schema.</para>
+ <para>More detailed instructions can be found at <ulink url="http://www.ibm.com/developerworks/websphere/library/techarticles/0407_woolf/0407_woolf.html?ca=dnp-327#oracle_exception">http://www.ibm.com/developerworks/websphere/library/techarticles/0407_woolf/0407_woolf.html?ca=dnp-327#oracle_exception</ulink>, <citetitle>Configuring and using XA distributed transactions in WebSphere Studio - OracleXAException</citetitle>.</para>
</section>
-
-
-
</chapter>
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Feedback.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Feedback.xml 2010-02-01 05:16:21 UTC (rev 100195)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Feedback.xml 2010-02-01 05:47:48 UTC (rev 100196)
@@ -5,22 +5,22 @@
<section id="We_Need_Feedback">
<title>Help Contribute</title>
<para>
- If you find a typographical error in the <citetitle>Administration and Configuration Guide</citetitle>, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in JIRA: <ulink url="http://jira.jboss.com">http://jira.jboss.com</ulink> against the project <citetitle>JBoss Application Server</citetitle> and component <citetitle>Documentation</citetitle>.
+ If you find a typographical error in the <citetitle>Administration and Configuration Guide</citetitle>, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in JIRA: <ulink url="http://jira.jboss.com">http://jira.jboss.com</ulink> against the project <citetitle>JBoss Enterprise Web Platform</citetitle> and component <citetitle>Documentation</citetitle>.
</para>
<para>
If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
</para>
- <note><title>Note</title><para>Be sure to give us your name so you can receive full credit.</para></note>
+ <!--<note><title>Note</title><para>Be sure to give us your name so you can receive full credit.</para></note>
<note><title>Note</title><para>This content is taken from svn.jboss.org/repos/jbossas/projects/docs/trunk and has yet to be branched.</para></note>
<para>To access the content directly and make changes yourself:</para>
-<screen>svn co https://svn.jboss.org/repos/jbossas/projects/docs/trunk/AS_5/Administration_And_Configuration_Guide/ --username yourname
+<screen>svn co https://svn.jboss.org/repos/jbossas/projects/docs/trunk/AS_5/Administration_And_Configuration_Guide/ username yourname
</screen>
<para>The directory structure includes other languages the book will be translated in. For English please edit the files under <emphasis>en-US</emphasis>.
</para>
<para>To identify the filename you wish to edit, please check the chapter title which will match the file's name. The files are written in Docbook xml. After saving your changes please validate the files you've edited for errors before committing your changes.
- </para>
+ </para>-->
</section>
More information about the jboss-cvs-commits
mailing list