anonymous wrote : But you're still happily using Seam with jBPM?
Happy? Honestly, I think the Seam + jBPM hype in the early days of Seam (winter-spring
2006) was a bit over hyped and I don't think it receives enough attention by the Seam
team. I think part of the problem is a lot of the features get implemented in a sort of
'toy' or 'proof-of-concept' mode - not really pushed around the block. I
think the combo of jBPM + Seam + EJB3 holds a lot of promise - maybe there's
opportunity for better integration between Seam and jBPM with respect to custom
ActionHandlers, DecisionHandlers, things like that...possibly some even Seam base classes
for these that deal with resource injection issues 'seamlessly' (e.g. JbpmContext,
EntityManager, etc...).
The jBPM API's are often weak in many areas - the core implementation and
functionality is basically just what you need for long running processes. The API's
(IMHO) are not really designed with the customer in mind (by customer, I mean the
developer that uses the API's). As an example, try to get and cancel a timer task in
a custom ActionHandler. Also, for extra points, try getting the 'current open
task' on a process without knowing the taskId ahead of time via the API's... ;-)
Anyway - I am happy using Seam, I am less happy about Seam + jBPM integration, I'm
also concerned that the developers will stick with relatively simple use cases and
increasingly will be distracted by all the JSF-tag library noise (first ICEFaces, now
RichFaces, ...). Ultimately, I've been able to solve 'most' of my problems
with jBPM and Seam, but my solutions are not as 'elegant' as they could be.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029814#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...