Hi,
"kukeltje" wrote : What I (personally) want to prevent is re-inventing the at
least a complex wheel with the jobscheduler instead of using/extending jms just because
some people do not want to use an appserver.
|
| I'm not against spring, but I've seen implementations of systems much more
complex/wired just to prevent using MDB's.
Here's just another vote for improved spring integration. Generally I agree with your
comment, but the current application I'm working on is a dedicated background
application that doesn't need the overhead of an appserver so we are using jBPM in a
standalone environment. This is one of the reasons we picked jBPM because of the stated
goal of being lightweight and able to run in a standalone / embedded environment w/o
requiring an appserver.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091749#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...