[jboss-cvs] JBossRemoting/docs ...
Tom Elrod
tom.elrod at jboss.com
Wed Aug 2 22:42:25 EDT 2006
User: telrod
Date: 06/08/02 22:42:25
Modified: docs README.txt
Log:
Updates for the 2.0.0.CR1 release.
Revision Changes Path
1.9 +129 -21 JBossRemoting/docs/README.txt
(In the diff below, changes in quantity of whitespace are not shown.)
Index: README.txt
===================================================================
RCS file: /cvsroot/jboss/JBossRemoting/docs/README.txt,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- README.txt 31 Jul 2006 04:17:38 -0000 1.8
+++ README.txt 3 Aug 2006 02:42:25 -0000 1.9
@@ -4,34 +4,47 @@
This distribution of JBoss Remoting contains the following directories:
docs - contains user guide and javadoc
-etc - contains example service xml for creating and running jboss remoting services within the JBoss Application Server.
+etc - contains example service xml for creating and running jboss remoting services within the JBoss Application Server and example web.xml for the remoting invoker servlet.
examples - source code for remoting samples, which are referenced in the user guide. Also contains a build file for compiling and running the samples.
-lib - all the jar files needed for running remoting. Includes the remoting jar itself, jboss-remoting.jar
+lib - all the jar files needed for running remoting. Includes the remoting jar itself, jboss-remoting.jar and the other remoting jars broken out by functionality. Also contains servlet-invoker.war.
src - source code for JBoss Remoting.
tests - unit tests for JBoss Remoting.
Please read the JBoss_Remoting_Guide.pdf in the docs directory for more information about this release and JBoss Remoting.
-New to JBossRemoting 1.4.0
-- Support for pluggable serialization implementations
-- Includes JBoss Serialization (which allows to send non-serializable payloads and better serialization performance)
-- Multiplex transport
-- Compression marshaller/unmarshaller
-- Connection listeners (receives notification of client or server failure)
-- Callback exception handlers
-- Full HTTP 1.1. support
- - Uses Apache Tomcat connectors for implementation
- - GET, POST, HEAD, OPTIONS, and PUT method types
- - Keep-alive supported
- - Handler setting of response headers and response code/message
- - Return of error stream upon > 400 response codes to client
-
-
-The following public API for JBossRemoting was changed in release 1.2.0 which will make it incompatible with previous versions:
-• Removed ClientInvokerAdapter and dependant classes
-• Callback related classes moved to new remoting callback package
-• InvokerCallbackHandler accepts Callback type as parameter instead of InvocationRequest
+Important changes and differences in 2.0.0 release (from 1.4.x release)
+
+- socket invoker configuration ‘socketTimeout’ has been changed to ‘timeout’
+- org.jboss.remoting.Client.RAW value changed from ‘RAW_PAYLOAD’ to ‘rawPayload’.
+- org.jboss.remoting.Client.ENABLE_LEASE value changed from ‘ENABLE_LEASE’ to ‘enableLease’.
+- org.jboss.remoting.Client.HANDSHAKE_COMPLETED_LISTENER value changed from ‘HANDSHAKE_COMPLETED_LISTENER’ to ‘handshakeCompletedListener’.
+- org.jboss.remoting.Client.CALLBACK_SERVER_PROTOCOL value changed from ‘CALLBACK_SERVER_PROTOCOL’ to ‘callbackServerProtocol’.
+- org.jboss.remoting.Client.CALLBACK_SERVER_HOST value changed from ‘CALLBACK_SERVER_HOST’ to ‘callbackServerHost’.
+- org.jboss.remoting.Client.CALLBACK_SERVER_PORT value changed from ‘CALLBACK_SERVER_PORT’ to ‘callbackServerPort’.
+- BYVALUE (byvalue) used to force invokers to be remote but now are local and use cloning of values. If want to force local invokers to use transport, thus making them remote calls, will need to use FORCE_REMOTE (force_remote).
+- InvokerLocator will not automatically convert host name value to an IP address. This change means equality for locators is based on if is host name or ip, but does not resolve one to the other.
+- No longer have InvokerRegistry:
+ o public static synchronized void registerInvoker(String transport, String clientClassName, String serverClassName)
+ o public static synchronized void registerInvoker(String transport, Class client, Class server)
+ o public static synchronized void unregisterInvoker(String transport)
+
+ but instead have been replaced with:
+
+ o public static synchronized void registerInvokerFactories(String transport, Class clientFactory, Class serverFactory)
+ o public static synchronized void unregisterInvokerFactories(String transport)
+
+since invokers are created via factories now (for both client and server invokers)
+
+- org.jboss.remoting.transport.sslsocket - added. includes files that were under org.jboss.remoting.transport.socket.ssl
+- org.jboss.remoting.transport.https- added. includes files that were under org.jboss.remoting.transport.http.ssl
+- org.jboss.remoting.transport.sslmultiplex - added. includes files that were under org.jboss.remoting.transport.multiplex.ssl
+- org.jboss.remoting.transport.sslrmi - added. includes files that were under org.jboss.remoting.transport.rmi.ssl
+- Exception handling for web based clients has changed to will now throw an exception by default. Can get previous behavior by using the 'NoThrowOnError' configuration.
+- The client socket connection pool has been changed to be bound.
+- SSL related classes have been consolidated so all reside within remoting security package and use SSLSocketBuilder at core.
+- Client.connect() method must be called before making an invocation (otherwise will get an exception).
+
Known issues:
@@ -39,6 +52,101 @@
in Jira, please create one.
+Release Notes - JBoss Remoting - Version 2.0.0.CR1 (Boon)
+
+** Bug
+ * [JBREM-303] - org.jboss.test.remoting.transport.multiplex.BasicSocketTestCase(jboss_serialization) failure
+ * [JBREM-387] - classloading problem - using wrong classloader
+ * [JBREM-468] - No connection possible after an illegitimate attempt
+ * [JBREM-484] - AbstractDetector.checkInvokerServer() is probably broken
+ * [JBREM-494] - ClientDisconnectedException does not have serial version UID
+ * [JBREM-495] - classes that do not have serial version UID
+ * [JBREM-500] - ServerThread never dies
+ * [JBREM-502] - not getting REMOVED notification from registry for intra-VM detection
+ * [JBREM-503] - NPE in abstract detector
+ * [JBREM-506] - StreamHandler throws index out of bounds exception
+ * [JBREM-508] - serialization exception with mustang
+ * [JBREM-519] - StreamServer never shuts down the server
+ * [JBREM-526] - TimeUtil not using daemon thread
+ * [JBREM-528] - ConcurrentModificationException when checking for dead servers (AbstractDetector)
+ * [JBREM-530] - Detection heartbeat requires small timeout (for dead server detection)
+ * [JBREM-534] - multiplex client cannot re-connect to server after it has died and then been re-started
+ * [JBREM-537] - org.jboss.test.remoting.transport.rmi.ssl.handshake.RMIInvokerTestCase(java_serialization) - failing
+ * [JBREM-541] - null pointer when receiving detection message
+ * [JBREM-545] - setting of the bind address within MulticastDetector not working
+ * [JBREM-546] - InvokerLocator.equals is broken
+ * [JBREM-552] - cannot init cause of ClassCastException
+ * [JBREM-553] - deadlock when disconnecting
+ * [JBREM-556] - versioning tests failing
+ * [JBREM-561] - http chuncked test cases failing under jdk 1.5
+
+** Feature Request
+ * [JBREM-427] - SSL Connection: load a new keystore at runtime
+ * [JBREM-430] - transporter needs to be customizable
+ * [JBREM-461] - Better documentation for sslmultiplex
+ * [JBREM-491] - need to implement using ssl client mode for push callbacks for all transports
+ * [JBREM-492] - would like an API to indicate if a transport requires SSL configuration
+ * [JBREM-499] - need indication if invoker is secured by ssl
+ * [JBREM-501] - give descriptive names to threads
+ * [JBREM-504] - some synch blocks in AbstractDetector could change
+ * [JBREM-520] - Organize configuring of ServerSocketFactory's and callback SocketFactory's.
+ * [JBREM-527] - Allow user to pass Connector to be used for stream server
+ * [JBREM-532] - need synchronous call from detector client to get all remoting servers on network
+ * [JBREM-539] - add sslservlet procotol
+ * [JBREM-544] - http client invoker (for http, https, servlet, and sslservlet) needs to handle exceptions in same manner as other transport implementations
+
+** Task
+ * [JBREM-21] - Add stress tests
+ * [JBREM-218] - investigate why jrunit report on cruisecontrol inaccurate
+ * [JBREM-311] - need required library matrix
+ * [JBREM-320] - optimize pass by value within remoting
+ * [JBREM-321] - performance tuning
+ * [JBREM-368] - Configure SSLSockets and SSLServerSockets used in callbacks to be in server mode and client mode, respectively.
+ * [JBREM-383] - Document new versioning for remoting
+ * [JBREM-384] - correct manifest to comply with new standard
+ * [JBREM-390] - finish multiplex
+ * [JBREM-412] - Remoting Guide lacks left margin
+ * [JBREM-423] - document how remoting identity works and how to configure
+ * [JBREM-428] - add the samples/transporter/multiple/ to the distribution build (think may be there by default) and update the docs
+ * [JBREM-434] - fix configuration data within document (socketTimeout should be timeout)
+ * [JBREM-435] - break out remoting jars (serialization)
+ * [JBREM-442] - need full doc on how socket invoker works (connection pooling, etc.)
+ * [JBREM-447] - convert static transporter factory methods into constructor calls
+ * [JBREM-452] - Send the pre-release jar to the messaging team for testing
+ * [JBREM-454] - cache socket wrapper classes
+ * [JBREM-477] - remove Client.setInvoker() and Client.getInvoker() methods
+ * [JBREM-487] - Eliminate possible synchronization problem in InvokerRegistry
+ * [JBREM-490] - consolidate the remoting security related classes
+ * [JBREM-493] - Update version of jboss serialization being used
+ * [JBREM-496] - restructure service providers for remoting
+ * [JBREM-497] - change InvokerLocator to respect hostname over ip address
+ * [JBREM-498] - change logging on cleaning up failed detection
+ * [JBREM-507] - need to make configuration properties consistent
+ * [JBREM-509] - Fix call to super() in ServerInvoker's two argument constructor.
+ * [JBREM-511] - Allow HTTPSClientInvoker to create a HostnameVerifier from classname.
+ * [JBREM-513] - Create SSL version of RMI transport.
+ * [JBREM-514] - Fix potential NullPointerException in SSLSocketClientInvoker.createSocket().
+ * [JBREM-516] - add very simple transporter sample
+ * [JBREM-517] - HTTPServerInvoker needs to be deprecated
+ * [JBREM-523] - connection pool on socket client invoker needs to be bound
+ * [JBREM-524] - Clean up MicrosocketClientInvoker code
+ * [JBREM-529] - Need to be able to reuse socket connections after move to TIME_WAIT state
+ * [JBREM-533] - remove external http GET test
+ * [JBREM-535] - add config to force use of remote invoker instead of local
+ * [JBREM-536] - turn off host verification when doing push callback from server using same ssl config as server
+ * [JBREM-538] - update remoting dist build to break out transports into individual jars
+ * [JBREM-540] - need to make servlet-invoker.war part of remoting distribution
+ * [JBREM-542] - change how remoting servlet finds servlet invoker
+ * [JBREM-543] - fix servlet invoker error handling to be more like that of the http invoker
+ * [JBREM-547] - need test case for exposing multiple interfaces for transporter server target pojo
+ * [JBREM-551] - org.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization) failure
+ * [JBREM-555] - fix connection validator to not require extra thread to execute ping every time
+ * [JBREM-558] - Break master.xml documentation into chapter files
+ * [JBREM-559] - update doc for 2.0.0.CR1 release
+ * [JBREM-560] - InvokerGroupTestCase(java_serialization) failure
+ * [JBREM-563] - Multiplex ClientConfigurationCallbackConnectorTestCase(jboss_serialization) failure
+
+
Release Notes - JBoss Remoting - Version 2.0.0.Beta2 (Boon)
** Bug
More information about the jboss-cvs-commits
mailing list