On Fri, Sep 25, 2009 at 8:31 PM, Lars Heinemann <[email protected]> wrote:
> There is no real magic with NormalizedMessage. Just have a look at the > JBI spec. It's explained there very detailed. > I think you did the right thing with doing a custom marshaler for your > protocol. So now it depends what you got when de-serializing your > object message. I think if its a pure object you can just put that > object to the headers map of the inMsg. Another way would be to use > xstream for serializing / deserializing objects which would give you a > perfect XML you can directly put into the content of the normalized > message. I don't know your stuff good enough to give you better hints > ;) > > The JBI spec is here? jbi-1_0-fr-spec.pdf - http://jcp.org/aboutJava/communityprocess/final/jsr208/index.html I went down the xstream path, since we already use xstream to send messages over a wireless network. I'll read the spec and wait for enlightenment. Thanks very much for the hints.
