MQSeries.net :: View topic - Code constraints for Java Custom Node? Reuse HL7 parser?

simon.starkie

I am considering a new Custom Node in Java to call a pre-existing Java API that retrieves data from a legacy system (CICS Cobol DB2). The Java API already exists and is the preferred (by the owner of the legacy system) means of retrieving data from the legacy system.
How much lattitude do I have in Java when coding a Custom Node for MQSI? That is, I don't think a Java Sleep, for example, would be a great idea, but it could be done. Sorry this is a bit vague, but I need to get a handle on this before any coding approach (or even MQSI itself) is chosen for a solution.

Also, we have a Custom HL7 parser that was created explicitly for another project. We now have a new project that wants to input XML messages and output HL7 messages. It would be nice if we could re-use the Custom HL7 parser and use resetcontentdescriptor to reparse the message from the tree (i.e. that was originally input as XML) into HL7 prior to ouputting it to a queue. Are there any considerations I should worry about before suggesting this approach? I'm trying to keep MQSI from becoming a defunct product at this site...reusing components from previous projects would help us to keep MQSI/WMQI for a while...

Thanks.