1 of 1 people found this helpful
We have someone contributing an export tool to create an XML format of the messages. But Messages on the journal and server are just blobs, nothing else.
Take a look on PrintData. Maybe that gives you what you want.
PrintData is a class that I use to debug Journal data from time to time. It's not documented yet on the user's manual as it's not final yet.
Thanks for the alternative, but I'm more interested in reconstructing the Message Object starting from the text file obtained as the result of the conversion using ExportJournal. There is a section starting with @data, I'm interested how exactly is the Message encoded into that sequence, because a simple Base64 followed by a deserialization does not properly reconstruct the Message. Isn't there a predefined way of obtaining it? If not, could you be so kind to advise on how to decode that sequence back into the original Message Object?
Thanks in advance!
We are working into another export tool, based on org.hornetq.core.persistence.impl.journal.PrintData, that will give you properties as strings and the bytes blog will just be user's data. That will be independent of version and we may use it to exchange data with other providers.
Thanks again. Any idea about when is that new version of export going to surface the web?
And one more thing.
What is your professional opinion, could one person make his own message recreator in a fain amount of time? Not necessarily at high quality standards, just something basic.
Thanks in advance! (and sorry if I'm bugging you).