[
https://issues.apache.org/activemq/browse/AMQ-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies reassigned AMQ-1499:
-------------------------------
Assignee: Dejan Bosanac
> OXMMessageTransformer
> ---------------------
>
> Key: AMQ-1499
> URL: https://issues.apache.org/activemq/browse/AMQ-1499
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.4.0
>
> Attachments: oxm-message-transformer.zip
>
>
> I've created a message transformer that uses Spring OXM as a wrapping layer
> for different marshallers. I've used the current XStreamMessageTransformer as
> a base for this work. All classes are put in a separate "oxm" package, so I'm
> sending it as a zip archive.
> There three interesting classes here.:
> The first one is the AbstractXMLMessageTransformer which encapsulates all
> operations (such as transformation type: xml, object, adaptive) except
> marshalling itself (which is left abstract).
> OXMMessageTransformer is then easily created by extending this class. I've
> also implemented new XStreamMessageTransformer on these principles, but I've
> put it in the "oxm" package since I didn't want to mess the current one.
> Basically, with this new one, the whole "xstream" package is obsolete now.
> I've also refactored test cases, so it is easy now to use the same tests with
> different transformers/marshallers. This will ease the task of creating
> additional transformers (Castor, Jaxb, ...) if someone would like to use them
> without OXM for any reason.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
