[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity
by NUNO GODINHO DE MATOS (Jira)
[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ]
NUNO GODINHO DE MATOS commented on WFLY-8954:
---------------------------------------------
Last time I checked the lastest version of eclipselink the oncussess bug still stood.
So in Widlfly13.0.Final which is the version we currently use, we still need to apply the patch proposed above to work-around the issue.
I am not sure, but I have the impression that It would be good if the wildfly base code itself would get patched, since we have that just by tweaking the wildfly JAR to integrate with eclipselink the issue can be resolved.
This would have the benefit that wildfly with eclipselink integration would not be patched just for very future version of eclipselink...
We will continue apply the same patch over and over again, whenever we move wildfly version forward.
Thanks
> Wildfly 10 with eclipselink Onscucess observer gets stale entity
> ----------------------------------------------------------------
>
> Key: WFLY-8954
> URL: https://issues.jboss.org/browse/WFLY-8954
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Reporter: NUNO GODINHO DE MATOS
> Assignee: Scott Marlow
> Priority: Major
>
> Hi,
> In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink.
> When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success.
> Then the observer will be working with stale entities that do not reflect the modifications done to the entity.
> A sample application for this issue is available in:
> https://github.com/99sono/wildfly10-observe-on-success-stale-entity
> The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation.
> Many thanks for taking a look.
> Kindest regards.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-4788) newline within the rule cell of spreadsheet is included as a value incorrectly
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-4788?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-4788:
--------------------------------
Sprint: 2019 Week 47-49 (from Nov 18)
> newline within the rule cell of spreadsheet is included as a value incorrectly
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4788
> URL: https://issues.jboss.org/browse/DROOLS-4788
> Project: Drools
> Issue Type: Bug
> Components: decision tables
> Affects Versions: 7.26.0.Final
> Environment: - spreadsheet
> - 7.26.0.Final and later
> Reporter: Hiroko Miura
> Assignee: Mario Fusco
> Priority: Major
> Labels: support
> Attachments: newlineInConditionCellTest.zip
>
>
> When there is new line in rule cell with specific condition, new line('\n') is included as a value.
> Here is generated problematic DRL.
> {noformat}
> rule "newlineInCell_11"
> when
> m:Message(map["Key1"] == var1,
> map["\nKey2"] == var2) <== HERE
> then
> System.out.println(m.getMessage());
> m.setMessage("Goodbye cruel world");
> m.setStatus(Message.GOODBYE);
> end
> {noformat}
> This does happen with 7.26.0.Final(RHDM7.5.0), but not with 7.23.0.Final(7.4.x).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-2750) [DMN Designer] Default cell symbols
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2750?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2750:
--------------------------------
Description:
As a citizen developer, I want to build my decision logic with as small effort as possible. Especially I want to build the *valid* expressions with minimal interaction with the designer. For this reason the designer should fill in default values/symbols into cells where possible. This should help with DMN designer getting started experience.
In this epic we should discuss where is possible to fill some default values/symbols into expression cells.
h3. Context
I think no appropriate default value exists. Maybe with exception of the last row?
h3. Literal Expressions
My proposal would be:
- empty cell, if it is valid value for literal expression cell, if not
- value according to the column data type, 0 for number, today for date ...
h3. Decision table
- symbol *-* due to trisotext samples
h3. Function
Really not sure
h3. Relation
Really not sure
h3. Invocation
Really not sure
[~manstis] [~tirelli] [~tari_manga] could you please put your thoughts into comments? I filed this epic to follow agile process. Not saying something from description will happen. However if we will agree on some default values we can then file separate tasks for this epic. I f we agree it is not good idea, we will close the epic.
h2. Manual Acceptance test
Note: Proposed after discussion in this jira
- Autogonerated top level decision table, input is structure (/)
- Nested decision table, for example as context entry (/)
- Adding columns/rows (/)
was:
As a citizen developer, I want to build my decision logic with as small effort as possible. Especially I want to build the *valid* expressions with minimal interaction with the designer. For this reason the designer should fill in default values/symbols into cells where possible. This should help with DMN designer getting started experience.
In this epic we should discuss where is possible to fill some default values/symbols into expression cells.
h3. Context
I think no appropriate default value exists. Maybe with exception of the last row?
h3. Literal Expressions
My proposal would be:
- empty cell, if it is valid value for literal expression cell, if not
- value according to the column data type, 0 for number, today for date ...
h3. Decision table
- symbol *-* due to trisotext samples
h3. Function
Really not sure
h3. Relation
Really not sure
h3. Invocation
Really not sure
[~manstis] [~tirelli] [~tari_manga] could you please put your thoughts into comments? I filed this epic to follow agile process. Not saying something from description will happen. However if we will agree on some default values we can then file separate tasks for this epic. I f we agree it is not good idea, we will close the epic.
h2. Manual Acceptance test
Note: Proposed after discussion in this jira
- Autogonerated top level decision table, input is structure
- Nested decision table, for example as context entry
> [DMN Designer] Default cell symbols
> -----------------------------------
>
> Key: DROOLS-2750
> URL: https://issues.jboss.org/browse/DROOLS-2750
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
>
> As a citizen developer, I want to build my decision logic with as small effort as possible. Especially I want to build the *valid* expressions with minimal interaction with the designer. For this reason the designer should fill in default values/symbols into cells where possible. This should help with DMN designer getting started experience.
> In this epic we should discuss where is possible to fill some default values/symbols into expression cells.
> h3. Context
> I think no appropriate default value exists. Maybe with exception of the last row?
> h3. Literal Expressions
> My proposal would be:
> - empty cell, if it is valid value for literal expression cell, if not
> - value according to the column data type, 0 for number, today for date ...
> h3. Decision table
> - symbol *-* due to trisotext samples
> h3. Function
> Really not sure
> h3. Relation
> Really not sure
> h3. Invocation
> Really not sure
> [~manstis] [~tirelli] [~tari_manga] could you please put your thoughts into comments? I filed this epic to follow agile process. Not saying something from description will happen. However if we will agree on some default values we can then file separate tasks for this epic. I f we agree it is not good idea, we will close the epic.
> h2. Manual Acceptance test
> Note: Proposed after discussion in this jira
> - Autogonerated top level decision table, input is structure (/)
> - Nested decision table, for example as context entry (/)
> - Adding columns/rows (/)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-2750) [DMN Designer] Default cell symbols
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2750?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2750:
--------------------------------
Description:
As a citizen developer, I want to build my decision logic with as small effort as possible. Especially I want to build the *valid* expressions with minimal interaction with the designer. For this reason the designer should fill in default values/symbols into cells where possible. This should help with DMN designer getting started experience.
In this epic we should discuss where is possible to fill some default values/symbols into expression cells.
h3. Context
I think no appropriate default value exists. Maybe with exception of the last row?
h3. Literal Expressions
My proposal would be:
- empty cell, if it is valid value for literal expression cell, if not
- value according to the column data type, 0 for number, today for date ...
h3. Decision table
- symbol *-* due to trisotext samples
h3. Function
Really not sure
h3. Relation
Really not sure
h3. Invocation
Really not sure
[~manstis] [~tirelli] [~tari_manga] could you please put your thoughts into comments? I filed this epic to follow agile process. Not saying something from description will happen. However if we will agree on some default values we can then file separate tasks for this epic. I f we agree it is not good idea, we will close the epic.
h2. Manual Acceptance test
Note: Proposed after discussion in this jira
- Autogonerated top level decision table, input is structure
- Nested decision table, for example as context entry
was:
As a citizen developer, I want to build my decision logic with as small effort as possible. Especially I want to build the *valid* expressions with minimal interaction with the designer. For this reason the designer should fill in default values/symbols into cells where possible. This should help with DMN designer getting started experience.
In this epic we should discuss where is possible to fill some default values/symbols into expression cells.
h3. Context
I think no appropriate default value exists. Maybe with exception of the last row?
h3. Literal Expressions
My proposal would be:
- empty cell, if it is valid value for literal expression cell, if not
- value according to the column data type, 0 for number, today for date ...
h3. Decision table
- symbol *-* due to trisotext samples
h3. Function
Really not sure
h3. Relation
Really not sure
h3. Invocation
Really not sure
[~manstis] [~tirelli] [~tari_manga] could you please put your thoughts into comments? I filed this epic to follow agile process. Not saying something from description will happen. However if we will agree on some default values we can then file separate tasks for this epic. I f we agree it is not good idea, we will close the epic.
> [DMN Designer] Default cell symbols
> -----------------------------------
>
> Key: DROOLS-2750
> URL: https://issues.jboss.org/browse/DROOLS-2750
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
>
> As a citizen developer, I want to build my decision logic with as small effort as possible. Especially I want to build the *valid* expressions with minimal interaction with the designer. For this reason the designer should fill in default values/symbols into cells where possible. This should help with DMN designer getting started experience.
> In this epic we should discuss where is possible to fill some default values/symbols into expression cells.
> h3. Context
> I think no appropriate default value exists. Maybe with exception of the last row?
> h3. Literal Expressions
> My proposal would be:
> - empty cell, if it is valid value for literal expression cell, if not
> - value according to the column data type, 0 for number, today for date ...
> h3. Decision table
> - symbol *-* due to trisotext samples
> h3. Function
> Really not sure
> h3. Relation
> Really not sure
> h3. Invocation
> Really not sure
> [~manstis] [~tirelli] [~tari_manga] could you please put your thoughts into comments? I filed this epic to follow agile process. Not saying something from description will happen. However if we will agree on some default values we can then file separate tasks for this epic. I f we agree it is not good idea, we will close the epic.
> h2. Manual Acceptance test
> Note: Proposed after discussion in this jira
> - Autogonerated top level decision table, input is structure
> - Nested decision table, for example as context entry
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-4336) [DMN Designer] Text Annotation SVG and glyph needs revision
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4336?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4336:
--------------------------------
Description:
The SVG and glyph used for {{TextAnnotations}} needs revision.
The horizontal lines are too long.
h3. Manual Acceptance test
- Check changes Firefox (/)
- Check changes Chrome (/)
- Put long line text (/)
- Resize (/)
- Move (/)
was:
The SVG and glyph used for {{TextAnnotations}} needs revision.
The horizontal lines are too long.
h3. Manual Acceptance test
- Check changes Firefox
- Check changes Chrome (/)
- Put long line text (/)
- Resize (/)
- Move (/)
> [DMN Designer] Text Annotation SVG and glyph needs revision
> -----------------------------------------------------------
>
> Key: DROOLS-4336
> URL: https://issues.jboss.org/browse/DROOLS-4336
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.24.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
> Attachments: DMN-text-annotation.png, DMN12-Specification.png
>
>
> The SVG and glyph used for {{TextAnnotations}} needs revision.
> The horizontal lines are too long.
> h3. Manual Acceptance test
> - Check changes Firefox (/)
> - Check changes Chrome (/)
> - Put long line text (/)
> - Resize (/)
> - Move (/)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-4336) [DMN Designer] Text Annotation SVG and glyph needs revision
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4336?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4336:
--------------------------------
Description:
The SVG and glyph used for {{TextAnnotations}} needs revision.
The horizontal lines are too long.
h3. Manual Acceptance test
- Check changes Firefox
- Check changes Chrome (/)
- Put long line text (/)
- Resize (/)
- Move (/)
was:
The SVG and glyph used for {{TextAnnotations}} needs revision.
The horizontal lines are too long.
h3. Manual Acceptance test
- Check changes Firefox
- Check changes Chrome
- Put multilne text
- Put long line text
- Resize
- Move
> [DMN Designer] Text Annotation SVG and glyph needs revision
> -----------------------------------------------------------
>
> Key: DROOLS-4336
> URL: https://issues.jboss.org/browse/DROOLS-4336
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.24.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
> Attachments: DMN-text-annotation.png, DMN12-Specification.png
>
>
> The SVG and glyph used for {{TextAnnotations}} needs revision.
> The horizontal lines are too long.
> h3. Manual Acceptance test
> - Check changes Firefox
> - Check changes Chrome (/)
> - Put long line text (/)
> - Resize (/)
> - Move (/)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-4336) [DMN Designer] Text Annotation SVG and glyph needs revision
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4336?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4336:
--------------------------------
Description:
The SVG and glyph used for {{TextAnnotations}} needs revision.
The horizontal lines are too long.
h3. Manual Acceptance test
- Check changes Firefox
- Check changes Chrome
- Put multilne text
- Put long line text
- Resize
was:
The SVG and glyph used for {{TextAnnotations}} needs revision.
The horizontal lines are too long.
> [DMN Designer] Text Annotation SVG and glyph needs revision
> -----------------------------------------------------------
>
> Key: DROOLS-4336
> URL: https://issues.jboss.org/browse/DROOLS-4336
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.24.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
> Attachments: DMN-text-annotation.png, DMN12-Specification.png
>
>
> The SVG and glyph used for {{TextAnnotations}} needs revision.
> The horizontal lines are too long.
> h3. Manual Acceptance test
> - Check changes Firefox
> - Check changes Chrome
> - Put multilne text
> - Put long line text
> - Resize
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-4336) [DMN Designer] Text Annotation SVG and glyph needs revision
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4336?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4336:
--------------------------------
Description:
The SVG and glyph used for {{TextAnnotations}} needs revision.
The horizontal lines are too long.
h3. Manual Acceptance test
- Check changes Firefox
- Check changes Chrome
- Put multilne text
- Put long line text
- Resize
- Move
was:
The SVG and glyph used for {{TextAnnotations}} needs revision.
The horizontal lines are too long.
h3. Manual Acceptance test
- Check changes Firefox
- Check changes Chrome
- Put multilne text
- Put long line text
- Resize
> [DMN Designer] Text Annotation SVG and glyph needs revision
> -----------------------------------------------------------
>
> Key: DROOLS-4336
> URL: https://issues.jboss.org/browse/DROOLS-4336
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.24.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
> Attachments: DMN-text-annotation.png, DMN12-Specification.png
>
>
> The SVG and glyph used for {{TextAnnotations}} needs revision.
> The horizontal lines are too long.
> h3. Manual Acceptance test
> - Check changes Firefox
> - Check changes Chrome
> - Put multilne text
> - Put long line text
> - Resize
> - Move
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months