|Re: BPMS Push Monitoring - IProcessExecutionMonitor [message #1140793 is a reply to message #1140683]
||Wed, 16 October 2013 16:10
| Kunal Suri
Registered: April 2013
Location: Paris Saclay, France
Thanks a lot for your quick response
I tried using the step 1 - No Outcome (I hope I didn't do it wrong!)
I tried Step 2 and got the results as expected
Thus, its preferably easier for Stardust to read from the jar file as described in step 2 and I totally agree its more cleaner and reusable to write the code in that format.
Jan Hendrik Scheufen wrote on Wed, 16 October 2013 10:32
I think you have two location options for storing your own services file
- Inside the web project
As you noted correctly there are already two folders in the web project called META-INF. The content of both gets merged when the project is deployed, so it does not matter which one you use. I'd recommend to use the location WebContent/META-INF/services/, because it's more of a standard location where others would expect to find such files.
- In a custom JAR project
If you want to go one step further, you can also create your own JAR project (in Eclipse: File > New > Other > JEE > Utility Project) and include it into the web project for deployment: Right-click on the web project > Properties > Deployment Assembly > Add > Project.
In your utility project you can then create the required folders and files underneath the src/ folder.
We typically recommend this approach, because it makes life easier in the long run to keep custom code and files outside of the web project. For example, you can upgrade or just throw away and recreate the web project without losing any of your custom files.
Let me know if you have any further questions. Disclaimer: I've not tried the above setup myself, yet, but according to the specification this SHOULD work.
Powered by FUDForum
. Page generated in 0.03368 seconds