[openorb-announce] The Community OpenORB 1.3.0 BETA1 is out

[Michael R. <mi...@ru...>]

The Community OpenORB 1.3.0 BETA1 is out.

After nearly 6 months of steady product improvement, rationalisation
and platform enhancement, the OpenORB community is proud to release 
the first beta of "The Community OpenORB" product suite version 1.3.

The archives of all packages can be found at the SF project download
area: https://sourceforge.net/project/showfiles.php?group_id=43608

Have fun,
   The Community OpenORB Team


Improvements:
=============

All modules have been updated and brought into line with strict 
coding standards, major enhancements to the logging framework 
(including support for alternative logging mechanisms including 
Log4J, JDK1.4 Logging, and Avalon Logkit), a complete revision 
of the build systems with unification of the build structure 
across all packages, and the introduction of docbook based 
documentation.  A complete list of changes per package is available
in the WHATSNEW file included with each module.

OpenORB:
--------
- Reduced memory footprint.
- Improved source code readability (aligned with Apache/Jakarta coding
  guidelines).
- Lots of bug fixes.
- Enhanced JDK 1.4 support (*1)
- Relocation of the Transient Naming Service to the NamingService
  package.
- Total refactoring the logging system (server side exceptions will
  not disappear on the server anymore).
- Improved support for multiple ORBs in a single VM (removed
  System.exit() calls inside the ORB)
- Many internal code improvements (more refactoring).
- Enhanced javadoc.
- Enhanced ORB configuration and initialization. 
- IDLCompiler code generation improvements (speedup in invoke methods,
  default factory generation, IdlParser can load IDL file from jars 
  now, improved debug output, removed InterfaceRepository lookup for
  performance reasons)
- Improved support for multiple endpoints in an IOR by adding the new
  property openorb.client.bindings.discard_old for tweaking of 
  endpoints received from LOCATION_FORWARD replies and by implementing 
  the support for the propertyset XML tag in the OpenORB config files.

RMIoverIIOP (*2):
-----------------
- Lots of bug fixes
- Improved source code readability (aligned with Apache/Jakarta coding
  guidelines).

SSL:
----
- Improved source code readability (aligned with Apache/Jakarta coding
  guidelines).
- JDK 1.4 support.

EvaluatorUtility:
-----------------
- Some bug fixes.

NamingService (INS) (*3):
-------------------------
- Added the transient NameService from OpenORB core.
- Added support for programmatically creating NS instances.

NotificationService:
--------------------
- Lots of bug fixes.
- Many performance improvements.

PersistentStateService (PSS) (*3):
----------------------------------
- Several logging improvements.
- JDK 1.4 support.

TransactionService (OTS):
-------------------------
- Added support for programmatically creating OTS instances.


Foot Notes:

(*1)
    See README for additional notes concerning deployment restrictions 
under the Win32 in combination with JDK1.4.0 release.

(*2)
    Full JDK1.4 support will be included in the final release 
version.

(*3)
    Early access implementation aligned with a OpenORB 2.0 release 
target are maintained under the Jakarta Avalon Project. Refer:
http://cvs.apache.org/viewcvs/jakarta-avalon-apps/enterprise/
    A new version of the Persistent State Service can be found here:
http://cvs.apache.org/viewcvs/jakarta-avalon-apps/enterprise/pss/
This new version is aligned to the PSS 2.0 spec. and incorporate many
bug fixes over the source code base at SourceForge. The PSS 2.0 spec. 
is not API compatible to the old version (1.x). When migrating from PSS 
1.x to PSS 2.0 modifications will be required to code dealing with 
initial reference resolution. In addition the concepts of catalogs has 
been removed as part of OMG specification finalisation.  Refer to the 
README for additional migration notes.  A NamingService (INS) based on 
PSS 2.0 is available here:
http://cvs.apache.org/viewcvs/jakarta-avalon-apps/enterprise/ins/


Bug Reporting:

Please report any problem you find to the SourceForge mailing list
ope...@li.... When the problem is identified as a bug
it will be filed at the SourceForge bug tracking facilities.