When I step through and debug in Eclipse it is fine. I've added print statements to the console to list various values extracted from the MSH HAPI and it fails when attempting to print the first data from the DATE field in the MSH header when running the JAR. But in Eclipse it goes through just fine and print out all the values. and completes the whole cycle successfully.
What stands out in the GOOD log is line 199 of the Camel parsing does not appear in the JAR/BAD log: "2013-01-20 21:47:05,865 INFO Camel (camel-1) thread #1 - JmsConsumer[hl7] ca.uhn.hl7v2.VersionLogger - HAPI version is: 1.2" Nor do the lines 212 - 215. It's as if it's using a different Parser: 2013-01-20 21:47:05,942 DEBUG Camel (camel-1) thread #1 - JmsConsumer[hl7] ca.uhn.hl7v2.parser.MessageIterator - hasNext() for direction MSH 2013-01-20 21:47:05,942 DEBUG Camel (camel-1) thread #1 - JmsConsumer[hl7] ca.uhn.hl7v2.parser.MessageIterator - hasNext() current position: Root:SIU_S12(0) 2013-01-20 21:47:05,942 DEBUG Camel (camel-1) thread #1 - JmsConsumer[hl7] ca.uhn.hl7v2.parser.MessageIterator - hasNext() current position: SIU_S12:MSH(-1) It looks like the HL7 was not parsed successfully or correctlry by the time it reaches my Bean. 2013-01-20 21:47:05,942 DEBUG Camel (camel-1) thread #1 - JmsConsumer[hl7] ca.uhn.hl7v2.parser.MessageIterator - hasNext() for direction MSH -- View this message in context: http://camel.465427.n5.nabble.com/HL7-component-works-in-Eclipse-IDE-but-not-when-exported-to-JAR-tp5725936p5725945.html Sent from the Camel - Users mailing list archive at Nabble.com.
