[
https://issues.jboss.org/browse/JBRULES-3355?page=com.atlassian.jira.plug...
]
Edson Tirelli resolved JBRULES-3355.
------------------------------------
Resolution: Done
Problems when writing rhs in Rule API
-------------------------------------
Key: JBRULES-3355
URL:
https://issues.jboss.org/browse/JBRULES-3355
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler
Affects Versions: 5.3.1.Final, 5.4.0.Beta1
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: 5.3.2.Final, 5.4.0.Beta2
Description of problem:
There are several problems when writing rhs of a rule in Rule API:
- if you omit rhs() you 'nullend' on the end of the rule which results in
compile error
- if you put comment in rhs() like rhs("//consequences") you get
'//consequencesend' which result in compile error as well
I think there should be line delimiter behind rhs and that if rhs is omitted it
should result in empty string rather than "null".
KnowledgeDescr descr = DescrFactory.newPackage().name("org.sample")
.newRule().name("results in consequencesend")
.rhs("//consequences")
.end()
.newRule().name("results in nullend")
.lhs()
.pattern("String").end()
.end()
.end()
.getDescr();
--
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