issues (or features?) with 1.3.1

[albertosaez]

I've testing 1.3.1, trying to port my channels from 1.2.

* For DB receivers, the 'raw message' is a non-pretty-printed XML (when with 1.2 was).
* LLP senders doesn't update the 'QUEUED' state for messages if the ACK timeout is set to '0' (doesn't wait for an ACK). [!!]
* LLP senders can't recognize an ACK from another MIRTH channel.
* Now, the name for 2.3.1 fields has changed (due to HAP update), so I've had to change all of my transformations. This is clearly a feature, but for me this has been horrible.
* LLP and DB receivers (at least) creates two different entries for each message: one when the message is received (set to RECEIVED), and another when the message is SENDED or ERROR. I don't know if this is an erorr or a feature.
* Messages in the MessageBrowser are showed from oldest to newer, which is different from 1.2

--> The' Validate JS' button doesn't point to the right line (well, this happened with 1.2 too)

[!!] this seems to be an error in my own code. I'll test it

[chrisl]

Re: issues (or features?) with 1.3.1

1) For DB receivers, the 'raw message' is a non-pretty-printed XML (when with 1.2 was).
-Not sure about this one - we removed Pretty Printing from the mule-config to preserve the proper spacing on the File Writer templates. Not sure if this would have any effect. Have you checked it in the Preprocessor?

2) LLP senders doesn't update the 'QUEUED' state for messages if the ACK timeout is set to '0' (doesn't wait for an ACK). [!!]
-We changed the QUEUE code a bit to make sure the status is set to QUEUED even if "Use Persistant Queues" is not selected. Let us know if you find anything

3) LLP senders can't recognize an ACK from another MIRTH channel.
-Weird. Do you get any errors? Can you look into this code? Thanks!

4) Now, the name for 2.3.1 fields has changed (due to HAP update), so I've had to change all of my transformations. This is clearly a feature, but for me this has been horrible.
-What is the old name and new name? We can add the replacement to the Import Converter.

5) LLP and DB receivers (at least) creates two different entries for each message: one when the message is received (set to RECEIVED), and another when the message is SENDED or ERROR. I don't know if this is an erorr or a feature.
-This is a feature. The previous stat tracking and message list was inaccurate. Now you have a message for whatever was received and a message for each destination. You can now see the exact number of messages received, rejected, queued, errored or sent. We are upgrading the message browser in 1.3.2 to show all messages from the same original message grouped in a tree.

6) Messages in the MessageBrowser are showed from oldest to newer, which is different from 1.2 &
7) The' Validate JS' button doesn't point to the right line (well, this happened with 1.2 too)
-Add this to the JIRA and we'll fix that for 1.3.2.

Thanks a bunch for your testing and code Alberto, we appreciate it!

-Chris