Type: Feature Request
Status: Closed (View Workflow)
Affects Version/s: None
Fix Version/s: 5.0.0.M2
Security Level: Public (Everyone can see)
Similar Issues:Show 9 results
BLACKTIE-174 Starting a server with invalid XML does not result in a graceful error message and orderly shutdown BLACKTIE-194 Change message broker to HornetQ BLACKTIE-303 Update the transport to support sending messages to topics as well as queues BLACKTIE-379 Support codec layer in Blacktie BLACKTIE-350 Support XA transactions for enqueue BLACKTIE-125 Introduce support for routing requests using JBossESB BLACKTIE-285 Rename Environment.[xml|xsd] to btconfig.[xml|xsd] BLACKTIE-288 Add support for TPGETANY BLACKTIE-193 Received messages cannot be tptypes'd
Currently the message payload is placed onto the wire directly (atmibroker-hyrbid/BufferConverterImpl.cxx) although it is padded to ensure that different machine architectures can read the data successfully.
It is proposed to add an option to encode the data on the wire in XML which should prove useful for routing the request.
The XML format should support all our buffer types:
char data should be encoded into the XML buffer as base64 data
An example buffer would look like:
See https://jira.jboss.org/browse/BLACKTIE-328 to see how the schema looks like.
It is envisaged that this would affect both Java and C++
It will affect configuration
It will affect atmibroker-hybrid
It should not affect atmibroker-xatmi or the java equivalent as the encoding should be transparent to the user.
Note we should try to ensure that what we do here is compatible with: https://jira.jboss.org/browse/BLACKTIE-202
It would be interesting to investigate whether it is possible to encode the message in SOAP rather than raw XML to help with: https://jira.jboss.org/browse/BLACKTIE-329