[JBoss JIRA] (DROOLS-2733) Support MVEL Dialect using custom inline accumulate code with external declarations in the executable model
by Luca Molteni (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2733?page=com.atlassian.jira.plugi... ]
Luca Molteni updated DROOLS-2733:
---------------------------------
Description:
The executable model doesn't support custom inline accumulate code that uses external declarations such as
{code:java}
String str = "import " + Person.class.getCanonicalName() + ";\n" +
"rule R dialect \"mvel\" when\n" +
" String( $l : length )" +
" $sum : Integer() from accumulate (\n" +
" Person( age > 18, $age : age ), init( int sum = 0 * $l; ), action( sum += $age; ), reverse( sum -= $age; ), result( sum )\n" +
" )" +
"then\n" +
" insert($sum);\n" +
"end";
{code}
(Notice that in the init we multiply the sum value with the length of string)
But it can support such style using the "classic" generation of accumulate classes which gets compiled among the executable model and instantiate during the execution of the DSL.
This mechanism is broken with the MVEL dialect, as we don't have such generated classes.
Probably what we should do instead is putting MVEL expressions in the DSL directly such as
{code:java}
accumulateScript("initCode", "accCode", "reverseCode");
{code}
and then during interpretation create a new MVEL context and execute the accumulate in memory
was:
The executable model doesn't support custom inline accumulate code that uses external declarations such as
{code:java}
String str = "import " + Person.class.getCanonicalName() + ";\n" +
"rule R when\n" +
" String( $l : length )" +
" $sum : Integer() from accumulate (\n" +
" Person( age > 18, $age : age ), init( int sum = 0 * $l; ), action( sum += $age; ), reverse( sum -= $age; ), result( sum )\n" +
" )" +
"then\n" +
" insert($sum);\n" +
"end";
{code}
(Notice that in the init we multiply the sum value with the length of string)
But it can support such style using the "classic" generation of accumulate classes which gets compiled among the executable model and instantiate during the execution of the DSL.
This mechanism is broken with the MVEL dialect, as we don't have such generated classes.
Probably what we should do instead is putting MVEL expressions in the DSL directly such as
{code:java}
accumulateScript("initCode", "accCode", "reverseCode");
{code}
and then during interpretation create a new MVEL context and execute the accumulate in memory
> Support MVEL Dialect using custom inline accumulate code with external declarations in the executable model
> -----------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2733
> URL: https://issues.jboss.org/browse/DROOLS-2733
> Project: Drools
> Issue Type: Feature Request
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Optional
>
> The executable model doesn't support custom inline accumulate code that uses external declarations such as
> {code:java}
> String str = "import " + Person.class.getCanonicalName() + ";\n" +
> "rule R dialect \"mvel\" when\n" +
> " String( $l : length )" +
> " $sum : Integer() from accumulate (\n" +
> " Person( age > 18, $age : age ), init( int sum = 0 * $l; ), action( sum += $age; ), reverse( sum -= $age; ), result( sum )\n" +
> " )" +
> "then\n" +
> " insert($sum);\n" +
> "end";
> {code}
> (Notice that in the init we multiply the sum value with the length of string)
> But it can support such style using the "classic" generation of accumulate classes which gets compiled among the executable model and instantiate during the execution of the DSL.
> This mechanism is broken with the MVEL dialect, as we don't have such generated classes.
> Probably what we should do instead is putting MVEL expressions in the DSL directly such as
> {code:java}
> accumulateScript("initCode", "accCode", "reverseCode");
> {code}
> and then during interpretation create a new MVEL context and execute the accumulate in memory
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2733) Support MVEL Dialect using custom inline accumulate code with external declarations in the executable model
by Luca Molteni (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2733?page=com.atlassian.jira.plugi... ]
Luca Molteni updated DROOLS-2733:
---------------------------------
Description:
The executable model doesn't support custom inline accumulate code that uses external declarations such as
{code:java}
String str = "import " + Person.class.getCanonicalName() + ";\n" +
"rule R when\n" +
" String( $l : length )" +
" $sum : Integer() from accumulate (\n" +
" Person( age > 18, $age : age ), init( int sum = 0 * $l; ), action( sum += $age; ), reverse( sum -= $age; ), result( sum )\n" +
" )" +
"then\n" +
" insert($sum);\n" +
"end";
{code}
(Notice that in the init we multiply the sum value with the length of string)
But it can support such style using the "classic" generation of accumulate classes which gets compiled among the executable model and instantiate during the execution of the DSL.
This mechanism is broken with the MVEL dialect, as we don't have such generated classes.
Probably what we should do instead is putting MVEL expressions in the DSL directly such as
{code:java}
accumulateScript("initCode", "accCode", "reverseCode");
{code}
and then during interpretation create a new MVEL context and execute the accumulate in memory
was:
The executable model doesn't support custom inline accumulate code that uses external declarations such as
` String str = "import " + Person.class.getCanonicalName() + ";\n" +
"rule R when\n" +
" String( $l : length )" +
" $sum : Integer() from accumulate (\n" +
" Person( age > 18, $age : age ), init( int sum = 0 * $l; ), action( sum += $age; ), reverse( sum -= $age; ), result( sum )\n" +
" )" +
"then\n" +
" insert($sum);\n" +
"end";
`
(Notice that in the init we multiply the sum value with the length of string)
But it can support such style using the "classic" generation of accumulate classes which gets compiled among the executable model and instantiate during the execution of the DSL.
This mechanism is broken with the MVEL dialect, as we don't have such generated classes.
Probably what we should do instead is putting MVEL expressions in the DSL directly such as
`accumulateScript("initCode", "accCode", "reverseCode");`
and then during interpretation create a new MVEL context and execute the accumulate in memory
> Support MVEL Dialect using custom inline accumulate code with external declarations in the executable model
> -----------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2733
> URL: https://issues.jboss.org/browse/DROOLS-2733
> Project: Drools
> Issue Type: Feature Request
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Optional
>
> The executable model doesn't support custom inline accumulate code that uses external declarations such as
> {code:java}
> String str = "import " + Person.class.getCanonicalName() + ";\n" +
> "rule R when\n" +
> " String( $l : length )" +
> " $sum : Integer() from accumulate (\n" +
> " Person( age > 18, $age : age ), init( int sum = 0 * $l; ), action( sum += $age; ), reverse( sum -= $age; ), result( sum )\n" +
> " )" +
> "then\n" +
> " insert($sum);\n" +
> "end";
> {code}
> (Notice that in the init we multiply the sum value with the length of string)
> But it can support such style using the "classic" generation of accumulate classes which gets compiled among the executable model and instantiate during the execution of the DSL.
> This mechanism is broken with the MVEL dialect, as we don't have such generated classes.
> Probably what we should do instead is putting MVEL expressions in the DSL directly such as
> {code:java}
> accumulateScript("initCode", "accCode", "reverseCode");
> {code}
> and then during interpretation create a new MVEL context and execute the accumulate in memory
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2733) Support MVEL Dialect using custom inline accumulate code with external declarations in the executable model
by Luca Molteni (JIRA)
Luca Molteni created DROOLS-2733:
------------------------------------
Summary: Support MVEL Dialect using custom inline accumulate code with external declarations in the executable model
Key: DROOLS-2733
URL: https://issues.jboss.org/browse/DROOLS-2733
Project: Drools
Issue Type: Feature Request
Reporter: Luca Molteni
Assignee: Luca Molteni
Priority: Optional
The executable model doesn't support custom inline accumulate code that uses external declarations such as
` String str = "import " + Person.class.getCanonicalName() + ";\n" +
"rule R when\n" +
" String( $l : length )" +
" $sum : Integer() from accumulate (\n" +
" Person( age > 18, $age : age ), init( int sum = 0 * $l; ), action( sum += $age; ), reverse( sum -= $age; ), result( sum )\n" +
" )" +
"then\n" +
" insert($sum);\n" +
"end";
`
(Notice that in the init we multiply the sum value with the length of string)
But it can support such style using the "classic" generation of accumulate classes which gets compiled among the executable model and instantiate during the execution of the DSL.
This mechanism is broken with the MVEL dialect, as we don't have such generated classes.
Probably what we should do instead is putting MVEL expressions in the DSL directly such as
`accumulateScript("initCode", "accCode", "reverseCode");`
and then during interpretation create a new MVEL context and execute the accumulate in memory
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2652) [DMN Designer] Different icons for different connector types
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2652?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2652:
--------------------------------
Description:
The toolbox shows icons for the different connection types available from a given node.
At the moment they are all the same icon and it is difficult to know which toolbox icon represents which connection type. Until https://issues.jboss.org/browse/DROOLS-1944 a short-term fix is to simply ensure each connection type has an icon more correctly representing its type.
h3. Manual Acceptance test
Each node type has appropriate connector icons in the context menu (/)
was:
The toolbox shows icons for the different connection types available from a given node.
At the moment they are all the same icon and it is difficult to know which toolbox icon represents which connection type. Until https://issues.jboss.org/browse/DROOLS-1944 a short-term fix is to simply ensure each connection type has an icon more correctly representing its type.
h3. Manual Acceptance test
Each node type has appropriate connector icons in the context menu
> [DMN Designer] Different icons for different connector types
> ------------------------------------------------------------
>
> Key: DROOLS-2652
> URL: https://issues.jboss.org/browse/DROOLS-2652
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Attachments: DROOLS-2652 (toolbox icons).png, ProcessCanvasInteractionsB2.png
>
>
> The toolbox shows icons for the different connection types available from a given node.
> At the moment they are all the same icon and it is difficult to know which toolbox icon represents which connection type. Until https://issues.jboss.org/browse/DROOLS-1944 a short-term fix is to simply ensure each connection type has an icon more correctly representing its type.
> h3. Manual Acceptance test
> Each node type has appropriate connector icons in the context menu (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10541) allow user to easily override the transaction node identifier
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-10541?page=com.atlassian.jira.plugin... ]
Tom Jenkinson updated WFLY-10541:
---------------------------------
Description:
Add
{code}
node-identifier="${jboss.tx.node.id:1}
{code}
to the default WF Config files.
Allows a user to then set -Djboss.tx.node.id to something like a pod name during startup in a script
IMPORTANT: The ID must be globally unique still so scenarios where there is more than one process on this box will need to use something to ensure there is an identifier that is unique
was:
Add
{code}
node-identifier="${jboss.tx.node.id:1}
{code}
to the default WF Config files.
Allows a user to then set -Djboss.tx.node.id to something like a pod name during startup in a script
> allow user to easily override the transaction node identifier
> -------------------------------------------------------------
>
> Key: WFLY-10541
> URL: https://issues.jboss.org/browse/WFLY-10541
> Project: WildFly
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 13.0.0.Final
> Reporter: Brad Maxwell
> Assignee: Tom Jenkinson
>
> Add
> {code}
> node-identifier="${jboss.tx.node.id:1}
> {code}
> to the default WF Config files.
> Allows a user to then set -Djboss.tx.node.id to something like a pod name during startup in a script
> IMPORTANT: The ID must be globally unique still so scenarios where there is more than one process on this box will need to use something to ensure there is an identifier that is unique
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years