This content has been marked as final. Show 2 replies
We have an online application build around seam, POJOs and hibernate.
Our business seam components ("managers" + "model" classes) are isolated into a separate jar file (common.jar), the "view controler" seam components (aka "backing beans") are directly held into the war module, the war module calling the classes into the common.jar module.
We have the need for batch processes, ie processesthat will run outside any web/jee container, with a standard j2se jdk, from a plain java class, possibly running for hours. Those processes will use the seam common components from the common.jar file.
The high level algorithm is :
- bootstrap the seam engine - for each business item to process (maybe tens of thousand or more...): - begin transaction - do some business stuff that update the database - commit - shutdown the seam engine