Re: [ebxmlms-general] Hermes 1.0.0.1 available at freebxml

[David W. \(XML\) <da...@dr...>]

Patrick,

Congratulations!

I've added the news release to ebXMLforum.

Thanks, DW


----- Original Message ----- 
From: "Patrick Yee" <kc...@ce...>
To: <ebx...@li...>
Sent: Friday, August 12, 2005 12:20 PM
Subject: [ebxmlms-general] Hermes 1.0.0.1 available at freebxml


> Hi,
>
> We are happy to announce Hermes 1.0.0.1.
>
> We have tagged the CVS head as r1001, and we have also updated the zip
> files at freebxml.org to make them include the changes made at CVS head
> so far. Please see the release note attached.
>
> Thank you for your support!
>
> -- 
> Regards,
> Patrick Yee
> Center for E-Commerce Infrastructure Development
>
> Making E-Commerce Everyday Commerce
>
>


----------------------------------------------------------------------------
----


> Hermes 1.0.0.1 Release Note (12 Aug 2005)
> =========================================
>
> Enhancement
> 1. Reject self-signed certificate when verifying digital signature. This
is to prevent a potential problem when somebody used a self-signed
certificate to spoof someone else with a correct applicaton context.
> 2. Enhanced performance when large payload is received.
> 3. Make use of prepared statement to enable database access optimization
in some cases.
> 4. Some code rearrangement to avoid overloading of database connection
pool.
>
> Bugs Fixed
> 1. Fixed several memory leak problems.
> 2. Fixed the select criteria when doing archiving to ignore all
undelivered message.
> 3. Fixed an issue in file persistence, which we create a directory for
archive only if it does not exist.
> 4. Fixed a deadlock problem when delivery handler is working slow and at
the same time a retry message comes in.
> 5. Fixed a problem which now the database is not updated if there is any
problem in resolving outgoing URL.
> 6. Fixed an issue in ebXML message packaging. Now the service element will
be created correctly with type information.
> 7. Fixed an issue when handling loopback message which may cause deadlock
problem.
> 8. Some code review to make the source code more consistent.
>