-
1. Re: creating user nodes and attributes
mwohlf Aug 9, 2010 12:17 PM (in response to parvathy)you can create custom- and java-nodes, check out the user guide section 6.2 and 6.3 at http://docs.jboss.com/jbpm/v4/userguide/html_single/
if you want to be extra cool you can even extend jBPM with your own nodes and node bindings, see: http://www.lunatech-research.com/archives/2010/03/09/jbpm4-and-seam-working-together
-
2. Re: creating user nodes and attributes
parvathy Aug 9, 2010 12:43 PM (in response to mwohlf)thanks a lot..i guess the second link will help me...i have already gone thru the user guide.
Thanks
Parvathy
-
3. Re: creating user nodes and attributes
mwohlf Aug 9, 2010 1:16 PM (in response to parvathy)Instead of patching the jbpm4 jars with your own jbpm.jpdl.bindings.xml file you can just add your own bindings in a file called jbpm.user.bindings.xml check the Source of the org.jbpm.jpdl.internal.xml.JpdlParser, the file is defined in a static variable DEFAULT_BINDING_RESOURCES.
-
4. Re: creating user nodes and attributes
jlgranda81 Nov 28, 2010 12:13 AM (in response to mwohlf)Hello, I try to adapt instruction from http://www.lunatech-research.com/archives/2010/03/09/jbpm4-and-seam-working-together, for bpmn custom node. I modify jbpm.bpmn.flownodes.xml, added <activity binding="org.loxageek.ppless.action.jbpm.SeamComponentBinding" />.
When deploy I get:
org.jbpm.api.JbpmException:
xml validation error: cvc-id.2: There are multiple occurrences of ID value 'TestSeamProcess'. [line=9 column=32 ]: org.xml.sax.SAXParseException: cvc-id.2: There are multiple occurrences of ID value 'TestSeamProcess'.
xml validation error: cvc-attribute.3: The value 'TestSeamProcess' of attribute 'id' on element 'process' is not valid with respect to its type, 'ID'. [line=9 column=32 ]: org.xml.sax.SAXParseException: cvc-attribute.3: The value 'TestSeamProcess' of attribute 'id' on element 'process' is not valid with respect to its type, 'ID'.Any idea?
-
5. Re: creating user nodes and attributes
mwohlf Nov 28, 2010 4:48 AM (in response to jlgranda81)Hi José,
the exception says your process definition is invalid, specifically the id attribute of your process node in your process definition
-
6. Re: creating user nodes and attributes
jlgranda81 Nov 28, 2010 11:54 PM (in response to mwohlf)Hi Michael, I mix the exception output, sorry.
I try to adapt the code for custom node for jpdl, I create class org.loxageek.ppless.action.jbpm.SeamComponentBinding for support new <seam-component></seam-componet> in BPMN process definitions. When I deploy my xml, I get this exception.
From instructions, I undertand org.loxageek.ppless.action.jbpm.SeamComponentBinding will parser the new node.
the custom activity, i added into process definition sequence
<
seam-component
name
=
"send_request_to_group_leaders"
expression
=
"#{groupAction.sendNotificationToGroupLeaders('/emails/request-to-join-group.xhtml')}"
>
<
transition
to
=
"verify_request"
/>
</
seam-component
>
it's the correct exception output
23:50:03,386 INFO [DeployerManager] errors during deployment of deployment(830001):
xml validation error: cvc-complex-type.2.4.a: Invalid content was found starting with element 'seam-component'. One of '{"http://schema.omg.org/spec/BPMN/2.0":flowElement, "http://schema.omg.org/spec/BPMN/2.0":artifact, "http://schema.omg.org/spec/BPMN/2.0":supports}' is expected. [line=13 column=103 ]: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'seam-component'. One of '{"http://schema.omg.org/spec/BPMN/2.0":flowElement, "http://schema.omg.org/spec/BPMN/2.0":artifact, "http://schema.omg.org/spec/BPMN/2.0":supports}' is expected......
Any idea? I try to integrate jbpm4 and seam.
-
7. Re: creating user nodes and attributes
mwohlf Nov 29, 2010 3:58 AM (in response to jlgranda81)Hi José,
to me it looks like you are using bpmn not jpdl like in the example (http://www.lunatech-research.com/archives/2010/03/09/jbpm4-and-seam-working-together) maybe the bpmn parser uses a schema file to validate the process definition and the jpdl parser doesn't ?