From: Tom W. <tw...@su...> - 2013-11-20 00:05:33
|
Hi. I'm building my first HAPI application. I followed the sample code to build a receiving application and can successfully run a jar which starts the server, starts a client, sends a message, and shuts down the server (basically the sample code). Now, what's the quickest way to get my application to run as a standalone jar file, so that I can let it run on my local machine and start throwing messages at it? Do I write a main method that starts the server and then do some "wait forever" trick? Is there a best practice for running a HAPI ReceivingApplication as a standalone jar? For example, let's say I package my application as MyHapiReceiver.jar with a main method >From the command line, I run: %java -jar MyHapiReceiver.jar And then inside eclipse I start running client tests, which send messages to port 1011 (default) When I'm done testing, I'll need to stop MyHapi.jar gracefully. Simplicity is key. I want to get this up and running without putting it in a container or ESB. However I do have an instance of JBoss EAP 6 (no ESB) if that makes it easier (I suspect it won't). If someone has wrapper code to make the sample receiver application run as a standalone jar, that may be enough: http://hl7api.sourceforge.net/xref/ca/uhn/hl7v2/examples/ExampleReceiverApplication.html Any advice is appreciated. -tom |