This content has been marked as final.
Show 4 replies
-
1. Re: Could not parse knowledge - xxx cannot be resolved to a type
tsurdilovic Dec 4, 2012 12:23 PM (in response to tlucz)Could you provide reproducible test cast for this? Your model jars and whole bpmn2 would help. Are you executing this in console or some custom code?
-
2. Re: Could not parse knowledge - xxx cannot be resolved to a type
swiderski.maciej Dec 5, 2012 2:46 AM (in response to tlucz)try declaring fqcn in itemDefinition structureRef attribute
HTH
-
3. Re: Could not parse knowledge - xxx cannot be resolved to a type
tlucz Dec 5, 2012 3:36 AM (in response to swiderski.maciej)Hi Maciej,
It works that way, thanks!
The strange thing for me is when I don't use Java in conditionExpression it works without fqcn e.g:
<itemDefinition id="_companyItem" structureRef="VisitorCompanyTO" />
<conditionExpression xsi:type="tFormalExpression" >company.company.id!=null</conditionExpression>
br,
Tadeusz
-
4. Re: Could not parse knowledge - xxx cannot be resolved to a type
swiderski.maciej Dec 5, 2012 3:40 AM (in response to tlucz)I think it could be due to java compiler is more strict than mvel one.
Cheers