BPM 2.0 by jcrow

BPM 2.0

The EJB 3.0 component model is promising to change that, and it might. Unfortunately, when a problem is fixed here, a new one pops up there. We experienced this recently when we tried to port our process server on top of Apache Geronimo. Everything worked fine until we tried to package all the components together—process server, workflow services, XForms engine, etc.— then it broke. Somehow, one component was turning a shared Log4j service off, and we had no easy way of isolating which component was at fault. This vexing problem, alongside a dozen similar roadblocks, kept a team of three highlytalented Java developers busy for the best part of last quarter. If a software company like Intalio, which business is to develop software, is facing this kind of challenges, how is it for end-users whose primary business is selling widgets or processing financial transactions? Well, as far as I can tell from many discussions with customers, it’s not that great either… Your average developer cannot deal with this level of complexity. Not that she is not smart enough, but she’s got better things to do, like taking care of business for example. And what is true for J2EE is also true for collateral technologies, such as Eclipse for example—have you ever tried to use EMF and GEF? For me, BPM 2.0 is all about offering a quantum leap in abstraction that will allow your average developer—ABAP, PHP and VB folks—to bypass this complexity and focus on higher levels of the stack, namely processes, rules, and interfaces. To a large extent, these developers have felt left out with the exploding complexity of J2EE and .Net, and BPM 2.0 gives them the tools to be productive again, with a vengeance. That’s precisely why they like it so much.  Original Post