You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Jamie McCrindle <ja...@gmail.com> on 2006/06/13 13:11:01 UTC
bpmscript jbi component
hi all,
i'm focusing on putting together the standalone bpmscript jbi
component and i thought i'd run it by you guys in case i'm heading in
the wrong direction etc.:
* currently bpmscript has a bunch of jbi components but it should
probably be a single component with a number of endpoints:
bpmscript component: installs service units, creates process instances
based on messages to processes (not exposed as endpoints as yet),
passes messages to existing process instances
remote process manager component: used by the bpmscript web console to
do things like list processes, process instances etc.
task list component: called by processes to create tasks
remote task list manager component: used by the bpmscript web console
to list existing tasks and allow tasks to be completed
alarm component: used to manage distributed timeouts for process instances
dynamic saaj component: slight change to the saaj component that
allows a process instance to specify the soap endpoint in the message
rather than at configuration time (this could be deployed separately,
though, or the change could be rolled into the current saaj
component?)
corellation component: still in the works but it'll corellate and
route messages to process instances that are interested in inbound
messages based on some expression (e.g. a process instance registers
interest in messages from a rss or file poller).
my original plan was to use a lw-container service unit to deploy all
of these components at once but it would be better to be able to
deploy bpmscript as a fully fledged jbi component. as such, it looks
like i'll have to change the components above to be different
Endpoints for a single BpmScriptComponent rather than a collection of
components in their own right. Does that make sense?
most of these end points are required by default which is appears
different to the way that endpoints are handled in the archetype. I
assume there won't be a problem registering them by default?
* Each process should also be an end point. Potentially each process
instance should also be an endpoint (for unsolicited messages to the
running process instance e.g. shutdown, retry etc.). Not sure of the
overhead of making each process instance a dynamic endpoint.
* bpmscript is still using maven 1, it's been easy enough to get the
files from the m2 service engine archetype and there are enough
examples lying around in servicemix for it not to be too much effort
to work out a maven.xml / project.xml for it.
thoughts?
Jamie.