Merge Hessian and binary message builders/formatters
----------------------------------------------------
Key: SYNAPSE-306
URL: https://issues.apache.org/jira/browse/SYNAPSE-306
Project: Synapse
Issue Type: Improvement
Components: Transports
Reporter: Andreas Veithen
Priority: Minor
Fix For: 1.3
SYNAPSE-259 introduced message builders and formatters for the Hessian format:
see package org.apache.synapse.format.hessian in module synapse-extensions.
SYNAPSE-261 added builders and formatters for generic binary payloads: see
package org.apache.synapse.format in module synapse-transports.
While the code looks very different, those builders and formatters do almost
the same thing: the two builders wrap the binary data of the message in a
wrapper element using a DataHandler, while the formatters unwrap the data and
hand it to the transport. The main differences in behavior are:
* The wrapper element (default) names are different.
* The Hessian message formatter handles SOAP faults in a protocol specific way.
Other differences are technical. For example the Hessian builder uses a
TemporaryData object to store the binary data, while BinaryBuilder uses a byte
array. Note that using a TemporaryData object would also be beneficial for
BinaryBuilder, but this is not possible for the moment given that TemporaryData
belongs to synapse-core, while BinaryBuilder is part of synapse-transports.
Given the similarities between the two implementations, the proposal is to
merge them as far as possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]