JBoss Remoting SVN: r4510 - remoting2/branches/2.x/src/main/org/jboss/remoting.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2008-08-12 03:04:07 -0400 (Tue, 12 Aug 2008)
New Revision: 4510
Modified:
remoting2/branches/2.x/src/main/org/jboss/remoting/Version.java
Log:
JBREM-1025: Updated version to 2.4.0.SP1.
Modified: remoting2/branches/2.x/src/main/org/jboss/remoting/Version.java
===================================================================
--- remoting2/branches/2.x/src/main/org/jboss/remoting/Version.java 2008-08-12 07:03:21 UTC (rev 4509)
+++ remoting2/branches/2.x/src/main/org/jboss/remoting/Version.java 2008-08-12 07:04:07 UTC (rev 4510)
@@ -34,7 +34,7 @@
public static final byte VERSION_2 = 2;
public static final byte VERSION_2_2 = 22;
- public static final String VERSION = "2.4.0.GA (Pinto)";
+ public static final String VERSION = "2.4.0.SP1 (Pinto)";
private static final byte byteVersion = VERSION_2_2;
private static byte defaultByteVersion = byteVersion;
private static boolean performVersioning = true;
15 years, 9 months
JBoss Remoting SVN: r4509 - remoting2/branches/2.x.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2008-08-12 03:03:21 -0400 (Tue, 12 Aug 2008)
New Revision: 4509
Modified:
remoting2/branches/2.x/build.xml
Log:
JBREM-1024: Added versioning test for 2.4.0.GA; (2) JBREM-1025: updated version to 2.4.0.SP1.
Modified: remoting2/branches/2.x/build.xml
===================================================================
--- remoting2/branches/2.x/build.xml 2008-08-12 06:02:14 UTC (rev 4508)
+++ remoting2/branches/2.x/build.xml 2008-08-12 07:03:21 UTC (rev 4509)
@@ -224,9 +224,9 @@
<!-- Module name(s) & version -->
<property name="module.name" value="remoting"/>
<property name="module.Name" value="JBoss Remoting"/>
- <property name="module.version" value="2.4.0.GA"/>
+ <property name="module.version" value="2.4.0.SP1"/>
<!-- extension is for the file suffix to use for dtribution build -->
- <property name="module.version.extension" value="2_4_0_GA"/>
+ <property name="module.version.extension" value="2_4_0_SP1"/>
<property name="implementation.url" value="http://www.jboss.org/products/remoting"/>
<property name="root.dir" value="${basedir}"/>
@@ -1661,6 +1661,21 @@
</antcall>
<!-- ******************************************************************************** -->
+ <!-- Current <- -> 2.4.0.GA -->
+ <antcall target="tests.versioning.all_transports" inheritrefs="true">
+ <param name="jboss-junit-configuration" value="2_4_0_GA-client"/>
+ <param name="client.classpath" value="${etc.dir}/lib/remoting_2_4_0_GA/jboss-remoting.jar"/>
+ <param name="server.classpath" value="${output.lib.dir}/jboss-remoting.jar"/>
+ <param name="check_content_type" value="true"/>
+ </antcall>
+ <antcall target="tests.versioning.all_transports" inheritrefs="true">
+ <param name="jboss-junit-configuration" value="2_4_0_GA-server"/>
+ <param name="server.classpath" value="${etc.dir}/lib/remoting_2_4_0_GA/jboss-remoting.jar"/>
+ <param name="client.classpath" value="${output.lib.dir}/jboss-remoting.jar"/>
+ <param name="check_content_type" value="true"/>
+ </antcall>
+
+ <!-- ******************************************************************************** -->
<!-- Current <- -> 2.2.2.SP7 -->
<antcall target="tests.versioning.all_transports_pre_2.4" inheritrefs="true">
<param name="jboss-junit-configuration" value="2_2_2_SP7-client"/>
15 years, 9 months
JBoss Remoting SVN: r4508 - remoting2/branches/2.x/docs.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2008-08-12 02:02:14 -0400 (Tue, 12 Aug 2008)
New Revision: 4508
Modified:
remoting2/branches/2.x/docs/README.txt
Log:
JBREM-1025: Added release notes for 2.4.0.SP1 release.
Modified: remoting2/branches/2.x/docs/README.txt
===================================================================
--- remoting2/branches/2.x/docs/README.txt 2008-08-12 05:59:00 UTC (rev 4507)
+++ remoting2/branches/2.x/docs/README.txt 2008-08-12 06:02:14 UTC (rev 4508)
@@ -30,6 +30,38 @@
in Jira, please create one.
==========================================================================================================
+Release Notes - JBoss Remoting - Version 2.4.0.SP1 (Pinto)
+Bug
+
+ * [JBREM-302] - remote dynamic marshall loading not working on linux
+ * [JBREM-925] - SSLSocketBuilder config attribute names out of sync with docs
+ * [JBREM-990] - CLONE [JBREM-960] - Remoting configured with Servlet invoker can return misleading Exceptions when Servlet path is incorrect
+ * [JBREM-991] - Investigate MulticastDetector message flood
+ * [JBREM-1000] - CLONE [JBREM-962] - Remote classloading does not work with Isolated EARs
+ * [JBREM-1005] - Prevent build up of cancelled TimerTasks in bisocket transport
+ * [JBREM-1006] - SOA MTOM bug points to bug in Remoting codebase
+ * [JBREM-1019] - RemotingClassLoader needs option to delegate to user class loader before parent
+ * [JBREM-1022] - Fix misleading javadoc in InvokerLocator
+ * [JBREM-1023] - Dynamic marshalling fails with JBossSerialization
+
+Feature Request
+
+ * [JBREM-996] - CLONE [JBREM-971] - Enhance server-side connection error handling so certain (potentially revealing) socket-related exceptins are not discarded
+ * [JBREM-997] - CLONE [JBREM-970] - Enhance client-side error reporting so a misspelled truststore file name required by SSL can be easily spotted
+ * [JBREM-1012] - CLONE [JBREM-1010] - Add feature to declaratively turn on leasing for 2.4.0
+ * [JBREM-1015] - CLONE [JBREM-1014] - Support injection of socket factory class name into AbstractInvoker
+
+Release
+
+ * [JBREM-1025] - Release 2.4.0.SP1
+
+Task
+
+ * [JBREM-999] - Make sure all fixes on 2.2 branch are ported to 2.x branch.
+ * [JBREM-1017] - Improve socket timeout log message
+ * [JBREM-1024] - Assure version compatibility with earlier versions of Remoting
+
+==========================================================================================================
Release Notes - JBoss Remoting - Version 2.4.0.GA
Bug
15 years, 9 months
JBoss Remoting SVN: r4507 - remoting2/branches/2.x/docs/guide/en.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2008-08-12 01:59:00 -0400 (Tue, 12 Aug 2008)
New Revision: 4507
Modified:
remoting2/branches/2.x/docs/guide/en/master.xml
Log:
JBREM-1000, JBREM-1019: New chapter about classloading; JBREM-1025: Changed version to 2.4.0.SP1.
Modified: remoting2/branches/2.x/docs/guide/en/master.xml
===================================================================
--- remoting2/branches/2.x/docs/guide/en/master.xml 2008-08-12 05:58:03 UTC (rev 4506)
+++ remoting2/branches/2.x/docs/guide/en/master.xml 2008-08-12 05:59:00 UTC (rev 4507)
@@ -9,6 +9,7 @@
<!ENTITY chap6 SYSTEM "chap6.xml">
<!ENTITY chap7 SYSTEM "chap7.xml">
<!ENTITY chap8 SYSTEM "chap8.xml">
+<!ENTITY chap_cl SYSTEM "chap-classloaders.xml">
<!ENTITY chap9 SYSTEM "chap9.xml">
<!ENTITY chap10 SYSTEM "chap10.xml">
<!ENTITY chap11 SYSTEM "chap11.xml">
@@ -23,9 +24,9 @@
<bookinfo>
<title>JBoss Remoting Guide</title>
- <subtitle>JBoss Remoting version 2.4.0.GA</subtitle>
+ <subtitle>JBoss Remoting version 2.4.0.SP1</subtitle>
- <releaseinfo>May 28, 2008</releaseinfo>
+ <releaseinfo>August 12, 2008</releaseinfo>
<mediaobject>
<imageobject>
@@ -55,6 +56,8 @@
&chap7;
&chap8;
+
+ &chap_cl;
&chap9;
15 years, 9 months
JBoss Remoting SVN: r4506 - remoting2/branches/2.x/docs/guide/en.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2008-08-12 01:58:03 -0400 (Tue, 12 Aug 2008)
New Revision: 4506
Added:
remoting2/branches/2.x/docs/guide/en/chap-classloaders.xml
Log:
JBREM-1000, JBREM-1019: New chapter about classloading.
Added: remoting2/branches/2.x/docs/guide/en/chap-classloaders.xml
===================================================================
--- remoting2/branches/2.x/docs/guide/en/chap-classloaders.xml (rev 0)
+++ remoting2/branches/2.x/docs/guide/en/chap-classloaders.xml 2008-08-12 05:58:03 UTC (rev 4506)
@@ -0,0 +1,201 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter>
+ <title>Remote classloading facility</title>
+
+ <para>When a Remoting unmarshaller reads a serialized request or response from
+ the network, it needs to have access to the classes of the objects contained
+ in the serialized object. Frequently, these will be a simple combination of
+ Remoting and Java objects. For example, if an application returns a
+ <classname>java.lang.String</classname>, it will be wrapped in an
+ <classname>org.jboss.remoting.InvocationResponse</classname>, and both classes
+ will be known to the unmarshaller. But what if an application returns an
+ unknown implementation of a known interface? Remoting has a remote
+ classloading facility to support the latter scenario.</para>
+
+ <section id="section-client-classloading"
+ xreflabel="Classloading in client invokers">
+ <title>Classloading in client invokers</title>
+
+ <para>An instance of
+ <classname>org.jboss.remoting.marshal.serializable.SerializableUnMarshaller</classname>,
+ which is the default unmarshaller, or parent of the default unmarshaller,
+ for the socket, bisocket, and http transports (marshalling and unmarshalling
+ in the rmi transport is handled by the RMI runtime), will look for classes
+ in the following order:</para>
+
+ <orderedlist>
+
+ <listitem>
+ <para>try system classloader, which loads from locations specified in the classpath;</para>
+ </listitem>
+
+ <listitem>
+ <para>try the Remoting classloader, that is, the classloader that
+ loaded the Remoting classes (which, depending on the context, may or may not be the system classloader);</para>
+ </listitem>
+
+ <listitem>
+ <para>try to load from Remoting's remote classloading facility;</para>
+ </listitem>
+
+ <listitem>
+ <para>try the current thread's context classloader.</para>
+ </listitem>
+ </orderedlist>
+
+ <para>The current thread's context classloader can be moved to the front of
+ the list to enable the alternative behavior:</para>
+
+ <orderedlist>
+
+ <listitem>
+ <para>try the current thread's context classloader;</para>
+ </listitem>
+
+ <listitem>
+ <para>try system classloader, which loads from locations specified in the classpath;</para>
+ </listitem>
+
+ <listitem>
+ <para>try the Remoting classloader, that is, the classloader that
+ loaded the Remoting classes (which, depending on the context, may or may not be the system classloader);</para>
+ </listitem>
+
+ <listitem>
+ <para>try to load from Remoting's remote classloading facility.</para>
+ </listitem>
+ </orderedlist>
+
+ <para>This alternative behavior may be enabled either by setting the
+ <code>org.jboss.remoting.Remoting.CLASSLOADING_PARENT_FIRST_DELEGATION</code>
+ parameter (actual value "classloadingParentFirstDelegation") to "false" in
+ the <classname>InvokerLocator</classname> or in the client invoker's
+ configuration map (see <xref linkend="chapter-configuration"/> for more on
+ configuration options) or by setting the system property
+ Remoting.CLASSLOADING_PARENT_FIRST_DELEGATION_PROP (actual value
+ "org.jboss.remoting.classloadingParentFirstDelegation") to "false".</para>
+
+ <para>Note that the default behavior, in the absence of any explicit action
+ to the contrary, is for a thread's context classloader to be set to the same
+ classloader that loaded the application. However, somewhere outside of
+ Remoting, the context classloader may be set otherwise. For example, a
+ Remoting client invoker might be running inside an EJB3 container that
+ maintains a classloader associated with the EJB3's EAR file and sets the
+ thread context classloader to the EAR classloader whenever it passes control
+ into code supplied in the EAR. This situation would arise when one EJB3
+ calls another EJB3, where the invocation would ultimately be made by a
+ Remoting client invoker. <emphasis role="bold">Note</emphasis>, by the way,
+ the implication that this discussion about classloading in client invokers
+ applies not only to clients in the ordinary client server sense, but also to
+ clients running inside the server.</para>
+ </section>
+
+ <section id="section-server-classloading"
+ xreflabel="Server side support for remote classloading">
+ <title>Server side support for remote classloading</title>
+
+ <para>Remoting implements an optional remote classloading facility that
+ makes it possible for a client invoker unmarshaller to request copies of
+ classes that it encounters during the deserialization process. This facility
+ is provided by a special
+ <classname>org.jboss.remoting.transport.Connector</classname> that runs an
+ <classname>org.jboss.remoting.ServerInvocationHandler</classname> designed
+ to locate and return requested classes. This facility is enabled by
+ configuring a <classname>Connector</classname> with the parameter
+ <code>org.jboss.remoting.InvokerLocator.LOADER_PORT</code> (actual value
+ "loaderport") set to an available port number. (See <xref
+ linkend="chapter-configuration"/> for more on configuration options.) Using
+ the "loaderport" parameter will result in the creation of a second
+ <classname>Connector</classname> which responds to requests to download
+ classes.</para>
+
+ <para>Prior to Remoting release 2.4.0.SP1, the classloading search
+ implemented by the classloading
+ <classname>SerrverInvocationHandler</classname> was the following:</para>
+
+ <orderedlist>
+ <listitem>
+ <para>try system classloader, which loads from locations specified in the classpath;</para>
+ </listitem>
+
+ <listitem>
+ <para>try the Remoting classloader, that is, the classloader that
+ loaded the Remoting classes (which, depending on the context, may or
+ may not be the system classloader).</para>
+ </listitem>
+ </orderedlist>
+
+ <para>This original behavior is too restrictive in the context of the rich
+ classloading options of the JBoss Application Server. As of release
+ 2.4.0.SP1, it is possible to configure the classloading facility with a list
+ of additional classloaders. One option is to pass a list of classloaders to a
+ <classname>Connector</classname> programatically using the
+ <code>org.jboss.remoting.Remoting.Remoting.REMOTE_CLASS_LOADERS</code>
+ parameter (actual value "remoteClassLoaders") in either a configuration map
+ or an <classname>org.jboss.remoting.ServerConfiguration</classname>. For
+ example:</para>
+
+ <programlisting>
+ServerConfiguration serverConfiguration = new ServerConfiguration("socket");
+Map invokerLocatorParameters = new HashMap();
+invokerLocatorParameters.put(InvokerLocator.LOADER_PORT, "5544");
+serverConfiguration.setInvokerLocatorParameters(invokerLocatorParameters);
+Map serverParameters = new HashMap();
+ArrayList classLoaders = new ArrayList();
+classLoader1 = ...
+classLoader2 = ...
+classLoaders.add(classLoader1);
+classLoaders.add(classLoader2);
+serverParameters.put(Remoting.REMOTE_CLASS_LOADERS, classLoaders);
+serverConfiguration.setServerParameters(serverParameters);
+connector = new Connector();
+connector.setServerConfiguration(serverConfiguration);
+ </programlisting>
+
+ <para>An alternative in the presence of the JBoss microcontainer, e.g., in
+ the Application Server, would be to achieve the same result declaratively.
+ For example:</para>
+
+ <programlisting><?xml version="1.0" encoding="UTF-8"?>
+<deployment xmlns="urn:jboss:bean-deployer:2.0">
+
+ <bean name="remoting:serverConfiguration"
+ class="org.jboss.remoting.ServerConfiguration">
+ <constructor>
+ <parameter>socket</parameter>
+ </constructor>
+ <property name="invokerLocatorParameters">
+ <map keyClass="java.lang.String" valueClass="java.lang.String">
+ <entry>
+ <key>loaderport</key>
+ <value>5544</value>
+ </entry>
+ </map>
+ </property>
+ <property name="serverParameters">
+ <map keyClass="java.lang.String" valueClass="java.lang.Object">
+ <entry>
+ <key>remoteClassLoaders</key>
+ <value>
+ <list elementClass="java.lang.ClassLoader">
+ <value>ear1:classloader</value>
+ <value>ear2:classloader</value>
+ </list>
+ </value>
+ </entry>
+ </map>
+ </property>
+ <property name="invocationHandlers">
+ ...
+ </property>
+ </bean>
+
+ <bean name="remoting:connector" class="org.jboss.remoting.transport.Connector">
+ <property name="serverConfiguration">
+ <inject bean="remoting:serverConfiguration"/>
+ </property>
+ </bean>
+
+</deployment></programlisting>
+ </section>
+</chapter>
15 years, 9 months
JBoss Remoting SVN: r4505 - remoting2/branches/2.x/docs/guide/en.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2008-08-12 01:57:35 -0400 (Tue, 12 Aug 2008)
New Revision: 4505
Modified:
remoting2/branches/2.x/docs/guide/en/chap5.xml
Log:
JBREM-1000, JBREM-1019: Added chapter xreflabel for reference in classloader chapter.
Modified: remoting2/branches/2.x/docs/guide/en/chap5.xml
===================================================================
--- remoting2/branches/2.x/docs/guide/en/chap5.xml 2008-08-12 05:56:20 UTC (rev 4504)
+++ remoting2/branches/2.x/docs/guide/en/chap5.xml 2008-08-12 05:57:35 UTC (rev 4505)
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter>
+<chapter id="chapter-configuration" xreflabel="Configuration">
<title>Configuration</title>
<para>This covers the configuration for JBoss Remoting discovery, connectors,
15 years, 9 months
JBoss Remoting SVN: r4504 - remoting2/branches/2.x/docs/guide/en.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2008-08-12 01:56:20 -0400 (Tue, 12 Aug 2008)
New Revision: 4504
Modified:
remoting2/branches/2.x/docs/guide/en/chap17.xml
Log:
JBREM-1025: Added release notes for 2.4.0.SP1 release.
Modified: remoting2/branches/2.x/docs/guide/en/chap17.xml
===================================================================
--- remoting2/branches/2.x/docs/guide/en/chap17.xml 2008-08-12 05:55:58 UTC (rev 4503)
+++ remoting2/branches/2.x/docs/guide/en/chap17.xml 2008-08-12 05:56:20 UTC (rev 4504)
@@ -52,6 +52,39 @@
<section>
<title>Version 2.4</title>
+
+ <bridgehead>Release Notes - JBoss Remoting - Version 2.4.0.SP1 (Pinto)</bridgehead>
+
+ <para><emphasis role="bold">Bug</emphasis></para>
+
+ <para>* [JBREM-302] - remote dynamic marshall loading not working on linux</para>
+ <para>* [JBREM-925] - SSLSocketBuilder config attribute names out of sync with docs</para>
+ <para>* [JBREM-990] - CLONE [JBREM-960] - Remoting configured with Servlet invoker can return misleading Exceptions when Servlet path is incorrect</para>
+ <para>* [JBREM-991] - Investigate MulticastDetector message flood</para>
+ <para>* [JBREM-1000] - CLONE [JBREM-962] - Remote classloading does not work with Isolated EARs</para>
+ <para>* [JBREM-1005] - Prevent build up of cancelled TimerTasks in bisocket transport</para>
+ <para>* [JBREM-1006] - SOA MTOM bug points to bug in Remoting codebase</para>
+ <para>* [JBREM-1019] - RemotingClassLoader needs option to delegate to user class loader before parent</para>
+ <para>* [JBREM-1022] - Fix misleading javadoc in InvokerLocator</para>
+ <para>* [JBREM-1023] - Dynamic marshalling fails with JBossSerialization</para>
+
+ <para><emphasis role="bold">Feature Request</emphasis></para>
+
+ <para>* [JBREM-996] - CLONE [JBREM-971] - Enhance server-side connection error handling so certain (potentially revealing) socket-related exceptins are not discarded</para>
+ <para>* [JBREM-997] - CLONE [JBREM-970] - Enhance client-side error reporting so a misspelled truststore file name required by SSL can be easily spotted</para>
+ <para>* [JBREM-1012] - CLONE [JBREM-1010] - Add feature to declaratively turn on leasing for 2.4.0</para>
+ <para>* [JBREM-1015] - CLONE [JBREM-1014] - Support injection of socket factory class name into AbstractInvoker</para>
+
+ <para><emphasis role="bold">Release</emphasis></para>
+
+ <para>* [JBREM-1025] - Release 2.4.0.SP1</para>
+
+ <para><emphasis role="bold">Task</emphasis></para>
+
+ <para>* [JBREM-999] - Make sure all fixes on 2.2 branch are ported to 2.x branch.</para>
+ <para>* [JBREM-1017] - Improve socket timeout log message</para>
+ <para>* [JBREM-1024] - Assure version compatibility with earlier versions of Remoting</para>
+
<bridgehead>Release Notes - JBoss Remoting - Version 2.4.0.GA (Pinto)</bridgehead>
<para><emphasis role="bold">Bug</emphasis></para>
15 years, 9 months
JBoss Remoting SVN: r4503 - remoting2/branches/2.x/docs/guide/en.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2008-08-12 01:55:58 -0400 (Tue, 12 Aug 2008)
New Revision: 4503
Modified:
remoting2/branches/2.x/docs/guide/en/chap1.xml
Log:
JBREM-1025: Added information about 2.4.0.SP1 release.
Modified: remoting2/branches/2.x/docs/guide/en/chap1.xml
===================================================================
--- remoting2/branches/2.x/docs/guide/en/chap1.xml 2008-08-11 02:23:58 UTC (rev 4502)
+++ remoting2/branches/2.x/docs/guide/en/chap1.xml 2008-08-12 05:55:58 UTC (rev 4503)
@@ -177,30 +177,54 @@
<section>
<title>What's new in version 2.4?</title>
- <para>JBossRemoting 2.4.0.GA is an incremental release, with dozens of bug fixes and several new features:
- </para>
+ <section>
+ <title>Release 2.4.0.SP1</title>
+
+ <itemizedlist>
+ <listitem>
+ <para>The remote classloading facility can be configured with lists of
+ classloaders.</para>
+ </listitem>
+
+ <listitem>
+ <para>Classloading in the client can optionally start with the thread
+ context classloader.</para>
+ </listitem>
+
+ <listitem>
+ <para>Leasing can be enabled declaratively.</para>
+ </listitem>
+ </itemizedlist>
+ </section>
- <itemizedlist>
- <listitem>
- <para>servers can be bound to multiple IP addresses</para>
- </listitem>
- <listitem>
- <para>can run in the presence of a security manager</para>
- </listitem>
- <listitem>
- <para>greater configurability</para>
- </listitem>
- <listitem>
- <para>supports IPv6 addresses</para>
- </listitem>
- <listitem>
- <para>improved connection monitoring</para>
- </listitem>
- <listitem>
- <para>server gets client address in invocations</para>
- </listitem>
+ <section>
+ <title>Release 2.4.0.GA</title>
- </itemizedlist>
-
+ <para>JBossRemoting 2.4.0.GA is an incremental release, with dozens of bug
+ fixes and several new features: </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>servers can be bound to multiple IP addresses</para>
+ </listitem>
+ <listitem>
+ <para>can run in the presence of a security manager</para>
+ </listitem>
+ <listitem>
+ <para>greater configurability</para>
+ </listitem>
+ <listitem>
+ <para>supports IPv6 addresses</para>
+ </listitem>
+ <listitem>
+ <para>improved connection monitoring</para>
+ </listitem>
+ <listitem>
+ <para>server gets client address in invocations</para>
+ </listitem>
+
+ </itemizedlist>
+ </section>
+
</section>
</chapter>
\ No newline at end of file
15 years, 9 months
JBoss Remoting SVN: r4502 - remoting2/branches/2.x/src/main/org/jboss/remoting/transport.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2008-08-10 22:23:58 -0400 (Sun, 10 Aug 2008)
New Revision: 4502
Modified:
remoting2/branches/2.x/src/main/org/jboss/remoting/transport/Connector.java
Log:
JBREM-1000: Fixed remoteClassLoaders type test in init().
Modified: remoting2/branches/2.x/src/main/org/jboss/remoting/transport/Connector.java
===================================================================
--- remoting2/branches/2.x/src/main/org/jboss/remoting/transport/Connector.java 2008-08-10 23:36:32 UTC (rev 4501)
+++ remoting2/branches/2.x/src/main/org/jboss/remoting/transport/Connector.java 2008-08-11 02:23:58 UTC (rev 4502)
@@ -480,7 +480,7 @@
{
setRemoteClassLoaders((List) o);
}
- else
+ else if (o != null)
{
log.warn("value of " + Remoting.REMOTE_CLASS_LOADERS + " must be a List");
}
15 years, 9 months
JBoss Remoting SVN: r4501 - remoting2/branches/2.x.
by jboss-remoting-commits＠lists.jboss.org
Author: ron.sigal(a)jboss.com
Date: 2008-08-10 19:36:32 -0400 (Sun, 10 Aug 2008)
New Revision: 4501
Modified:
remoting2/branches/2.x/build.xml
Log:
JBREM-302, JBREM-1023: (1) tests.marshall now runs in linux; (2) tests.marshall now runs with both java and jboss serialization.
Modified: remoting2/branches/2.x/build.xml
===================================================================
--- remoting2/branches/2.x/build.xml 2008-08-10 23:29:51 UTC (rev 4500)
+++ remoting2/branches/2.x/build.xml 2008-08-10 23:36:32 UTC (rev 4501)
@@ -860,6 +860,9 @@
<param name="jboss-junit-configuration" value="java_serialization_security"/>
</antcall>
<antcall target="tests.marshall" inheritrefs="true">
+ <param name="remoting.metadata.key" value="remoting.metadata"/>
+ <param name="metadata" value="serializationtype=java"/>
+ <param name="jboss-junit-configuration" value="java_serialization"/>
</antcall>
</target>
@@ -898,6 +901,11 @@
</antcall>
<antcall target="tests.nonserializable" inheritrefs="true"/>
<antcall target="tests.functional.main.serialization.jboss" inheritrefs="true"/>
+ <antcall target="tests.marshall" inheritrefs="true">
+ <param name="remoting.metadata.key" value="remoting.metadata"/>
+ <param name="metadata" value="serializationtype=jboss"/>
+ <param name="jboss-junit-configuration" value="jboss_serialization"/>
+ </antcall>
</target>
@@ -1539,8 +1547,8 @@
<!-- End of socket serialization smoke tests -->
<!-- Tests dynamic, remote loading of marshaller/unmarshaller -->
- <target name="tests.marshall" if="os.windows">
- <echo>remote marshalling tests</echo>
+ <target name="tests.marshall">
+ <echo>remote marshalling tests: ${metadata}</echo>
<mkdir dir="${output.tests.results}"/>
<mkdir dir="${output.tests.tmp}"/>
<junit printsummary="true" fork="yes" includeantruntime="true" tempdir="${output.tests.tmp}">
@@ -1549,6 +1557,7 @@
<path refid="tests.marshall.classpath"/>
<pathelement location="${output.lib.dir}/jboss-remoting-tests.jar"/>
</classpath>
+ <jvmarg value="-D${remoting.metadata.key}=${metadata}"/>
<sysproperty key="${java.security.manager.key}" value="${java.security.manager}"/>
<sysproperty key="java.security.policy" value="${java.security.policy.marshal}"/>
<sysproperty key="java.security.debug" value="${java.security.debug}"/>
@@ -1557,6 +1566,7 @@
<sysproperty key="log4j.jar.dir" value="${basedir}/lib/apache-log4j/lib"/>
<sysproperty key="log4j.config.dir" value="${basedir}/src/etc"/>
<sysproperty key="ant.library.dir" value="${ant.library.dir}"/>
+ <sysproperty key="jboss-junit-configuration" value="${jboss-junit-configuration}"/>
<sysproperty key="jrunit.bind_addr" value="${bind.address}"/>
<sysproperty key="jrunit.mcast_addr" value="${multicast.address}"/>
<sysproperty key="jrunit.mcast_port" value="${multicast.port}"/>
@@ -1566,10 +1576,10 @@
<sysproperty key="jrunit.logdir" value="${output.tests}"/>
<!-- this is needed for the remoting.marshall.dynamic.remote.MarshallerLoadingServer -->
<jvmarg value="-Dloader.path=${output.lib.dir}/jboss-remoting-loading-tests.jar"/>
- <formatter type="xml"/>
+ <formatter classname="org.jboss.ant.taskdefs.XMLJUnitMultipleResultFormatter"
+ extension="-${jboss-junit-configuration}.xml"/>
<batchtest fork="yes" todir="${output.tests.results}"
haltonfailure="no">
- <formatter type="xml"/>
<fileset dir="${tests.compile.dir}">
<include name="**/remoting/marshall/dynamic/remote/**/*TestCase.class"/>
<exclude name="**/remoting/**/performance/**"/>
15 years, 9 months