[JBoss JIRA] (DROOLS-2738) Create a simple, structured or compound data type
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2738?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2738:
-------------------------------------
[~karreiro] [~manstis] [~tirelli]
I attached another pass, this time using a drilldown/tree ish kind of approach. The mockup in annotated, so I won't repeat here. Let me know what you think. Thanks!
P.S. Focused on the "complex" data type cause that's the hardest one...
> Create a simple, structured or compound data type
> -------------------------------------------------
>
> Key: DROOLS-2738
> URL: https://issues.jboss.org/browse/DROOLS-2738
> Project: Drools
> Issue Type: Sub-task
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Attachments: customDO-drilldown.pdf
>
>
> We're trying to solve two big issues with this dialog:
> I) the definition of a simple (basic) data type; and
> II) the definition of a structured data type.
> * The first one is kind of easy, we just need to provide to the user an input and a select, in order to capture the name and the type of a simple data type.
> * The second problem is a little bit more difficult. Because the user needs to be able to define complex data types, with nested structures. For example, the user can create a data type called Person with 3 nested fields (they are simple data types) Additionally, a structured data type can have other complex nested data types.
> * Requirement to address situations where we're going to have many levels of nesting and many fields. The user should be able to: a) navigate between levels; b) expand/collapse nested types; c) create complex data structures easily.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2738) Create a simple, structured or compound data type
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2738?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2738:
--------------------------------
Attachment: customDO-drilldown.pdf
> Create a simple, structured or compound data type
> -------------------------------------------------
>
> Key: DROOLS-2738
> URL: https://issues.jboss.org/browse/DROOLS-2738
> Project: Drools
> Issue Type: Sub-task
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Attachments: customDO-drilldown.pdf
>
>
> We're trying to solve two big issues with this dialog:
> I) the definition of a simple (basic) data type; and
> II) the definition of a structured data type.
> * The first one is kind of easy, we just need to provide to the user an input and a select, in order to capture the name and the type of a simple data type.
> * The second problem is a little bit more difficult. Because the user needs to be able to define complex data types, with nested structures. For example, the user can create a data type called Person with 3 nested fields (they are simple data types) Additionally, a structured data type can have other complex nested data types.
> * Requirement to address situations where we're going to have many levels of nesting and many fields. The user should be able to: a) navigate between levels; b) expand/collapse nested types; c) create complex data structures easily.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2738) Create a simple, structured or compound data type
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2738?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2738:
--------------------------------
Description:
We're trying to solve two big issues with this dialog:
I) the definition of a simple (basic) data type; and
II) the definition of a structured data type.
* The first one is kind of easy, we just need to provide to the user an input and a select, in order to capture the name and the type of a simple data type.
* The second problem is a little bit more difficult. Because the user needs to be able to define complex data types, with nested structures. For example, the user can create a data type called Person with 3 nested fields (they are simple data types) Additionally, a structured data type can have other complex nested data types.
* Requirement to address situations where we're going to have many levels of nesting and many fields. The user should be able to: a) navigate between levels; b) expand/collapse nested types; c) create complex data structures easily.
was:
We're trying to solve two big issues with this dialog: I) the definition of a simple (basic) data type; and II) the definition of a structured data type.
The first one is kind of easy, we just need to provide to the user an input and a select, in order to capture the name and the type of a simple data type. Here some examples of four simple data types:
The second problem is a little bit more difficult. Because the user needs to be able to define complex data types, with nested structures. For example, the user can create a data type called Person with 3 nested fields (they are simple data types):
Person
name (Text)
age (Number)
email (Text)
Additionally, a structured data type can have other complex nested data types, like:
Person
name (Text)
age (Number)
email (Text)
address (Address)
street (Text)
city (Text)
country (Text)
The approach that you adopted to solve the scenario above was to express these nested levels using text:
..which is pretty interesting. But, the example that we're handling here has only one level of nesting (Address), and Edson is concerned about situations where we're going to have many levels of nesting and many fields. Something like this:
Person
name (Text)
age (Number)
email (Text)
address (Address)
Something (Something)
field1 (Text)
field2 (Text)
field3 (Text)
field4 (Text)
field5 (Text)
field6 (Text)
field7 (Text)
field8 (Text)
Something (Something)
field1 (Text)
field2 (Text)
field3 (Text)
field4 (Text)
field5 (Text)
field6 (Text)
field7 (Text)
field8 (Text)
Something (Something)
field1 (Text)
field2 (Text)
field3 (Text)
field4 (Text)
field5 (Text)
field6 (Text)
Something (Something)
field1 (Text)
Something (Something)
field1 (Text)
Edson thinks that the user should be able to: a) navigate between levels; b) expand/collapse nested types; c) create complex data structures easily.
That said, we need a different approach to handle this kind of complex structure. Maybe we could adopt the tree view prototypes and improve them, maybe we could use a breadcrumb to navigate between levels, or maybe we can have another idea
> Create a simple, structured or compound data type
> -------------------------------------------------
>
> Key: DROOLS-2738
> URL: https://issues.jboss.org/browse/DROOLS-2738
> Project: Drools
> Issue Type: Sub-task
> Reporter: Liz Clayton
> Assignee: Liz Clayton
>
> We're trying to solve two big issues with this dialog:
> I) the definition of a simple (basic) data type; and
> II) the definition of a structured data type.
> * The first one is kind of easy, we just need to provide to the user an input and a select, in order to capture the name and the type of a simple data type.
> * The second problem is a little bit more difficult. Because the user needs to be able to define complex data types, with nested structures. For example, the user can create a data type called Person with 3 nested fields (they are simple data types) Additionally, a structured data type can have other complex nested data types.
> * Requirement to address situations where we're going to have many levels of nesting and many fields. The user should be able to: a) navigate between levels; b) expand/collapse nested types; c) create complex data structures easily.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[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 edited comment on WFLY-8954 at 7/14/18 1:23 PM:
----------------------------------------------------------------------
HI,
All I can say, is that as far as I can see the issue is not resolved.
So we are keeping all of our local tunnings.
Since I did not have any computer setup anymore to work with wildfly source or eclipselink.
Today I have done the following experiment:
1. Have checked out wildfly source code on branch 10.x with the test
org.jboss.as.test.compat.jpa.eclipselink.wildfly8954.WFLY8954BaseTest
This branch can be obtained from:
git remote -v
origin https://github.com/99sono/wildfly.git (fetch)
2. My local machine looks as follows:
git branch
* WFLY-8954
master
3. I have checked out eclipselink runtime
git remote -v
origin git://git.eclipse.org/gitroot/eclipselink/eclipselink.runtime.git
4. I have built the eclipselink runtime:
ant -f antbuild.xml build-eclipselink-jar
5. Since I mad sure I know what eclipselink library is getting used when running the failing on observes test by logging:
this.getClass().getResource("/org/eclipse/persistence/internal/sessions/EmptyRecord.class");
6. I copy pasted the most recent eclipselink.jar built using the master branch of eclipselink into the module folder of the wildfly using during runtime of the system test
I called this jar locally_built_eclipselink.jar
And I modified the module.xml to point to the locally built eclipselink jar.
7. I edited the pom.xml of system test to disable the task that copies resources on the test module.
Otherwise my changes would be useless since the module.xml and the eclipselink.jar would both be crushed
8. Mvn clean install
The result is no altered:
testSimpleCreateAndLoadEntities(org.jboss.as.test.compat.jpa.eclipselink.wildfly8954.WFLY8954BaseTest) Time elapsed: 2.457 sec <<< FAILURE!
java.lang.AssertionError: The observer bug has been tected. The context is:
EVENT OBSERVED: SomeEntityChangeEvent [oldValue=Initial Address Value. , newValue=IncrementAddressNumber: 1 , someEntityId=10]
lastProcessedEntityAddressBeforeExecutingRefresh: Initial Address Value. lastProcessedEntityAddressAfterExecutingRefresh: IncrementAddressNumber: 1
NOTE: location of eclipselink is: jar:file:/Users/johndoe/Projects/git/wildfly/testsuite/compat/target/modules/org/eclipse/persistence/test/locally_built_eclipselink.jar!/org/eclipse/persistence/internal/sessions/EmptyRecord.class .
at org.junit.Assert.fail(Assert.java:88)
at org.jboss.as.test.compat.jpa.eclipselink.wildfly8954.WFLY8954BaseTest.testSimpleCreateAndLoadEntities(WFLY8954BaseTest.java:148)
You can see from the log above running the mvn clean install that the library I built locally of eclipselink does not bring any changes.
For this reason, I see no option but going forward wit the JIPIAPA change that was provided ina pull request and which is working very well.
NOTE:
We are stil using wildfly 10.1.0.Final for the time being.
I did not do the same experiment using a more recent version of wildfly, since the git branch do this test is well prepared for 10.1.0.Final, and if the fix would be done on the eclipselink code itself and not in the JIPIPA i see no reason why the fix to eclipselink should not be working here as well.
>From my point of view a developer integrating with eclipselink and wildfly, right now, has not alternative other than to patch
jipijapa-eclipselink.jar
On his own. Even if the pull request has been declined...
Kindest regards
was (Author: nuno.godinhomatos):
HI,
All I can say, is that as far as I can see the issue is not resolved.
So we are keeping all of our local tunnings.
Since I did not have any computer setup anymore to work with wildfly source or eclipselink.
Today I have done the following experiment:
1. Have checked out wildfly source code on branch 10.x with the test
org.jboss.as.test.compat.jpa.eclipselink.wildfly8954.WFLY8954BaseTest
This branch can be obtained from:
git remote -v
origin https://github.com/99sono/wildfly.git (fetch)
2. My local machine looks as follows:
git branch
* WFLY-8954
master
3. I have checked out eclipselink runtime
git remote -v
origin git://git.eclipse.org/gitroot/eclipselink/eclipselink.runtime.git
4. I have built the eclipselink runtime:
ant -f antbuild.xml build-eclipselink-jar
5. Since I mad sure I know what eclipselink library is getting used when running the failing on observes test by logging:
this.getClass().getResource("/org/eclipse/persistence/internal/sessions/EmptyRecord.class");
6. I copy pasted the most recent eclipselink.jar built using the master branch of eclipselink into the module folder of the wildfly using during runtime of the system test
I called this jar locally_built_eclipselink.jar
And I modified the module.xml to point to the locally built eclipselink jar.
7. I edited the pom.xml of system test to disable the task that copies resources on the test module.
Otherwise my changes would be useless since the module.xml and the eclipselink.jar would both be crushed
8. Mvn clean install
The result is no altered:
testSimpleCreateAndLoadEntities(org.jboss.as.test.compat.jpa.eclipselink.wildfly8954.WFLY8954BaseTest) Time elapsed: 2.457 sec <<< FAILURE!
java.lang.AssertionError: The observer bug has been tected. The context is:
EVENT OBSERVED: SomeEntityChangeEvent [oldValue=Initial Address Value. , newValue=IncrementAddressNumber: 1 , someEntityId=10]
lastProcessedEntityAddressBeforeExecutingRefresh: Initial Address Value. lastProcessedEntityAddressAfterExecutingRefresh: IncrementAddressNumber: 1
NOTE: location of eclipselink is: jar:file:/Users/johndoe/Projects/git/wildfly/testsuite/compat/target/modules/org/eclipse/persistence/test/locally_built_eclipselink.jar!/org/eclipse/persistence/internal/sessions/EmptyRecord.class .
at org.junit.Assert.fail(Assert.java:88)
at org.jboss.as.test.compat.jpa.eclipselink.wildfly8954.WFLY8954BaseTest.testSimpleCreateAndLoadEntities(WFLY8954BaseTest.java:148)
You can see from the log above running the mvn clean install that the library I built locally of eclipselink does not bring any changes.
For this reason, I see no option but going forward wit the JIPIAPA change that was provided ina pull request and which is working very well.
NOTE:
We are stil using wildfly 10.1.0.Final for the time being.
I did not do the same experiment using a more recent version of wildfly, since the git branch do this test is well prepared for 10.1.0.Final, and if the fix would be done on the eclipselink code itself and not in the JIPIPA i see no reason why the fix to eclipselink should not be working here as well.
>From my point of view a developer integrating with eclipselink and wildfly, right now, has not alternative other than to patch
jipijapa-eclipselink.jar
On his own.
Kindest regards
> 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
>
> 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.5.0#75005)
8 years
[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:
---------------------------------------------
HI,
All I can say, is that as far as I can see the issue is not resolved.
So we are keeping all of our local tunnings.
Since I did not have any computer setup anymore to work with wildfly source or eclipselink.
Today I have done the following experiment:
1. Have checked out wildfly source code on branch 10.x with the test
org.jboss.as.test.compat.jpa.eclipselink.wildfly8954.WFLY8954BaseTest
This branch can be obtained from:
git remote -v
origin https://github.com/99sono/wildfly.git (fetch)
2. My local machine looks as follows:
git branch
* WFLY-8954
master
3. I have checked out eclipselink runtime
git remote -v
origin git://git.eclipse.org/gitroot/eclipselink/eclipselink.runtime.git
4. I have built the eclipselink runtime:
ant -f antbuild.xml build-eclipselink-jar
5. Since I mad sure I know what eclipselink library is getting used when running the failing on observes test by logging:
this.getClass().getResource("/org/eclipse/persistence/internal/sessions/EmptyRecord.class");
6. I copy pasted the most recent eclipselink.jar built using the master branch of eclipselink into the module folder of the wildfly using during runtime of the system test
I called this jar locally_built_eclipselink.jar
And I modified the module.xml to point to the locally built eclipselink jar.
7. I edited the pom.xml of system test to disable the task that copies resources on the test module.
Otherwise my changes would be useless since the module.xml and the eclipselink.jar would both be crushed
8. Mvn clean install
The result is no altered:
testSimpleCreateAndLoadEntities(org.jboss.as.test.compat.jpa.eclipselink.wildfly8954.WFLY8954BaseTest) Time elapsed: 2.457 sec <<< FAILURE!
java.lang.AssertionError: The observer bug has been tected. The context is:
EVENT OBSERVED: SomeEntityChangeEvent [oldValue=Initial Address Value. , newValue=IncrementAddressNumber: 1 , someEntityId=10]
lastProcessedEntityAddressBeforeExecutingRefresh: Initial Address Value. lastProcessedEntityAddressAfterExecutingRefresh: IncrementAddressNumber: 1
NOTE: location of eclipselink is: jar:file:/Users/johndoe/Projects/git/wildfly/testsuite/compat/target/modules/org/eclipse/persistence/test/locally_built_eclipselink.jar!/org/eclipse/persistence/internal/sessions/EmptyRecord.class .
at org.junit.Assert.fail(Assert.java:88)
at org.jboss.as.test.compat.jpa.eclipselink.wildfly8954.WFLY8954BaseTest.testSimpleCreateAndLoadEntities(WFLY8954BaseTest.java:148)
You can see from the log above running the mvn clean install that the library I built locally of eclipselink does not bring any changes.
For this reason, I see no option but going forward wit the JIPIAPA change that was provided ina pull request and which is working very well.
NOTE:
We are stil using wildfly 10.1.0.Final for the time being.
I did not do the same experiment using a more recent version of wildfly, since the git branch do this test is well prepared for 10.1.0.Final, and if the fix would be done on the eclipselink code itself and not in the JIPIPA i see no reason why the fix to eclipselink should not be working here as well.
>From my point of view a developer integrating with eclipselink and wildfly, right now, has not alternative other than to patch
jipijapa-eclipselink.jar
On his own.
Kindest regards
> 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
>
> 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.5.0#75005)
8 years