kukeltje, you exactly describe how jpdl should expose it. one option (as we did it
before) is to put all those kind of components in the jpdl project.
jbpm can integrate with about anything. keeping all those library dependencies manageable
is difficult. some of these integrations like email, jcr and probably ical require whole
specific test environments.
merging all of that into the jpdl project can become a problem. that's why i'm
thinking of extracting it into separate projects.
but jpdl will still just use it and expose those features as it pleases.
and it's definitely not decided yet. it might go as well into the jpdl subproject
directly. i'm just sketching the context so that you (and all other readers) can shed
their light on this topic
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135704#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...