6 Replies Latest reply on Nov 7, 2012 6:41 PM by clebert.suconic

XmlDataImport create textmessages without content

dastraub Nov 7, 2012 10:59 AM

Using HQ 2.2.14.Final, we export messages with the XmlDataExporter and import using XmlDataImporter.

Unfortunatly, the imported messages has no text.

Here is a example from the exported XML :

</properties>

</queues>

<body>

<![CDATA[AAAAAAAAAAAAAAAAAAAAADYBAAAAIFQAaAByAGUAYQBkACAAMAAwACAATQBzAGcAIwAwADAAAAAAsgAAAAAAAAIFAQAAAEZqAG0AcwAuAHEAdQBlAHUAZQAuAG0AYQByAGsAdABkAGUAcABvAHQALwBvAHMALwBhAHUAZABpAHQALQBxAHUAZQB1AGUAAQhEEvEo7xHin-VtSkgz3Z4D_wAAAAAAAAAAAAABOtt3uZ8EAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=]]>

</body>

</message>

</messages>

1. Re: XmlDataImport create textmessages without content

jbertram Nov 7, 2012 11:08 AM (in response to dastraub)

I believe a bug was fixed for this. Can you try with 2.3.0.Beta1? I'm looking for the related JIRA in the mean-time.
Actions
2. Re: XmlDataImport create textmessages without content

jbertram Nov 7, 2012 11:11 AM (in response to jbertram)

Here is the relevant commit: https://github.com/hornetq/hornetq/commit/714ba18badd1649580e818c9986ade79f9051f60
Actions
3. Re: XmlDataImport create textmessages without content

dastraub Nov 7, 2012 11:35 AM (in response to jbertram)

<![CDATA[AQAAACBUAGgAcgBlAGEAZAAgADAAMAAgAE0AcwBnACMAMAAwAA==]]>
works better , thanks !
Actions
4. Re: XmlDataImport create textmessages without content

clebert.suconic Nov 7, 2012 12:08 PM (in response to dastraub)

I believe I have seen a case about someone asking us to set the Text there instead of the encoding. (In case of TextMessages). however.. there are two issues:

I - On core level everything is byte-array (on the server's side).

II - We could infer the message-type property that is on the message, (by decoding it first), but then there's an issue with CharSets... How to preserve it? This one here will work fine whatever the chartset. (it's just plain bytes.. and they get preserved).
Actions
5. Re: XmlDataImport create textmessages without content

dastraub Nov 7, 2012 5:35 PM (in response to clebert.suconic)

You're right - my first suspicion was also an encoding-issue, and I lost some time with this f...cking I/O-API to make ensure everything is UTF-8 ...
To working only with bytes is enough at this level.

An other question - is it possible to reuse the message id ? I see your UUID has no "parsing" function (yet). But so we can make sure, that messages are imported only once.
Actions
6. Re: XmlDataImport create textmessages without content

clebert.suconic Nov 7, 2012 6:41 PM (in response to dastraub)

that was done on purpose... the messageID should be assigned at the time of the import. The importing will be a basic producer, so the messageIDs will be re-generated.

When we came up with this, we even though about inter operability with brokers.
Actions

Go to original post