[ebxmlms-develop] Hermes v0.9.3.0 released

[Patrick Y. <kc...@ce...>]

Dear all,

We are pleased to announce a new stable release of Hermes today. You can =
download the latest release either from our project homepage on =
SourceForge (http://sourceforge.net/projects/ebxmlms), or from =
freebXML.org (http://www.freebxml.org).

Thanks a lot for your support. For your information, here is the release =
note of this release:

Version 0.9.3.0
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Configuration:
- Splitted the property file into three. msh.properties.xml will be for =
Hermes
  server, msh_client.properties.xml will be for MSH stub and=20
  monitor.properties.xml is for Monitor.
- Bug fixed for wrong property file entry being read for rolling log =
file.
Operation:
- Enhanced exception support. Now exception would be thrown if any SOAP =
header
  that has the mustUnderstand flag equals to "1", but cannot be =
processed.
- Modified DiagTool to create dump directories automatically.
- Log the MSH halt and resume time to MSHLog table.
- Added "GetIsHalted()" function to check if the MSH has been halted. =
Monitor
  has been updated to demonstrate its usage.
- Added unregistration of application context. However, the =
unregistration will=20
  fail when there is pending message to be sent or to be received.
- If the application context of the incoming message cannot be =
recognized, now=20
  it will send an error message back to the originating MSH.=20
- Added a new class Utility for common methods called by server and =
clients.
- Modified to suspend the mail polling thread also when the MSH is =
suspended.
- Fixed the bug that the starting time of archive / backup operations =
cannot be
  earlier than year 2001.
- After a pending message is marked as "deleted", it was possible that =
the same
  message be returned in the subsequent getPendingMessages() call since =
the
  sending thread is not immediately shut down but it needs to wait till =
the next
  retry time. It is now changed in the way such that deleted sending =
threads are
  not returned by getPendingMessages().
- Trusted Repository delivery method is now divided into "server-side =
trusted
  repository", which is written by the MSH, and "client-side =
repository", which
  is written by the client stub (Request Object).
- The use of polling directory is removed and it can be safely deleted. =
All
  messages are now stored in the message repository.
- Fixed the bug that using different messaging mode in the same =
application
  context causes error.
- Updated XERCES library to version 2.2.1
- Supported fractional seconds in UTC formatted time, and we now do =
checking on=20
  timestamp when a message arrives. Now we generally use UTC time for =
all=20
  date/time parameter values and for returning results
- Modified the behaviour of archive by date. Now all the messages that =
are in=20
  the time range (inclusive) are archived and nothing more.
- Reformat the results returned by getDBConnectionPoolInfo so that it =
looks=20
  similar to the relevant settings in configuration file.
- Fixed bug in dumping data from MSHLog: only output those in specified =
time=20
  period only.
- Fixed the logger error displayed in tomcat console under Windows =
environment.
- Fixed the bug that always return success in "restore" function.
- Bug Fix: the response message of archiveByDate() now shows the failed =
message=20
  IDs clearly.
- Bug fix: Null pointer exception results if the message repository =
directory=20
  cannot be written. Now it throws exception that is properly handled by =
the=20
  Transaction object.
Packaging:
- Modified packaging part to fulfil the requirement of ebMS =
specification.
- Reorganized the exceptions thrown when composing/internalizing an =
ebXML
  message. Now a SOAPValidationException will be thrown in case the =
operation is
  invalid with respect to the ebXML schema, and an =
EbxmlValidationException will
  be thrown if a logical error occurs.
- Refactored an ebXML message validation module, which is responsible =
for
  validate the correctness of the received message according various=20
  requirement from the ebMS specification. The checkings include SOAP=20
  formatting, payload integrity, etc. For any incorrect messages, =
corresponding=20
  ebXML error messages would be sent back to the sending MSH.
Database:
- Fixed the bug that connection pool cannot be reset successfuly if a
  connection cannot be closed successfully.
- Added "GetNumRecordsInDB()" function to check the number of records =
stored=20
  in MSH database. Monitor has been updated to demonstrate its usage.
- Added "GetDBConnectionPoolInfo()" function to check the information =
about the=20
  connection pool. Monitor has been updated to demonstrate its usage.
- Modified database connection pool mechanism. Now a new database =
connection=20
  will be created and returned if the old connection has been idle for a
  specified time period.
- Modified to close the database connections asynchronously, so that it =
won't
  block the main threads.
- Modified to mark the database connection invalid when returning to =
connection=20
  pool if any error occurred during database operations, so that the =
object is=20
  discarded and a new connection is created next time it is requested.
- Changed DB schema to accommodate more than 2 possible values of sync =
reply
  mode in CPA.
- Now check the healthiness of DB connection in the connection pool =
before any=20
  database operations.
- Bug Fix: "archiveByDate" function, when used with SQL Server, results =
in a=20
  SQL exception "cannot connvert arithmetic data type". This is fixed by =

  using parameterized query when selecting records.
- Bug fix: connection is committed and then freed after archive =
operations now.
Monitor:
- Fixed bug in monitor: once digital signature is turned on, it cannot =
be=20
  turned off even if the check box is unset.


Regards,
-Patrick
--
Patrick Yee
System Architect
Center for E-Commerce Infrastructure Development (CECID)
Dept. of Computer Science and Information Systems
The University of Hong Kong
Tel: (852) 22415674
Fax: (852) 25474611