[jboss-cvs] JBoss Messaging SVN: r2751 - in trunk/docs/examples: http and 8 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Jun 1 08:56:11 EDT 2007
Author: timfox
Date: 2007-06-01 08:56:11 -0400 (Fri, 01 Jun 2007)
New Revision: 2751
Modified:
trunk/docs/examples/ejb3mdb/README.html
trunk/docs/examples/http/README.html
trunk/docs/examples/mdb-failure/README.html
trunk/docs/examples/mdb/README.html
trunk/docs/examples/queue-failover/README.html
trunk/docs/examples/secure-socket/README.html
trunk/docs/examples/stateless-clustered/README.html
trunk/docs/examples/stateless/README.html
trunk/docs/examples/topic/README.html
trunk/docs/examples/web-service/README.html
Log:
More updates to readmes
Modified: trunk/docs/examples/ejb3mdb/README.html
===================================================================
--- trunk/docs/examples/ejb3mdb/README.html 2007-06-01 12:45:00 UTC (rev 2750)
+++ trunk/docs/examples/ejb3mdb/README.html 2007-06-01 12:56:11 UTC (rev 2751)
@@ -134,109 +134,7 @@
security domain. Follow the instructions from the "Installation"
paragraph of the release documentation. <br>
<br>
-<big><span style="font-weight: bold;">3. The example fails with <small>"<span
- style="font-family: courier new,courier,monospace;">Have not received
-any reply. The example failed!</span>"</small> and the server log
-contains ClassNotFoundExceptions</span></big><br>
-<br>
-If all you get after running the example is<br>
-<br>
-<small><span style="font-family: courier new,courier,monospace;">send:</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] Queue /queue/testQueue exists</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] The Hello! message was successfully sent to the </span></small><small><span
- style="font-family: courier new,courier,monospace;">testQueue </span></small><small><span
- style="font-family: courier new,courier,monospace;">queue</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] java.lang.Exception: Have not received any reply. The example
-failed!</span><br style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] at
-org.jboss.example.jms.mdb.Sender.example(Sender.java:102)</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] at
-org.jboss.example.jms.common.ExampleSupport.run(ExampleSupport.java:58)</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] at
-org.jboss.example.jms.mdb.Sender.main(Sender.java:131)</span><br
- style="font-family: courier new,courier,monospace;">
<br style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] #####################</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] ### FAILURE! ###</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] #####################</span></small><br
- style="font-family: courier new,courier,monospace;">
-<br style="font-family: courier new,courier,monospace;">
-check the server log. The presence of <br>
-<small><br style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">2006-04-11
-17:14:58,370 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler]
-Initialization failed DLQHandler</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">javax.naming.CommunicationException
-[<span style="font-weight: bold;">Root exception is
-java.lang.ClassNotFoundException: No ClassLoaders found for:
-org.jboss.jms.client.JBossConnectionFactory</span> (no security manager</span><span
- style="font-family: courier new,courier,monospace;">: RMI class loader
-disabled)]</span><br style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:713)</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-at javax.naming.InitialContext.lookup(InitialContext.java:347)</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-at
-org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:151)</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-at
-org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:245)</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-at
-org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:173)</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-...<br>
-<span style="font-family: times new roman,times,serif;"><br>
-<big>means that your Naming service was configured with a CallByValue
-semantics. There are two solutions</big></span></span></small><small><span
- style="font-family: courier new,courier,monospace;"><span
- style="font-family: times new roman,times,serif;"><big> for this
-situation</big></span></span></small><small><span
- style="font-family: courier new,courier,monospace;"><span
- style="font-family: times new roman,times,serif;"><big>:<br>
-</big></span></span></small><br>
-1) Enable JNDI call by reference semantics.<br>
-<br>
-<div style="margin-left: 40px;">To do that, modify the Naming (JNDI)
-service configuration and set its "CallByValue" attribute to "false".<br>
-<br>
-The Naming configuration file is <small><span
- style="font-family: courier new,courier,monospace;">$JBOSS_HOME/server/default/deploy/naming-service.xml</span></small>
-for an installer-generated JBoss configuration and <small><span
- style="font-family: courier new,courier,monospace;">$JBOSS_HOME/server/conf/jboss-service.xml
-</span></small>(the JNDI section, search for "jboss:service=Naming")
-for a raw installation.<br>
-</div>
-<br>
-2) In case you don't want to change JNDI CallByValue semantics, deploy
-the MDB in the same class loading domain as the Messaging server.<br>
-<br style="font-family: courier new,courier,monospace;">
<hr
style="width: 100%; height: 2px; font-family: courier new,courier,monospace;"><br>
<br>
Modified: trunk/docs/examples/http/README.html
===================================================================
--- trunk/docs/examples/http/README.html 2007-06-01 12:45:00 UTC (rev 2750)
+++ trunk/docs/examples/http/README.html 2007-06-01 12:56:11 UTC (rev 2751)
@@ -28,14 +28,6 @@
example will automatically deploy its own queue, unless a queue with
the same name is already deployed.
</p>
-<h3 style="margin-left: 40px;">Warning</h3>
-<div style="margin-left: 40px;">A service configuration bug that exists
-in all JBoss versions prior to 4.0.4.RC1 prevents this example from
-working correctly. You shouldn't attempt to run this example with JBoss
-4.0.3.SP1 or lower, unless the patch corresponding to the JIRA issue
-http://jira.jboss.org/jira/browse/JBAS-1709 was applied to your
-installation. The bug has been fixed since JBoss 4.0.4.RC1.<br>
-<span style="font-style: italic;"></span></div>
<br>
This example also needs to have access to <span
style="font-family: monospace;">jboss-messaging-client.jar</span>
@@ -148,75 +140,6 @@
<div style="margin-left: 40px;"><br>
</div>
<br>
-<h2>Configuration details</h2>
-<br>
-The example client looks up a specially-configured connection factory (<span
- style="font-family: monospace;">"/HttpConnectionFactory"</span>)
-that is deployed by the example run script. The HTTP
-ConnectionFactory relies on a HTTP Remoting Connector to provide
-the connection. The definition of the required services is
-specified in the <span style="font-family: monospace;">etc/messaging-http-service.xml
-</span>deployment descriptor. The deployment descriptor, as used by the
-example, is listed below.<br>
-<br>
-<br>
-<div style="margin-left: 40px;"><br>
-</div>
-<table
- style="width: 90%; text-align: left; font-family: monospace; background-color: rgb(204, 204, 204); margin-left: 40px;"
- border="1" cellpadding="2" cellspacing="2">
- <tbody>
- <tr>
- <td style="vertical-align: top;">
-<pre><?xml version="1.0" encoding="UTF-8"?>
-
-<!--
- HTTP Transport Example.
-
- $Id$
- -->
-
-<server>
-
- <mbean code="org.jboss.remoting.transport.Connector"
- name="jboss.messaging:service=Connector,transport=http"
- display-name="HTTP transport Connector">
- <attribute name="Configuration">
- <config>
- <invoker transport="http">
- <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
- <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
- <attribute name="dataType" isParam="true">jms</attribute>
- <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
- <attribute name="serverBindPort">4458</attribute>
- <attribute name="leasePeriod">10000</attribute>
- <attribute name="callbackStore">org.jboss.remoting.callback.CallbackStore</attribute>
- <attribute name="callbackPollPeriod" isParam="true">100</attribute>
- </invoker>
- <handlers>
- <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
- </handlers>
- </config>
- </attribute>
- </mbean>
-
- <mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
- name="jboss.messaging.destination:service=HttpConnectionFactory"
- xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
- <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
- <depends optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=http</depends>
- <attribute name="JNDIBindings">
- <bindings>
- <binding>/HttpConnectionFactory</binding>
- </bindings>
- </attribute>
- </mbean>
-
-</server></pre>
- </td>
- </tr>
- </tbody>
-</table>
<h2>Troubleshooting</h2>
<h3>1. I get <span style="font-family: monospace;">"javax.jms.JMSSecurityException:
User null is NOT authenticated" <br>
Modified: trunk/docs/examples/mdb/README.html
===================================================================
--- trunk/docs/examples/mdb/README.html 2007-06-01 12:45:00 UTC (rev 2750)
+++ trunk/docs/examples/mdb/README.html 2007-06-01 12:56:11 UTC (rev 2751)
@@ -35,19 +35,6 @@
<span style="font-family: monospace;">build.xml</span>
accordingly. <br>
<br>
-<span style="font-style: italic;">The example was designed to deploy
-its server-side artifacts </span><span
- style="font-family: monospace; font-style: italic;"></span><span
- style="font-style: italic;">under a JBoss' </span><span
- style="font-family: monospace; font-style: italic;">messaging</span><span
- style="font-style: italic;">
-configuration. If you intend to use the script with a JBoss
-configuration that is named differently, please modify the
-example's</span><span
- style="font-family: monospace; font-style: italic;"> build.xml</span><span
- style="font-style: italic;">
-accordingly.</span><br>
-<br>
<h2>Running the example</h2>
1. Set up the JBOSS_HOME environment variable to point to the JBoss
instance you deployed JBoss Messaging into. For example, if you
@@ -144,102 +131,8 @@
security domain. Follow the instructions from the "Installation"
paragraph of the release documentation. <br>
<br>
-<big><span style="font-weight: bold;">2. The example fails with <small>"<span
- style="font-family: courier new,courier,monospace;">Have not received
-any reply. The example failed!</span>"</small> and the server log
-contains ClassNotFoundExceptions</span></big><br>
-<br>
-If all you get after running the example is<br>
-<br>
-<small><span style="font-family: courier new,courier,monospace;">send:</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] Queue /queue/SmokeTestQueue exists</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] The Hello! message was successfully sent to the SmokeTestQueue
-queue</span><br style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] java.lang.Exception: Have not received any reply. The example
-failed!</span><br style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] at
-org.jboss.example.jms.mdb.Sender.example(Sender.java:102)</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] at
-org.jboss.example.jms.common.ExampleSupport.run(ExampleSupport.java:58)</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] at
-org.jboss.example.jms.mdb.Sender.main(Sender.java:131)</span><br
- style="font-family: courier new,courier,monospace;">
+
<br style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] #####################</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] ### FAILURE! ###</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-[java] #####################</span></small><br
- style="font-family: courier new,courier,monospace;">
-<br style="font-family: courier new,courier,monospace;">
-check the server log. The presence of <br>
-<small><br style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">2006-04-11
-17:14:58,370 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler]
-Initialization failed DLQHandler</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">javax.naming.CommunicationException
-[<span style="font-weight: bold;">Root exception is
-java.lang.ClassNotFoundException: No ClassLoaders found for:
-org.jboss.jms.client.JBossConnectionFactory</span> (no security manager</span><span
- style="font-family: courier new,courier,monospace;">: RMI class loader
-disabled)]</span><br style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:713)</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-at javax.naming.InitialContext.lookup(InitialContext.java:347)</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-at
-org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:151)</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-at
-org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:245)</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-at
-org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:173)</span><br
- style="font-family: courier new,courier,monospace;">
-<span style="font-family: courier new,courier,monospace;">
-...<br>
-<span style="font-family: times new roman,times,serif;"><br>
-<big>means that your Naming service was configured with a CallByValue
-semantics. There are two solutions for this situation:<br>
-</big></span></span></small><br>
-1) Enable JNDI call by reference semantics.<br>
-<br>
-<div style="margin-left: 40px;">To do that, modify the Naming (JNDI)
-service configuration and set its "CallByValue" attribute to "false".<br>
-<br>
-The Naming configuration file is <small><span
- style="font-family: courier new,courier,monospace;">$JBOSS_HOME/server/default/deploy/naming-service.xml</span></small>
-for an installer-generated JBoss configuration and <small><span
- style="font-family: courier new,courier,monospace;">$JBOSS_HOME/server/conf/jboss-service.xml
-</span></small>(the JNDI section, search for "jboss:service=Naming")
-for a raw installation.<br>
-</div>
-<br>
-2) In case you don't want to change JNDI CallByValue semantics, deploy
-the MDB in the same class loading domain as the Messaging server.<br>
-<br style="font-family: courier new,courier,monospace;">
<hr
style="width: 100%; height: 2px; font-family: courier new,courier,monospace;"><br>
<br>
Modified: trunk/docs/examples/mdb-failure/README.html
===================================================================
--- trunk/docs/examples/mdb-failure/README.html 2007-06-01 12:45:00 UTC (rev 2750)
+++ trunk/docs/examples/mdb-failure/README.html 2007-06-01 12:56:11 UTC (rev 2751)
@@ -46,19 +46,6 @@
<span style="font-family: monospace;">build.xml</span>
accordingly. <br>
<br>
-<span style="font-style: italic;">The example was designed to deploy
-its server-side artifacts </span><span
- style="font-family: monospace; font-style: italic;"></span><span
- style="font-style: italic;">under a JBoss' </span><span
- style="font-family: monospace; font-style: italic;">messaging</span><span
- style="font-style: italic;">
-configuration. If you intend to use the script with a JBoss
-configuration that is named differently, please modify the
-example's</span><span
- style="font-family: monospace; font-style: italic;"> build.xml</span><span
- style="font-style: italic;">
-accordingly.</span><span style="font-style: italic;"></span><br>
-<br>
<h2>Running the example</h2>
1. Set up the JBOSS_HOME environment variable to point to the JBoss
instance you deployed JBoss Messaging into. For example, if you
Modified: trunk/docs/examples/queue-failover/README.html
===================================================================
--- trunk/docs/examples/queue-failover/README.html 2007-06-01 12:45:00 UTC (rev 2750)
+++ trunk/docs/examples/queue-failover/README.html 2007-06-01 12:56:11 UTC (rev 2751)
@@ -3,7 +3,7 @@
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="content-type">
- <title>JBoss Messaging Example - JMS Topic</title>
+ <title>JBoss Messaging Example - Queue failover</title>
</head>
<body>
<br>
@@ -21,17 +21,8 @@
<br>
This example relies on having access to a running JBoss Messaging
cluster with at least two nodes. The JBoss Messaging cluster must be
-installed and started according to
-the
-"Installation" paragraph from the clustering documentation, bundled
-with the release (<a href="../../docs/clustering/html/index.html">HTML</a>,
-<a href="../../docs/clustering/html_single/index.html">HTML-single</a>
-and <a href="../../docs/clustering/pdf/ClusteringGuide.pdf">PDF</a>).
-The
-clustering documentation is also available on-line at <a
- href="http://labs.jboss.com/portal/jbossmessaging/docs/index.html">http://labs.jboss.com/portal/jbossmessaging/docs/index.html</a>.
+installed and started according to the userguide.
<br>
-<br>
This example also relies on having access to the <span
style="font-family: monospace;">jboss-messaging-client.jar</span>
archive included with the release bundle. If you run this example
Modified: trunk/docs/examples/secure-socket/README.html
===================================================================
--- trunk/docs/examples/secure-socket/README.html 2007-06-01 12:45:00 UTC (rev 2750)
+++ trunk/docs/examples/secure-socket/README.html 2007-06-01 12:56:11 UTC (rev 2751)
@@ -3,7 +3,7 @@
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="content-type">
- <title>JBoss Messaging Example - JMS Queue</title>
+ <title>JBoss Messaging Example - Secure Socket example</title>
</head>
<body>
<br>
@@ -27,13 +27,6 @@
"Installation" paragraph from the release documentation. However, the
example will automatically deploy its own queue, unless a queue with
the same name is already deployed. <br>
-<h3 style="margin-left: 40px;">Warning</h3>
-<div style="margin-left: 40px;">A service configuration bug that exists
-in all JBoss versions prior to 4.0.4.RC1 prevents this example from
-working correctly. You shouldn't attempt to run this example with JBoss
-4.0.3.SP1 or lower, unless the patch corresponding to the JIRA issue
-http://jira.jboss.org/jira/browse/JBAS-1709 was applied to your
-installation. The bug has been fixed since JBoss 4.0.4.RC1.<br>
<span style="font-style: italic;"></span></div>
<br>
This example also needs to have access to <span
@@ -48,9 +41,9 @@
<h2>Running the example</h2>
1. Set up the JBOSS_HOME environment variable to point to the JBoss
instance you deployed JBoss Messaging into. For example, if you
-deployed JBoss Messaging in <span style="font-family: monospace;">C:\jboss-4.0.4.GA\server\messaging\deploy,</span>
+deployed JBoss Messaging in <span style="font-family: monospace;">C:\jboss-4.2.0.GA\server\messaging\deploy,</span>
then your JBOSS_HOME value should be <span
- style="font-family: monospace;">C:\jboss-4.0.4.GA</span><br>
+ style="font-family: monospace;">C:\jboss-4.2.0.GA</span><br>
<br>
2. Go to the example's home directory<br>
<br>
@@ -129,9 +122,9 @@
<br>
deploy:<br>
[copy] Copying 1 file to
-C:\jboss-4.0.4.GA\server\messaging\deploy\jboss-messaging.sar<br>
+C:\jboss-4.2.0.GA\server\messaging\deploy\jboss-messaging.sar<br>
[copy] Copying 1 file to
-C:\jboss-4.0.4.GA\server\messaging\deploy<br>
+C:\jboss-4.2.0.GA\server\messaging\deploy<br>
<br>
sleep:<br>
[echo] Sleeping for 10 seconds ...<br>
@@ -142,7 +135,7 @@
the testQueue queue<br>
[java] Received message: Hello!<br>
[java] The example connected to JBoss
-Messaging version 1.0.1.GA (1.0)<br>
+Messaging version 1.3.0.GA (1.0)<br>
<br>
[java] #####################<br>
[java] ###
@@ -168,220 +161,9 @@
ConnectionFactory relies on a "secured" Remoting Connector to provide
the SSL connection. The definition of the required services is
specified in the <span style="font-family: monospace;">etc/messaging-secure-socket-service.xml
-</span>deployment descriptor. The deployment descriptor, as used by the
-example, is listed below. Note that all services (the Connector, the
-secure ConnectionFactory, the SSLServerSocketFactoryService and the
-SSLSocketBuilder) are deployed in the same class loading domain as the
-messaging server:<br>
-<br>
-<br>
-<div style="margin-left: 40px;"><br>
-</div>
-<table
- style="width: 90%; text-align: left; font-family: monospace; background-color: rgb(204, 204, 204); margin-left: 40px;"
- border="1" cellpadding="2" cellspacing="2">
- <tbody>
- <tr>
- <td style="vertical-align: top;"><br>
-<?xml version="1.0" encoding="UTF-8"?><br>
+</span>deployment descriptor. <br>
+
<br>
-<!--<br>
- Secure Socket Transport Example: the
-deployment descriptor for the secure socket factory<br>
- service, secure connector and secure
-connection factory.<br>
- <br>
- $Id: remoting-service.xml,v 1.2 2006/05/08
-21:35:35 ovidiu Exp $<br>
- --><br>
- <br>
-<server><br>
- <br>
-
-<loader-repository>jboss.messaging:loader=ScopedLoaderRepository<br>
-
-<loader-repository-config>java2ParentDelegation=false</loader-repository-config><br>
- </loader-repository><br>
- <br>
- <mbean code="org.jboss.remoting.transport.Connector"<br>
-
-name="jboss.messaging:service=Connector,transport=SSLSocket"<br>
-
-display-name="SSL Socket Transport Connector"><br>
- <attribute name="Configuration"><br>
- <config><br>
-
-<invoker transport="sslsocket"><br>
-
-<attribute name="marshaller"<br>
-
-
-isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute><br>
-
-<attribute name="unmarshaller"<br>
-
-isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute><br>
-
-<attribute name="serializationtype"
-isParam="true">jboss</attribute><br>
-
-<attribute name="dataType" isParam="true">jms</attribute><br>
-
-<attribute name="socket.check_connection"
-isParam="true">false</attribute><br>
-
-<attribute name="timeout">0</attribute><br>
-
-<attribute
-name="serverBindAddress">${jboss.bind.address}</attribute><br>
-
-<attribute name="serverBindPort">5457</attribute><br>
-
-<attribute name="leasePeriod">20000</attribute><br>
-
-<attribute name="serverSocketFactory"><br>
-
-jboss.messaging:service=ServerSocketFactory,type=SSL<br>
-
-</attribute><br>
-
-</invoker><br>
-
-<handlers><br>
-
-<handler subsystem="JMS"><br>
-
-org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler><br>
-
-</handlers><br>
- </config><br>
- </attribute><br>
-
-<depends>jboss.messaging:service=ServerSocketFactory,type=SSL</depends><br>
- </mbean><br>
- <br>
- <mbean
-code="org.jboss.jms.server.connectionfactory.ConnectionFactory"<br>
-
-name="jboss.messaging.destination:service=SecureConnectionFactory"<br>
-
-xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml"><br>
- <depends
-optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends><br>
- <depends
-optional-attribute-name="Connector"><br>
-
-jboss.messaging:service=Connector,transport=SSLSocket<br>
- </depends><br>
- <attribute name="JNDIBindings"><br>
- <bindings><br>
-
-<binding>/SecureConnectionFactory</binding><br>
- </bindings><br>
- </attribute><br>
- </mbean><br>
- <br>
- <!-- This section is for custom (SSL) server socket
-factory --><br>
- <br>
- <!--<br>
- The server socket factory
-mbean to be used as attribute to socket invoker (see<br>
- serverSocketFactory
-attribute above for where it is used). This service provides the exact<br>
- same API as the
-ServerSocketFactory, so can be set as an attribute of that type on any<br>
- MBean requiring an
-ServerSocketFactory.<br>
- --><br>
- <mbean
-code="org.jboss.remoting.security.SSLServerSocketFactoryService"<br>
-
-name="jboss.messaging:service=ServerSocketFactory,type=SSL"<br>
-
-display-name="SSL Server Socket Factory"><br>
- <depends
-optional-attribute-name="SSLSocketBuilder"<br>
-
-proxy-type="attribute">jboss.messaging:service=SocketBuilder,type=SSL</depends><br>
- </mbean><br>
- <br>
- <!--<br>
- This service is used to build the
-SSL Server socket factory. This will be where all the<br>
- store/trust information will be
-set. If do not need to make any custom configurations,<br>
- no extra attributes need to be set
-for the SSLSocketBuilder and just need to set the<br>
- javax.net.ssl.keyStore and
-javax.net.ssl.keyStorePassword system properties.<br>
- <br>
- This can be done by just adding
-something like the following to the run script for JBoss<br>
- (this one is for run.bat):<br>
- set
-JAVA_OPTS=-Djavax.net.ssl.keyStore=.keystore <br>
-
--Djavax.net.ssl.keyStorePassword=opensource %JAVA_OPTS%<br>
- <br>
- Otherwise, if want to customize
-the attributes for SSLSocketBuilder, will need to uncomment<br>
- them below.<br>
- --><br>
- <mbean
-code="org.jboss.remoting.security.SSLSocketBuilder"<br>
-
-name="jboss.messaging:service=SocketBuilder,type=SSL"<br>
-
-display-name="SSL Server Socket Factory Builder"><br>
- <!--<br>
- IMPORTANT
-- If making ANY customizations, this MUST be set to false.<br>
- Otherwise,
-will used default settings and the following attributes will be ignored.<br>
- --><br>
- <attribute
-name="UseSSLServerSocketFactory">false</attribute><br>
- <!-- This is the url string to the
-key store to use --><br>
- <attribute
-name="KeyStoreURL">messaging.keystore</attribute><br>
- <!-- The password for the key store
---><br>
- <attribute
-name="KeyStorePassword">secureexample</attribute><br>
- <!-- The password for the keys (will
-use KeystorePassword if this is not set explicitly. --><br>
- <attribute
-name="KeyPassword">secureexample</attribute><br>
- <!-- The protocol for the SSLContext.
-Default is TLS. --><br>
- <attribute
-name="SecureSocketProtocol">TLS</attribute><br>
- <!-- The algorithm for the key
-manager factory. Default is SunX509. --><br>
- <attribute
-name="KeyManagementAlgorithm">SunX509</attribute><br>
- <!--<br>
- The type
-to be used for the key store.<br>
- Defaults
-to JKS. Some acceptable values are JKS (Java Keystore - Sun's keystore
-format),<br>
- JCEKS
-(Java Cryptography Extension keystore - More secure version of JKS), and<br>
- PKCS12
-(Public-Key Cryptography Standards #12 keystore - RSA's Personal
-Information<br>
- Exchange
-Syntax Standard). These are not case sensitive.<br>
- --><br>
- <attribute
-name="KeyStoreType">JKS</attribute><br>
- </mbean><br>
- <br>
-</server><br>
- <br>
</td>
</tr>
</tbody>
Modified: trunk/docs/examples/stateless/README.html
===================================================================
--- trunk/docs/examples/stateless/README.html 2007-06-01 12:45:00 UTC (rev 2750)
+++ trunk/docs/examples/stateless/README.html 2007-06-01 12:56:11 UTC (rev 2751)
@@ -3,7 +3,7 @@
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="content-type">
- <title>JBoss Messaging Example - Managed Environment</title>
+ <title>JBoss Messaging Example - Stateless Session Bean</title>
</head>
<body>
<br>
@@ -36,28 +36,13 @@
<span style="font-family: monospace;">build.xml</span>
accordingly. <br>
<br>
-<span style="font-style: italic;">The example was designed to deploy
-its server-side artifacts </span><span
- style="font-family: monospace; font-style: italic;"></span><span
- style="font-style: italic;">under a JBoss' </span><span
- style="font-family: monospace; font-style: italic;">messaging</span><span
- style="font-style: italic;">
-configuration. If you intend to use the script with a JBoss
-configuration that is named differently, please modify the
-example's</span><span
- style="font-family: monospace; font-style: italic;"> build.xml</span><span
- style="font-style: italic;">
-accordingly.</span><br>
-<span style="font-style: italic;"></span><br>
-<span style="font-style: italic;"></span><br>
-<br>
<h2>Running the example</h2>
1. Set up the JBOSS_HOME environment variable to point to the JBoss
instance you deployed JBoss Messaging into. For example, if you
-deployed JBoss Messaging in <span style="font-family: monospace;">C:\jboss-4.0.3SP1\server\default\deploy,</span>
+deployed JBoss Messaging in <span style="font-family: monospace;">C:\jboss-4.2.0.GA\server\default\deploy,</span>
then your JBOSS_HOME value should be <span
style="font-family: monospace;">C:\</span><span
- style="font-family: monospace;">jboss-4.0.3SP1.</span><br>
+ style="font-family: monospace;">jboss-4.2.0.GA.</span><br>
<span style="font-family: monospace;"></span><br>
2. Go to the example's home directory<br>
<br>
@@ -118,7 +103,7 @@
<br>
deploy:<br>
[copy] Copying 1 file to
-C:\work\src\jboss-4.0.3SP1-src\build\output\jboss-4.0.3SP1\server\messaging\deploy<br>
+C:\work\src\jboss-4.2.0.GA\build\output\jboss-4.0.3SP1\server\messaging\deploy<br>
<br>
sleep:<br>
[echo] Sleeping for 5 seconds ...<br>
@@ -138,7 +123,7 @@
<br>
undeploy:<br>
[delete] Deleting:
-C:\work\src\jboss-4.0.3SP1-src\build\output\jboss-4.0.3SP1\server\messaging\deploy\stateless-example.jar<br>
+C:\work\src\jboss-4.2.0.GA\build\output\jboss-4.0.3SP1\server\messaging\deploy\stateless-example.jar<br>
<br>
BUILD SUCCESSFUL<br>
Total time: 9 seconds<br>
Modified: trunk/docs/examples/stateless-clustered/README.html
===================================================================
--- trunk/docs/examples/stateless-clustered/README.html 2007-06-01 12:45:00 UTC (rev 2750)
+++ trunk/docs/examples/stateless-clustered/README.html 2007-06-01 12:56:11 UTC (rev 2751)
@@ -3,7 +3,7 @@
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="content-type">
- <title>JBoss Messaging Example - Managed Environment</title>
+ <title>JBoss Messaging Example - Stateless Clustered Session Bean</title>
</head>
<body>
@@ -15,12 +15,9 @@
<p>
This example deploys in a cluster a stateless session bean that can then
send and receive messages from a queue. This is a very simple example that
-demonstrates using JBoss Messaging in a managed clustered environment.
+demonstrates using JBoss Messaging in a clustered environment.
The client uses HA-JNDI to look up the session bean. It then invokes the
-session bean to send a message to a test queue and afterwards pulls the
-message from the queue from a different connection using the JMS API
-directly. The example is considered successful if the message is received
-correctly.
+session bean to send a message to a test queue and afterwards consumes the same message.
</p>
<p>
This example relies on having access to a running JBoss Messaging cluster.
@@ -36,12 +33,6 @@
configured to find the client jar. Otherwise, you must modify example's
<tt>build.xml</tt> accordingly.
</p>
-<p><em>
-The example was designed to deploy its server-side artifacts under a JBoss'
-<tt>messaging-node0</tt> configuration, into the <tt>farm</tt> directory.
-If you intend to use the script with a JBoss configuration that is named
-differently, please modify the example's <tt>build.xml</tt>.
-</em></p>
<h2>Running the example</h2>
<p>
Modified: trunk/docs/examples/topic/README.html
===================================================================
--- trunk/docs/examples/topic/README.html 2007-06-01 12:45:00 UTC (rev 2750)
+++ trunk/docs/examples/topic/README.html 2007-06-01 12:56:11 UTC (rev 2751)
@@ -36,10 +36,10 @@
<h2>Running the example</h2>
1. Set up the JBOSS_HOME environment variable to point to the JBoss
instance you deployed JBoss Messaging into. For example, if you
-deployed JBoss Messaging in <span style="font-family: monospace;">C:\jboss-4.0.3SP1\server\default\deploy,</span>
+deployed JBoss Messaging in <span style="font-family: monospace;">C:\jboss-4.2.0.GA\server\default\deploy,</span>
then your JBOSS_HOME value should be <span
style="font-family: monospace;">C:\</span><span
- style="font-family: monospace;">jboss-4.0.3SP1.</span><br>
+ style="font-family: monospace;">jboss-4.2.0.GA.</span><br>
<span style="font-family: monospace;"></span><br>
2. Go to the example's home directory<br>
<br>
@@ -100,7 +100,7 @@
on the topic<br>
[java] Received message: Hello!<br>
[java] The example connected to JBoss
-Messaging version 1.0.1.GA (1.0)<br>
+Messaging version 1.2.0.GA (1.2)<br>
<br>
[java] #####################<br>
[java] ###
Modified: trunk/docs/examples/web-service/README.html
===================================================================
--- trunk/docs/examples/web-service/README.html 2007-06-01 12:45:00 UTC (rev 2750)
+++ trunk/docs/examples/web-service/README.html 2007-06-01 12:56:11 UTC (rev 2751)
@@ -3,7 +3,7 @@
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="content-type">
- <title>JBoss Messaging Example - WebSerivce Environment</title>
+ <title>JBoss Messaging Example - WebService Environment</title>
</head>
<body>
<br>
@@ -35,14 +35,6 @@
This example will also generate client classes using wsdltools from
JBoss Web Services.<br>
<br>
-<span style="font-style: italic;">The example was designed to deploy
-its server-side artifacts under a JBoss' messaging
-configuration. If you intend to use the script with a JBoss
-configuration that is named differently, please modify the
-example's build.xml accordingly.<br>
-<span style="font-style: italic;"></span><br>
-<span style="font-style: italic;"></span><br>
-<br>
<h2>Running the example</h2>
1. Set up the JBOSS_HOME environment variable to point to the JBoss
instance you deployed JBoss Messaging into. For example, if you
@@ -75,7 +67,7 @@
<td style="vertical-align: top;">
<div style="margin-left: 40px;"><br>
</div>
-example at example:/workspace/jboss-messaging-1.2.0.SP2/examples/web-services$
+example at example:/workspace/jboss-messaging-1.3.0.GA/examples/web-services$
ant<br>
Buildfile: build.xml<br>
<br>
@@ -102,7 +94,7 @@
<br>
war:<br>
[jar] Building jar:
-/workspace/jboss-messaging-1.2.0.SP2/examples/web-services/output/lib/jms-web-service.war<br>
+/workspace/jboss-messaging-1.3.0.GA/examples/web-services/output/lib/jms-web-service.war<br>
<br>
deploy:<br>
[copy] Copying 1 file to
@@ -115,7 +107,7 @@
[get] Getting:
http://127.0.0.1:8080/jms-web-service/JMSWebServiceExample?wsdl<br>
[get] To:
-/workspace/jboss-messaging-1.2.0.SP2/examples/web-services/output/service.wsdl<br>
+/workspace/jboss-messaging-1.3.0.GA/examples/web-services/output/service.wsdl<br>
[wstools] log4j:WARN No appenders could be found for logger
(org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory).<br>
[wstools] log4j:WARN Please initialize the log4j system properly.<br>
More information about the jboss-cvs-commits
mailing list