[switchyard-issues] [JBoss JIRA] (SWITCHYARD-842) processDefinition cannot be null
David Ward (JIRA)
jira-events at lists.jboss.org
Wed Jun 6 08:56:18 EDT 2012
David Ward created SWITCHYARD-842:
-------------------------------------
Summary: processDefinition cannot be null
Key: SWITCHYARD-842
URL: https://issues.jboss.org/browse/SWITCHYARD-842
Project: SwitchYard
Issue Type: Bug
Components: component-bpm
Affects Versions: 0.4
Reporter: David Ward
Assignee: David Ward
Priority: Blocker
Fix For: 0.5
Doing this:
<bpm:implementation.bpm processId="com.foo.bar">
<resource location="/META-INF/ChangeSet.xml" type="CHANGE_SET"/>
</bpm:implementation.bpm>
results in this:
Failed to execute goal org.switchyard:switchyard-plugin:0.5.0-SNAPSHOT:configure (default) on project FooBar: Model [org.switchyard.config.model.switchyard.v1.V1SwitchYardModel] is invalid: cvc-complex-type.4: Attribute 'processDefinition' must appear on element 'bpm:implementation.bpm'. -> [Help 1]
[ERROR]
Fixing this is a bit more work than just changing the schema in bpm-v1.xsd so that the processDefinition is 'optional' instead of 'required'. The DroolsBPMExchangeHandler appears to assume it to never be null as well.
The reason we should not have to set the processDefinition attribute is that it should be able to be defined in the change set and gotten from Guvnor too, not just the "other" resources.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the switchyard-issues
mailing list