[ebxmlms-general] Hermes v0.9.2.0 released

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

Dear all,

We are pleased to announce a new 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.2.0
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
- Supported transaction locking of a message based on its message ID
- Added clean up code to properly free resource such as Resultset, =
Statement
- Added database fields in vision to support sync reply, message order =
and=20
  persist duration
- Bug fixed: now deliver message to application works properly no matter =
what
  mode is used for the MSH client to get message from MSH server
- Added an optional feature: positive acknowledgment to MSH client if =
the=20
  message is successfully sent to the destination
- Added a system feature: clean halt, which will stop all sending and =
receiving
  processes, and the MSH client will receive error messages as if the =
messages
  are not sent successfully
- Added a system feature: backup and restore of MSH states and =
repository
- Bug fixed: no more NullPointerException when fail to authenticate the =
command=20
  object due to missing specification of user name/password in client =
side
- Extended the Request API and make it more user-friendly
- Added a system feature: to query the message status
- Bug fixed: now the message can be stored properly to repository even =
when
  the MSH is under stress
- Retry time is now calculated more accurately even if the MSH is halted =

  between retries
- Added a system feature: now we can delete a message in the queue if it =
has=20
  not bee nsent successfully
- Added a system feature: archiving the repository of MSH
- Restructured logging
- GUI in MSH Monitor updated to demonstrate the new features
- Modified the namespace to conform to ebMS Specification [2.3.1]
- Bug fixed: NullPointerException when fromUTCString is given an =
incomplete=20
  date/time string.
- Bug fixed: NullPointerException when an error message is received from =
the=20
  other MSH (e.g. TimeToLive expired) that needs to be forwarded to the =
user. It
  was previously caused by the "null" value of mshConnection variable in =

  onMessage() function when an error message is received.
- Added user interface to add TimeToLive to the message.
- Detailed message status that includes information in SentMessage and=20
  ReceivedMessage table.
- Changed the placement of the text field "Time to Live".
- Appends "charset" to the content-type mime header.
- Added namespace references so that the generated ebXML messages can be =

  validated.
- Implements "getTrustedRepository()" API. Now it can get trusted =
repository
  locatons from the MSH directly.
- Changed the database column name to avoid any possible SQL keywords
- Fixed the bug that the sending threads are not restarted after =
resuming MSH from
  halt state.
- Fixes the use case that connection pool cannot be reset successfuly if =
a=20
  connection cannot be closed successfully.
- Fixes the use case that NullPointerException will result if =
getMessageStatus()
  is used to query more than one message.
- Fixed the bug that the sending threads are not restarted after =
resuming MSH from
  halt state.
- Fixed the bug that diagnosis dump only parses the date part of the =
date/time=20
  specified.
- Used CommandConstants objects to contains command constants, so as to =
enforce=20
  maximum compatibility of Command objects across version.
- Fixed the bug that diagnosis dump cannot dump database when both =
Application=20
  Context and Starting / Ending date/time are specified.
- Retry sending acknowledgment only if the current thread sending the =
ack does not
  exist. =20
- Fixed the use case that if the application context cannot be archived =
because
  some of the messages are not ready, archiveByDate() and =
archiveByAppContext()
  return an invalid error message.
- Fixes the MSH backup function. Now it returns failure message =
correctly in
  case backup operation failed.
- Fixes the use case that archive only creates the directory on the =
first time of=20
  invocation if the destination directory does not exist; and runs =
successfully=20
  in subsequent runs.
- Allow database password to be zero-length in diagnosis tool =
configuration file.
- Modified the MSH properties file to demonstrate correct settings. The =
message
  repository and the objectstore directories cannot have a parent-child
  relationship.


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