Release Notes - Petals BC SOAP - Version 4.0.3 - HTML format

Bug

• [PETALSBCSOAP-2] - When handling SOAP faults, faultCode can have an unbounded prefix.
• [PETALSBCSOAP-16] - Some traces are not handled by the component logger and some others at a level too high
• [PETALSBCSOAP-17] - As consumer, the timeout of a sendSync is not properly logged
• [PETALSBCSOAP-19] - Modules are loaded even if they are not set in configuration
• [PETALSBCSOAP-24] - Can't create get an Axis service client from the pool
• [PETALSBCSOAP-26] - NPE in the Petals console
• [PETALSBCSOAP-28] - Propagate partner's SOAP Fault "as is"
• [PETALSBCSOAP-32] - Log that JMS is activated whereas the SU configuration specifies not.
• [PETALSBCSOAP-35] - SOAP over JMS - A queue is created on the JMS server when installing a SU even if the JMS transport parameter is disabled
• [PETALSBCSOAP-40] - Unable to start the component if SE Notif is not available
• [PETALSBCSOAP-42] - BC soap returns wrong WSDL.
• [PETALSBCSOAP-43] - Change the default host in the jbi.xml of the component to 0.0.0.0
• [PETALSBCSOAP-44] - Error when uninstalling a SU REST
• [PETALSBCSOAP-45] - 0.0.0.0, the default host, crashes the component under some OS

Improvement Request

• [PETALSBCSOAP-15] - Resolve the target operation and MEP in consume mode
• [PETALSBCSOAP-38] - Remove the SU parameters add-root and remove-root
• [PETALSBCSOAP-39] - JMS parameters should be settable from the configuration MBean
• [PETALSBCSOAP-41] - wrong log level when ctaching axis exception
• [PETALSBCSOAP-48] - The fault actor is not transmitted in the SOAP fault in the consumer mode

New Feature

• [PETALSBCSOAP-34] - Axis 1 webservice stack compatibility

The text area below allows the project release notes to be edited and copied to another document.