what if you rename it to UserName everywhere?
Nope, same result.
do you get an error while deploying? If so does it have somerthing to do with an xsd? If so try removing the full header in the process and just leave a header without references to an xsd. Could be a namespace issue.
That worked! Its a bug though. Not sure how to file a JIRA issue.
Not sure how to file a JIRA issue.
Log in to Jira using the same account you use for the forums and click on 'create new issue'.
Do I have official blessing to file a JIRA issue for this?
I couldn't find this bug in the jira, and it is causing me major grief. Can anyone confirm that it has been filed as a bug?
Also, I looked at the schema and don't really understand what is causing this error.
The matching wildcard is strict, but no declaration can be found for element 'xxxxxx'
where xxxxxx is the field name in my TaskAssignmentHandler class.
Can anyone comment? Thanx.
It seems that the schema for "assignment" should be ...
<xs:element name="assignment"> <xs:annotation> <xs:documentation>Controls the behavior of assigning a task to an identity.</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>The content of the assignment element can be used as configuration information for your custom assignment handler implementations. This allows the creation of reusable delegation classes.</xs:documentation> </xs:annotation> </xs:any> </xs:sequence> <xs:attribute name="class" type="xs:string" use="required"> <xs:annotation> <xs:documentation>The fully qualified class name of an implementation of org.jbpm.taskmgmt.def.AssignmentHandler.</xs:documentation> </xs:annotation> </xs:attribute> <xs:attribute name="config-type" type="configType" use="optional"> <xs:annotation> <xs:documentation>Specifies how the assignment handler object should be constructed and how the content of this element should be used as configuration information for that object.</xs:documentation> </xs:annotation> </xs:attribute> <xs:attribute name="expression" type="xs:string" use="optional"/> </xs:complexType> </xs:element>
Would it be possible for this change to be made in the offical schema file at jbpm.org? Thanx.
Finally found this in jira:
It claims to be fixed in 3.1a, but it apparently has not made it back to 3.0.x
Can the correct xsd be posted your web site (as specified in the processdefinition xml) ?? Thanx.
We are currently working hard on 3.1. After that release we will fix some things for 3.0x again. I suggest for the time being, turn xsd validation of (by changing it in the header) or refer to a local, corrected copy of the xsd