Dejan Bosanac wrote:
>
> I guess we should set transformation_error header in cases like this.
> Added
> to TODO :)
>
This would be very helpful. Until now I had no success even with annotated
classes, the message still has an empty body. Sending and receiving within a
Java client works perfectly. I then tried to receive the message using the
new Java API for STOMP, but after successful login, the client does not
receive the CONNECTED frame (I tried with and without authentication to
verify that the basic connection works).
Objectmessage with transformation=jms-json and JSON content sent from my
Delphi STOMP client will be received by the same client again correctly with
the message in JSON format. So it looks like the broker does not need a
matching Java class always.
However, if the JSON content matches the structure of a Java class in the
classpath, I assume that the broker should display it as an Java object in
the admin console - even if the sender is no Java application - and it
should be possible to retrieve an object in the Java client.
So I will also try to send the JSON encoded object from the Delphi to the
Java client. I can build the correct JSON encoded message body using XStream
and just set up the Delphi side to send exactly this message content.
Best Regards
Michael Justin
--
"Hey! It compiles! Ship it!"
--
View this message in context:
http://www.nabble.com/Broker-sends-empty-body-in-STOMP-ObjectMessage-%28using-jms-json-transformation%29-tp21727046p21762138.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
