[
https://jira.jboss.org/jira/browse/JBRULES-2243?page=com.atlassian.jira.p...
]
Edson Tirelli commented on JBRULES-2243:
----------------------------------------
After discussing this issue with the development team, we are going down a different path
with a higher level "assembling" file (e.g. the changeset file, ddj file, etc)
that will give instructions to the tools on how to properly assemble kbases from
individual resources and resolve cross-file references.
This work is partly done, but tooling must be improved to take advantage of that. I am
keeping this ticket open so that we keep track of it, but there are no deadlines for this
work right now.
If you need this for runtime purposes, the changeset descriptor already provide that to
some level. Eclipse tooling is not ready though.
Add support to source code assets to reference each other
---------------------------------------------------------
Key: JBRULES-2243
URL:
https://jira.jboss.org/jira/browse/JBRULES-2243
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: drools-api, drools-compiler, drools-core, drools-eclipse
Affects Versions: 5.0.0.FINAL, 5.0.1.FINAL
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: 5.1.0.M2
One asset defined in one DRL should be usable from other DRLs. So we need a way to import
them from one file into another, in a similar way as #includes works in C++ or
"import" in java, etc.
So, if I declare a type in DRL1.drl:
declare XYZ
...
end
I can then use it in rules in DRL2.drl:
uses "DRL1.drl"
rule "ABC"
when
XYZ(...)
then
end
Same for any other assets like functions.
This feature will require proper dependency management to avoid circular dependencies,
classloader issues, etc. Also, the IDE will require update to be able to properly reflect
these situations without raising false errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira