[jboss-cvs] JBossAS SVN: r101447 - in projects/docs/enterprise/EWP_5.0: Getting_Started_Guide/en-US and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Feb 25 01:39:15 EST 2010
Author: laubai
Date: 2010-02-25 01:39:14 -0500 (Thu, 25 Feb 2010)
New Revision: 101447
Modified:
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Book_Info.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Cache.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Revision_History.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Web_Services.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Book_Info.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/JNDIView_Service.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Revision_History.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml
Log:
Corrections for JBPAPP-3363, JBPAPP-3361.
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Book_Info.xml 2010-02-25 06:12:19 UTC (rev 101446)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Book_Info.xml 2010-02-25 06:39:14 UTC (rev 101447)
@@ -7,7 +7,7 @@
<subtitle>for JBoss Enterprise Web Platform 5.0</subtitle>
<edition>1</edition>
<issuenum>1</issuenum>
- <pubsnumber>1.6</pubsnumber>
+ <pubsnumber>1.8</pubsnumber>
<productname>JBoss Enterprise Web Platform</productname>
<productnumber>5.0</productnumber>
<!-- <pubdate>, 2009</pubdate> -->
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Cache.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Cache.xml 2010-02-25 06:12:19 UTC (rev 101446)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Cache.xml 2010-02-25 06:39:14 UTC (rev 101447)
@@ -582,10 +582,10 @@
</table>-->
<para>
- In the JBoss Enterprise Web Platform 5, JBoss Cache runs in the <literal>all</literal> configuration of the Enterprise Web Platform (for instance, <filename>$JBOSS_HOME/server/all</filename>). All you need to do is start the server with this configuration.
+ In the JBoss Enterprise Web Platform 5, JBoss Cache runs in the <literal>production</literal> configuration of the Enterprise Web Platform (for instance, <filename>$JBOSS_HOME/server/production</filename>). All you need to do is start the server with this configuration.
</para>
<screen>
-$JBOSS_HOME/bin/./run.sh -c all
+$JBOSS_HOME/bin/./run.sh -c production
</screen>
<para>
All required JARs will be on the classpath. Otherwise, you will need to ensure <filename>jbosscache.jar</filename> and <filename>jgroups-all.jar</filename> are on the classpath. You may need to add other JARs if you are using things like <classname>JdbmCacheLoader</classname>. The simplest way to do this is to copy the jars from the JBoss Cache distribution's <filename>lib</filename> directory to the <filename>lib</filename> directory of your <literal>all</literal> configuration. You could also package the JARs with the configuration file in a Service Archive (SAR) file or an EAR. </para>
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Revision_History.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Revision_History.xml 2010-02-25 06:12:19 UTC (rev 101446)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Revision_History.xml 2010-02-25 06:39:14 UTC (rev 101447)
@@ -8,8 +8,8 @@
<simpara>
<revhistory>
<revision>
- <revnumber>2.6</revnumber>
- <date>Wed Feb 10 2010</date>
+ <revnumber>2.8</revnumber>
+ <date>Thu Feb 25 2010</date>
<author>
<firstname>Laura</firstname>
<surname>Bailey</surname>
@@ -17,7 +17,7 @@
</author>
<revdescription>
<simplelist>
- <member>Updates for JBPAPP-3491.</member>
+ <member>JIRA corrections.</member>
</simplelist>
</revdescription>
</revision>
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Web_Services.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Web_Services.xml 2010-02-25 06:12:19 UTC (rev 101446)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Web_Services.xml 2010-02-25 06:39:14 UTC (rev 101447)
@@ -1749,7 +1749,8 @@
<para>Where users will put the provider JAR is mostly up to them, although with JDK5 the best (and in some cases only) place to have it is in <filename>$JAVA_HOME/jre/lib/ext</filename>. Under Windows there will normally be a JRE and a JDK install of Java. If an installation does not work despite apparently correct installation, it is likely that the provider installation has not been used.</para>
</section>
</section>
-
+
+ </section>
<section>
<title>JBossWS Extensions</title>
<para>This section describes proprietary JBoss extensions to JAX-WS.</para>
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Book_Info.xml 2010-02-25 06:12:19 UTC (rev 101446)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Book_Info.xml 2010-02-25 06:39:14 UTC (rev 101447)
@@ -5,7 +5,7 @@
<title>Getting Started Guide</title>
<subtitle>for Use with JBoss Enterprise Web Platform 5.0</subtitle>
<edition>1.0</edition>
- <pubsnumber>33.2</pubsnumber>
+ <pubsnumber>33.4</pubsnumber>
<productname>JBoss Enterprise Web Platform</productname>
<productnumber>5.0</productnumber>
<!-- <pubdate>, 2009</pubdate> --><isbn>N/A</isbn>
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/JNDIView_Service.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/JNDIView_Service.xml 2010-02-25 06:12:19 UTC (rev 101446)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/JNDIView_Service.xml 2010-02-25 06:39:14 UTC (rev 101447)
@@ -10,66 +10,42 @@
</para>
<screen>
java: Namespace
-
-+- securityManagement (class: org.jboss.security.integration.JNDIBasedSecurityManagement)
-+- comp (class: javax.namingMain.Context)
-+- XAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
-+- JmsXA (class: org.jboss.resource.adapter.jms.JmsConnectionFactoryImpl)
-+- policyRegistration (class: org.jboss.security.plugins.JBossPolicyRegistration)
-+- TransactionPropagationContextImporter (class: com.arjuna.ats.internal.jbossatx.jta.PropagationContextManager)
-+- app (class: org.jnp.interfaces.NamingContext)
-| +- Manager (class: javax.inject.manager.Manager)
-+- ClusteredConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
-+- Mail (class: javax.mail.Session)
-+- TransactionPropagationContextExporter (class: com.arjuna.ats.internal.jbossatx.jta.PropagationContextManager)
-+- ProfileService (class: org.jboss.system.server.profileservice.repository.AbstractProfileService)
-+- DefaultDS (class: org.jboss.resource.adapter.jdbc.WrapperDataSource)
-+- jaas (class: javax.naming.Context)
-| +- HsqlDbRealm (class: org.jboss.security.plugins.SecurityDomainContext)
-+- ClusteredXAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
-+- TransactionSynchronizationRegistry (class:
- com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple)
-+- SecurityProxyFactory (class: org.jboss.security.SubjectSecurityProxyFactory)
-+- ConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
-+- DefaultJMSProvider (class: org.jboss.jms.jndi.JNDIProviderAdapter)
-+- TransactionManager (class: com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate)
-+- timedCacheFactory (class: javax.naming.Context)
+
+ +- securityManagement (class: org.jboss.security.integration.JNDIBasedSecurityManagement)
+ +- comp (class: javax.namingMain.Context)
+ +- TransactionPropagationContextImporter (class: com.arjuna.ats.internal.jbossatx.jta.PropagationContextManager)
+ +- policyRegistration (class: org.jboss.security.plugins.JBossPolicyRegistration)
+ +- Mail (class: javax.mail.Session)
+ +- TransactionPropagationContextExporter (class: com.arjuna.ats.internal.jbossatx.jta.PropagationContextManager)
+ +- ProfileService (class: org.jboss.system.server.profileservice.repository.AbstractProfileService)
+ +- DefaultDS (class: org.jboss.resource.adapter.jdbc.WrapperDataSource)
+ +- jaas (class: javax.naming.Context)
+ | +- HsqlDbRealm (class: org.jboss.security.plugins.SecurityDomainContext)
+ +- TransactionSynchronizationRegistry (class: com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple)
+ +- SecurityProxyFactory (class: org.jboss.security.SubjectSecurityProxyFactory)
+ +- TransactionManager (class: com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate)
+ +- timedCacheFactory (class: javax.naming.Context)
Failed to lookup: timedCacheFactory, errmsg=org.jboss.util.TimedCachePolicy cannot be cast to javax.naming.NamingEnumeration
-
-
+
Global JNDI Namespace
-
-+- UserTransactionSessionFactory (proxy: $Proxy109 implements interface org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory)
-+- UUIDKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactory)
-+- HiLoKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory)
-+- SecureDeploymentManager (class: org.jnp.interfaces.NamingContext)
-| +- remote[link -> DeploymentManager] (class: javax.naming.LinkRef)
-+- SecureManagementView (class: org.jnp.interfaces.NamingContext)
-| +- remote[link -> ManagementView] (class: javax.naming.LinkRef)
-+- persistence.unit:unitName=jsfejb3.ear (class: org.jnp.interfaces.NamingContext)
-| +- app.jar#helloworld (class: org.hibernate.impl.SessionFactoryImpl)
-+- DeploymentManager (class: org.jboss.aop.generatedproxies.AOPProxy$4)
-+- XAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
-+- topic (class: org.jnp.interfaces.NamingContext)
-+- ClusteredConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
-+- ProfileService (class: org.jboss.aop.generatedproxies.AOPProxy$2)
-+- SecureProfileService (class: org.jnp.interfaces.NamingContext)
-| +- remote[link -> ProfileService] (class: javax.naming.LinkRef)
-+- queue (class: org.jnp.interfaces.NamingContext)
-| +- DLQ (class: org.jboss.jms.destination.JBossQueue)
-| +- ExpiryQueue (class: org.jboss.jms.destination.JBossQueue)
-+- ClusteredXAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
-+- UserTransaction (class: org.jboss.tm.usertx.client.ClientUserTransaction)
-+- ConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
-+- jmx (class: org.jnp.interfaces.NamingContext)
-| +- invoker (class: org.jnp.interfaces.NamingContext)
-| | +- RMIAdaptor (proxy: $Proxy103 implements interface org.jboss.jmx.adaptor.rmi.RMIAdaptor,interface org.jboss.jmx.adaptor.rmi.RMIAdaptorExt)
-| +- rmi (class: org.jnp.interfaces.NamingContext)
-| | +- RMIAdaptor[link -> jmx/invoker/RMIAdaptor] (class: javax.naming.LinkRef)
-+- TomcatAuthenticators (class: java.util.Properties)
-+- console (class: org.jnp.interfaces.NamingContext)
-| +- PluginManager (proxy: $Proxy104 implements interface org.jboss.console.manager.PluginManagerMBean)
-+- ManagementView (class: org.jboss.aop.generatedproxies.AOPProxy$3)
+
+ +- UserTransactionSessionFactory (proxy: $Proxy93 implements interface org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory)
+ +- SecureDeploymentManager (class: org.jnp.interfaces.NamingContext)
+ | +- remote[link -> DeploymentManager] (class: javax.naming.LinkRef)
+ +- SecureManagementView (class: org.jnp.interfaces.NamingContext)
+ | +- remote[link -> ManagementView] (class: javax.naming.LinkRef)
+ +- DeploymentManager (class: org.jboss.aop.generatedproxies.AOPProxy$4)
+ +- ProfileService (class: org.jboss.aop.generatedproxies.AOPProxy$2)
+ +- SecureProfileService (class: org.jnp.interfaces.NamingContext)
+ | +- remote[link -> ProfileService] (class: javax.naming.LinkRef)
+ +- UserTransaction (class: org.jboss.tm.usertx.client.ClientUserTransaction)
+ +- jmx (class: org.jnp.interfaces.NamingContext)
+ | +- invoker (class: org.jnp.interfaces.NamingContext)
+ | | +- RMIAdaptor (proxy: $Proxy89 implements interface org.jboss.jmx.adaptor.rmi.RMIAdaptor,interface org.jboss.jmx.adaptor.rmi.RMIAdaptorExt)
+ | +- rmi (class: org.jnp.interfaces.NamingContext)
+ | | +- RMIAdaptor[link -> jmx/invoker/RMIAdaptor] (class: javax.naming.LinkRef)
+ +- TomcatAuthenticators (class: java.util.Properties)
+ +- ManagementView (class: org.jboss.aop.generatedproxies.AOPProxy$3)
</screen>
<para>
This details the JNDI names to which your EJBs are bound.
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Revision_History.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Revision_History.xml 2010-02-25 06:12:19 UTC (rev 101446)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Revision_History.xml 2010-02-25 06:39:14 UTC (rev 101447)
@@ -7,8 +7,8 @@
<simpara>
<revhistory>
<revision>
- <revnumber>1.7</revnumber>
- <date>Thu Feb 11 2010</date>
+ <revnumber>1.9</revnumber>
+ <date>Wed Feb 17 2010</date>
<author>
<firstname>Laura</firstname>
<surname>Bailey</surname>
@@ -16,7 +16,7 @@
</author>
<revdescription>
<simplelist>
- <member>JIRA corrections.</member>
+ <member>Corrected description of services.</member>
</simplelist>
</revdescription>
</revision>
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2010-02-25 06:12:19 UTC (rev 101446)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2010-02-25 06:39:14 UTC (rev 101447)
@@ -410,7 +410,7 @@
</footnote>
</para>
<para>
- The JMX Console isn't the only web based management interface to JBoss. There is also the Web Console. Although it's a Java applet, the corresponding web application can be secured in the same way as the JMX Console. The Web Console is in the file <filename>deploy/management/console-mgr.sar/web-console.war.</filename>. The only difference is that the Web Console is provided as a simple WAR file instead of using the exploded directory structure that the JMX Console did. The only real difference between the two is that editing the files inside the WAR file is a bit more cumbersome.
+ The JMX Console is not the only web-based management interface in JBoss Enterprise Web Platform. The Enterprise Web Platform Administration Console is located in <filename>deploy/admin-console.war</filename> and shares the security domain associated with the JMX Console. For more information, refer to the <citetitle>Administration Console User Guide</citetitle>, available from <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Web_Platform/">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Web_Platform/</ulink>. <!--There is also the Web Console. Although it's a Java applet, the corresponding web application can be secured in the same way as the JMX Console. The Web Console is in the file <filename>deploy/management/console-mgr.sar/web-console.war.</filename>. The only difference is that the Web Console is provided as a simple WAR file instead of using the exploded directory structure that the JMX Console did. The only real difference between the two is that!
editing the files inside the WAR file is a bit more cumbersome.-->
</para>
</section>
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml 2010-02-25 06:12:19 UTC (rev 101446)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml 2010-02-25 06:39:14 UTC (rev 101447)
@@ -23,7 +23,7 @@
Local transaction datasources are configured using the <literal>local-tx-datasource</literal> element and XA-compliant ones using <literal>xa-tx-datasource</literal>. The example file <filename>generic-ds.xml</filename> shows how to use both types and also some of the other elements that are available for things like connection pool configuration. Examples of both local and XA configurations are available for Oracle, DB2 and Informix.
</para>
<para>
- If you look at the example files <filename> firebird-ds.xml</filename>, <filename> facets-ds.xml</filename> and <filename>sap3-ds.xml</filename>, you’ll notice that they have a completely different format, with the root element being <literal>connection-factories</literal> rather than <literal>datasources</literal>. These use an alternative, more generic JCA configuration syntax used with a pre-packaged JCA resource adapter. The syntax is not specific to datasource configuration and is used, for example, in the <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/deploy/messaging/jms-ds.xml</filename> file to configure the JMS resource adapter.
+ If you look at the example files <filename> firebird-ds.xml</filename>, <filename> facets-ds.xml</filename> and <filename>sap3-ds.xml</filename>, you’ll notice that they have a completely different format, with the root element being <literal>connection-factories</literal> rather than <literal>datasources</literal>. These use an alternative, more generic JCA configuration syntax used with a pre-packaged JCA resource adapter. The syntax is not specific to datasource configuration.
</para>
<para>
Next, we’ll work through some step-by-step examples to illustrate what’s involved setting up a datasource for a specific database.
@@ -123,13 +123,13 @@
- <section id="Using_MySQL_as_the_Default_DataSource-Testing_the_MySQL_DataSource">
+<!-- <section id="Using_MySQL_as_the_Default_DataSource-Testing_the_MySQL_DataSource">
<title>Testing the MySQL DataSource</title>
<para>
Using the test client described in <xref linkend="creating_a_jdbc_client"/>, you may now verify the proper installation of your datasource.
</para>
- </section>
+ </section>-->
</section>
@@ -243,12 +243,12 @@
</para>
-<section id="testing_the_datasource"><title>Testing the datasource</title>
+<!--<section id="testing_the_datasource"><title>Testing the datasource</title>
<para>Using the test client described in <xref linkend="creating_a_jdbc_client"/>, you may now verify the proper installation of your datasource.
</para>
</section>
- </section>
-</section>
+ </section>-->
+</section>
<!-- <section id="configuring_jbossmessaging_persistence_manager"><title>Configuring JBoss Messaging Persistence Manager</title>
@@ -277,7 +277,7 @@
</section> -->
-<section id="creating_a_jdbc_client"><title>Creating a JDBC client</title>
+<!--<section id="creating_a_jdbc_client"><title>Creating a JDBC client</title>
<para>
When testing a newly configured datasource we suggest using some very basic JDBC client code embedded in a JSP page.
First of all, you should create an exploded WAR archive under the deploy directory which is simply a folder named "<literal>jdbcclient.war</literal>".
@@ -322,6 +322,6 @@
</screen>
</para>
-</section>
-
+</section>-->
+ </section>
</chapter>
More information about the jboss-cvs-commits
mailing list