mx4j/src/docs/english introduction.xml,1.9,1.10 jsr160-explained.xml,1.11,1.12
Simone Bordet <[email protected]> Sun, 31 Oct 2004 11:38:12 +0000
| Newsgroups | gmane.comp.java.mx4j.cvs |
|---|---|
| Message-ID | <[email protected]> |
Update of /cvsroot/mx4j/mx4j/src/docs/english
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv19998/src/docs/english
Modified Files:
introduction.xml jsr160-explained.xml
Log Message:
Updated the documentation about Hessian and Burlap connectors
Index: jsr160-explained.xml
===================================================================
RCS file: /cvsroot/mx4j/mx4j/src/docs/english/jsr160-explained.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -C2 -d -r1.11 -r1.12
*** jsr160-explained.xml 20 Jul 2004 13:08:41 -0000 1.11
--- jsr160-explained.xml 31 Oct 2004 11:38:10 -0000 1.12
***************
*** 44,51 ****
<emphasis>jmxmp</emphasis> provider defined by the JSR 160 specification.
<sbr/>
! MX4J provides other two providers, not specified by the JSR 160 specification. This means that they will work
! only if MX4J runs at both client and server side. These two providers are the
! <emphasis>soap</emphasis> and
! <emphasis>local</emphasis> providers.
</para>
<para>
--- 44,53 ----
<emphasis>jmxmp</emphasis> provider defined by the JSR 160 specification.
<sbr/>
! MX4J provides other four providers, not specified by the JSR 160 specification. This means that they will work
! only if MX4J runs at both client and server side. These four providers are the
! <emphasis>soap</emphasis>,
! <emphasis>local</emphasis>,
! <emphasis>hessian</emphasis> and
! <emphasis>burlap</emphasis> providers.
</para>
<para>
***************
*** 56,59 ****
--- 58,63 ----
<listitem>service:jmx:soap://host</listitem>
<listitem>service:jmx:local://host</listitem>
+ <listitem>service:jmx:hessian://host</listitem>
+ <listitem>service:jmx:burlap://host</listitem>
</itemizedlist>
</para>
***************
*** 1063,1067 ****
<title>MX4J's JSR 160 JMXConnectors and JMXConnectorServers</title>
<section>
! <title>Overview of SOAPConnector and SOAPConnectorServer</title>
<para>
Thanks to the fact that JSR 160 allows complete pluggability of the communication protocol between
--- 1067,1071 ----
<title>MX4J's JSR 160 JMXConnectors and JMXConnectorServers</title>
<section>
! <title>The SOAP JSR 160 connector</title>
<para>
Thanks to the fact that JSR 160 allows complete pluggability of the communication protocol between
***************
*** 1089,1101 ****
<classname>mx4j.examples.tools.remote.soap.Client</classname> to follow the instructions below.
</para>
- </section>
- <section>
- <title>Using the JSR 160 JMXConnector and JMXConnectorServer over SOAP</title>
<para>
Starting successfully a SOAPConnectorServer requires Axis 1.1 and a servlet 2.3 compliant web container.
<sbr/>
Starting a standalone SOAPConnectorServer will perform several operations:
<itemizedlist>
! <listitem>Start a Jetty 4.2.x server on the port specified by the JMXServiceURL</listitem>
<listitem>Deploy to Jetty the Axis servlet, and mapping it to the path specified by the JMXServiceURL</listitem>
<listitem>Deploy to Axis the webservice that represent the remote MBeanServer</listitem>
--- 1093,1104 ----
<classname>mx4j.examples.tools.remote.soap.Client</classname> to follow the instructions below.
</para>
<para>
Starting successfully a SOAPConnectorServer requires Axis 1.1 and a servlet 2.3 compliant web container.
+ In this example the web container will be the <ulink url="http://jetty.mortbay.com">Jetty</ulink> web
+ container.
<sbr/>
Starting a standalone SOAPConnectorServer will perform several operations:
<itemizedlist>
! <listitem>Start a Jetty server on the port specified by the JMXServiceURL</listitem>
<listitem>Deploy to Jetty the Axis servlet, and mapping it to the path specified by the JMXServiceURL</listitem>
<listitem>Deploy to Axis the webservice that represent the remote MBeanServer</listitem>
***************
*** 1186,1189 ****
--- 1189,1260 ----
</para>
</section>
+ <section>
+ <title>The HESSIAN and BURLAP JSR 160 connectors</title>
+ <para>
+ MX4J implements other two JMXConnectors and JMXConnectorServers that use open source (Apache license)
+ <ulink url="http://www.caucho.com">Caucho</ulink> protocols
+ <ulink url="http://www.caucho.com/hessian">Hessian and Burlap</ulink>.
+ <sbr/>
+ Similarly to the SOAP JMXConnector and JMXConnectorServer, Hessian's and Burlap's
+ JMXConnector and JMXConnectorServer use HTTP as transport protocol.
+ </para>
+ <para>
+ Starting successfully a [Hessian|Burlap]ConnectorServer requires the hessian/burlap library
+ (hessian-3.0.8.jar) and a servlet 2.3 compliant web container, like for example, the
+ <ulink url="http://jetty.mortbay.com">Jetty</ulink> web container.
+ <sbr/>
+ Starting a standalone [Hessian|Burlap]ConnectorServer will perform several operations:
+ <itemizedlist>
+ <listitem>Start a Jetty server on the port specified by the JMXServiceURL</listitem>
+ <listitem>Deploy to Jetty an MX4J's customized [Hessian|Burlap] servlet, and mapping it to the path specified by the JMXServiceURL</listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ Follow the advices given for the SOAPConnectorServer in choosing the JMXServiceURL on server side
+ and on client side.
+ </para>
+ <para>
+ <example>
+ <title>Starting the HessianConnectorServer</title>
+ <programlisting>
+ <![CDATA[
+ // Use null as host
+ JMXServiceURL url = new JMXServiceURL("hessian", null, 8080, "/hessian");
+
+ MBeanServer server = ...;
+
+ JMXConnectorServer cntorServer = JMXConnectorServerFactory.newJMXConnectorServer(url, null, server);
+
+ // This method call will:
+ // 1. Start Jetty on port 8080
+ // 2. Deploy to Jetty the MX4J's Hessian servlet with servlet-mapping /hessian/*
+ cntorServer.start();
+ ]]>
+ </programlisting>
+ </example>
+ </para>
+ <para>
+ <example>
+ <title>Connecting to the HessianConnectorServer</title>
+ <programlisting>
+ <![CDATA[
+ // Remember to specify the host name if not in-VM
+ JMXServiceURL url = new JMXServiceURL("hessian", null, 8080, "/hessian");
+
+ // Connect !
+ JMXConnector cntor = JMXConnectorFactory.connect(url);
+
+ // Invoke some operation
+ MBeanServerConnection connection = cntor.getMBeanServerConnection();
+ Integer count = connection.getMBeanCount();
+ ]]>
+ </programlisting>
+ </example>
+ </para>
+ <para>
+ To use the Burlap protocol instead of the Hessian protocol, just replace the protocol (and optionally
+ the path), from 'hessian' to 'burlap'.
+ </para>
+ </section>
</section>
Index: introduction.xml
===================================================================
RCS file: /cvsroot/mx4j/mx4j/src/docs/english/introduction.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -C2 -d -r1.9 -r1.10
*** introduction.xml 12 Jun 2004 21:30:52 -0000 1.9
--- introduction.xml 31 Oct 2004 11:38:10 -0000 1.10
***************
*** 12,17 ****
</ulink>,
and it's an optional package for the J2SE
! <superscript>TM</superscript> platform that will be
! included in J2SE, version 1.5.
</para>
<para>
--- 12,17 ----
</ulink>,
and it's an optional package for the J2SE
! <superscript>TM</superscript> platform that is now
! included in J2SE 5.0.
</para>
<para>
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click