[JBoss JIRA] (DROOLS-3098) Add support for map and list
by Daniele Zonca (Jira)
Daniele Zonca created DROOLS-3098:
-------------------------------------
Summary: Add support for map and list
Key: DROOLS-3098
URL: https://issues.jboss.org/browse/DROOLS-3098
Project: Drools
Issue Type: Story
Components: Scenario Simulation and Testing
Reporter: Daniele Zonca
Assignee: Daniele Zonca
As user I want to be able to use Data Objects that contain Lists and Maps
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3095) Grid with multiple data/domain object instances
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3095?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-3095:
-------------------------------------
Description:
Implement "Instance" concept on the GIVEN/EXPECTED columns.
Given/Expected columns should have three headers:
# the top one is the group (GIVEN/EXPECTED),
# the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
# the third one is the specific property of the instance.
Below every instance header there could be one ore more property header - each of them belonging to that instance.
The user must define the type/name of the instance *before* mapping the final properties.
When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
When clicking on a Property header, user should see only first-level properties of the Instance it belongs to.
When When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.
These issue is related to https://issues.jboss.org/browse/DROOLS-2788
was:
Implement "Instance" concept on the GIVEN/EXPECTED columns.
Given/Expected columns should have three headers:
# the top one is the group (GIVEN/EXPECTED),
# the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
# the third one is the specific property of the instance.
Below every instance there could be one ore more properties - each of them related of that instance.
The user must define the type/name of the instance *before* mappping the final properties.
When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
When clicking on a Property header, user should see only first-level properties of the Instance it belongs to.
When When clicking on an EXPECET "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
> Grid with multiple data/domain object instances
> -----------------------------------------------
>
> Key: DROOLS-3095
> URL: https://issues.jboss.org/browse/DROOLS-3095
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
>
> Implement "Instance" concept on the GIVEN/EXPECTED columns.
> Given/Expected columns should have three headers:
> # the top one is the group (GIVEN/EXPECTED),
> # the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
> # the third one is the specific property of the instance.
> Below every instance header there could be one ore more property header - each of them belonging to that instance.
> The user must define the type/name of the instance *before* mapping the final properties.
> When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
> When clicking on a Property header, user should see only first-level properties of the Instance it belongs to.
> When When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
> Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.
> These issue is related to https://issues.jboss.org/browse/DROOLS-2788
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3095) Grid with multiple data/domain object instances
by Gabriele Cardosi (Jira)
Gabriele Cardosi created DROOLS-3095:
----------------------------------------
Summary: Grid with multiple data/domain object instances
Key: DROOLS-3095
URL: https://issues.jboss.org/browse/DROOLS-3095
Project: Drools
Issue Type: Task
Components: Scenario Simulation and Testing
Reporter: Gabriele Cardosi
Assignee: Gabriele Cardosi
Implement "Instance" concept on the GIVEN/EXPECTED columns.
Given/Expected columns should have three headers:
# the top one is the group (GIVEN/EXPECTED),
# the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
# the third one is the specific property of the instance.
Below every instance there could be one ore more properties - each of them related of that instance.
The user must define the type/name of the instance *before* mappping the final properties.
When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
When clicking on a Property header, user should see only first-level properties of the Instance it belongs to.
When When clicking on an EXPECET "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-10336) MustUnderstand headers: [{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security] are not understood.
by Daniel Čihák (Jira)
[ https://issues.jboss.org/browse/WFLY-10336?page=com.atlassian.jira.plugin... ]
Daniel Čihák reassigned WFLY-10336:
-----------------------------------
Assignee: Daniel Čihák (was: Jan Blizňák)
> MustUnderstand headers: [{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security] are not understood.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10336
> URL: https://issues.jboss.org/browse/WFLY-10336
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite, Web Services
> Environment: {noformat}
> Java(TM) SE Runtime Environment (build 8.0.5.11 - pxa6480sr5fp11-20180326_01(SR5 FP11))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64 Compressed References 20180309_380776 (JIT enabled, AOT enabled)
> OpenJ9 - 49fcaf39
> OMR - 5cbbadf
> IBM - 4453dac)
> JCL - 20180319_01 based on Oracle jdk8u161-b12
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Daniel Čihák
> Priority: Major
>
> There are test failures running the WildFly Test Suite: Integration - WS on IBM jdk.
> {noformat}
> wildfly/testsuite/integration/ws] $ mvn clean install
> ...
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] EJBSignTestCase.signedRequest:86 » SOAPFault MustUnderstand headers: [{http://...
> [ERROR] SignTestCase.signedRequest:88 » SOAPFault MustUnderstand headers: [{http://doc...
> [ERROR] EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromAlice:90 » SOAPFault
> [ERROR] EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn:102 » SOAPFault
> [ERROR] EJBSignEncryptTestCase.encryptedAndSignedRequest:88 » SOAPFault MustUnderstand...
> [ERROR] SignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromAlice:91 » SOAPFault
> [ERROR] SignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn:103 » SOAPFault
> [ERROR] SignEncryptTestCase.encryptedAndSignedRequest:90 » SOAPFault MustUnderstand he...
> [ERROR] WSTrustTestCase.test:318 » SOAPFault MustUnderstand headers: [{http://docs.oas...
> [ERROR] WSTrustTestCase.testActAs:441 » SOAPFault MustUnderstand headers: [{http://doc...
> [ERROR] WSTrustTestCase.testBearer:541 » SOAPFault MustUnderstand headers: [{http://do...
> [ERROR] WSTrustTestCase.testHolderOfKey:491 » SOAPFault MustUnderstand headers: [{http...
> [ERROR] WSTrustTestCase.testNoClientCallback:383 » SOAPFault MustUnderstand headers: [...
> [ERROR] WSTrustTestCase.testNoSignatureUsername:414 » SOAPFault MustUnderstand headers...
> [ERROR] WSTrustTestCase.testOnBehalfOf:468 » SOAPFault MustUnderstand headers: [{http:...
> [ERROR] WSTrustTestCase.testPicketLink:518 » SOAPFault MustUnderstand headers: [{http:...
> [ERROR] WSTrustTestCase.testUsingEPR:350 » SOAPFault MustUnderstand headers: [{http://...
> [INFO]
> [ERROR] Tests run: 119, Failures: 0, Errors: 17, Skipped: 0
> {noformat}
> *Caused by*
> {noformat}
> Caused by: org.apache.cxf.binding.soap.SoapFault: MustUnderstand headers: [{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security] are not understood.
> at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:87)
> at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:53)
> at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:42)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:112)
> at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:70)
> at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:35)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:827)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1695)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1572)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1373)
> at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
> at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:673)
> at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:63)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:533)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:442)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:343)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:296)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139)
> ... 129 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3054) Highlight in expression builder previous selection in Scenario right panel
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3054?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi edited comment on DROOLS-3054 at 10/10/18 4:42 AM:
--------------------------------------------------------------------
[~srambach] [~uxdlc] [~danielezonca]
Hi Sarah, I tried to put the class as per your suggestion, but the higlighting does not work. Could you provide me the html+css snippets for highlighted(selected)/ not-highlighted (unselected) elements?
was (Author: gabriolo):
[~srambach] [~uxdlc] [~danielezonca]
Hi Sarah, I tried to put the class as per your suggestion, but the higlithing does not work. Could you provide me the html+css snippets for highlighted(selected)/ not-highlighted (unselected) elements?
> Highlight in expression builder previous selection in Scenario right panel
> --------------------------------------------------------------------------
>
> Key: DROOLS-3054
> URL: https://issues.jboss.org/browse/DROOLS-3054
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screen Shot 2018-09-28 at 3.45.25 PM.png
>
>
> When the user edits the type of a column, the expression builder into the right panel should highlight the existing mapped type.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3054) Highlight in expression builder previous selection in Scenario right panel
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3054?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-3054:
-------------------------------------
Comment: was deleted
(was: [~srambach] [~uxdlc] [~danielezonca]
Hi Sarah, I tried to put the class as per your suggestion, but the higlithing does not work. Could you provide me the html+css snippets for highlighted(selected)/ not-highlighted (unselected) elements?)
> Highlight in expression builder previous selection in Scenario right panel
> --------------------------------------------------------------------------
>
> Key: DROOLS-3054
> URL: https://issues.jboss.org/browse/DROOLS-3054
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screen Shot 2018-09-28 at 3.45.25 PM.png
>
>
> When the user edits the type of a column, the expression builder into the right panel should highlight the existing mapped type.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3054) Highlight in expression builder previous selection in Scenario right panel
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3054?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi commented on DROOLS-3054:
------------------------------------------
[~srambach] [~uxdlc] [~danielezonca]
Hi Sarah, I tried to put the class as per your suggestion, but the higlithing does not work. Could you provide me the html+css snippets for highlighted(selected)/ not-highlighted (unselected) elements?
> Highlight in expression builder previous selection in Scenario right panel
> --------------------------------------------------------------------------
>
> Key: DROOLS-3054
> URL: https://issues.jboss.org/browse/DROOLS-3054
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screen Shot 2018-09-28 at 3.45.25 PM.png
>
>
> When the user edits the type of a column, the expression builder into the right panel should highlight the existing mapped type.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3054) Highlight in expression builder previous selection in Scenario right panel
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3054?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi commented on DROOLS-3054:
------------------------------------------
[~srambach] [~uxdlc] [~danielezonca]
Hi Sarah, I tried to put the class as per your suggestion, but the higlithing does not work. Could you provide me the html+css snippets for highlighted(selected)/ not-highlighted (unselected) elements?
> Highlight in expression builder previous selection in Scenario right panel
> --------------------------------------------------------------------------
>
> Key: DROOLS-3054
> URL: https://issues.jboss.org/browse/DROOLS-3054
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screen Shot 2018-09-28 at 3.45.25 PM.png
>
>
> When the user edits the type of a column, the expression builder into the right panel should highlight the existing mapped type.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi commented on DROOLS-3053:
------------------------------------------
[~srambach] [~uxdlc] [~danielezonca]
Hi Sarah, I would need the html/css (based on patternly) for this popup - I can not make a nice one simply extending the already existing one.
> Warning popup of column type change in Scenario grid
> ----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.png, warning2.png
>
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done/merged *after* DROOLS-3051.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
> - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months