[
https://issues.jboss.org/browse/DROOLS-1477?page=com.atlassian.jira.plugi...
]
Alexandros Koufoudakis updated DROOLS-1477:
-------------------------------------------
Description:
To use extension elements inside inputData elements in order to provide “external”
information: GEO location, time and location tracking of a decision making (when and were
specific decision was taken). This is the primary scope of the use.
In case extension element represents a complex type customer prefers to get back an
instance of the complex type, assuming the complex type is defined as a class by the
development team on the customer side. However, the customer also understands that it can
be more complex and considers the possibility to get the complex type as an XML snippet.
The parsing and turning the XML snippet into the complex type, defined by the customer.
The possibility of getting the list of extension elements is expected from other DMN
elements, which extend from DMNElement, according to the DMN specification and meta model
diagram by OMG. In other words, the usage of extension elements is not limited to be a
part of input data elements only.
The client is not expecting “authoring” of the extension elements.
Since extension elements are a part of DMN specification, this is an attempt to make it
possible for drools to register custom extension elements in a generic way.
was:Currently, the extension elements are disregarded. As I'm working in one of the
projects, which uses Drools 7 beta release and relies on extension elements, I would like
to add this feature and to try to implement it.
DMN Extension Elements
----------------------
Key: DROOLS-1477
URL:
https://issues.jboss.org/browse/DROOLS-1477
Project: Drools
Issue Type: Feature Request
Components: dmn engine
Reporter: Alexandros Koufoudakis
Assignee: Alexandros Koufoudakis
To use extension elements inside inputData elements in order to provide “external”
information: GEO location, time and location tracking of a decision making (when and were
specific decision was taken). This is the primary scope of the use.
In case extension element represents a complex type customer prefers to get back an
instance of the complex type, assuming the complex type is defined as a class by the
development team on the customer side. However, the customer also understands that it can
be more complex and considers the possibility to get the complex type as an XML snippet.
The parsing and turning the XML snippet into the complex type, defined by the customer.
The possibility of getting the list of extension elements is expected from other DMN
elements, which extend from DMNElement, according to the DMN specification and meta model
diagram by OMG. In other words, the usage of extension elements is not limited to be a
part of input data elements only.
The client is not expecting “authoring” of the extension elements.
Since extension elements are a part of DMN specification, this is an attempt to make it
possible for drools to register custom extension elements in a generic way.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)