[JBoss JIRA] (DROOLS-3067) [DMN Designer] Automatic Layout Feature Workbench Integration
by Daniel José dos Santos (Jira)
[ https://issues.jboss.org/browse/DROOLS-3067?page=com.atlassian.jira.plugi... ]
Daniel José dos Santos commented on DROOLS-3067:
------------------------------------------------
I opened the [^DMCommunity Challenge - March 2017.dmn] without the auto layout and with auto layout and looks the same to me (two separate graphs). Am I missing something?
This is with automatic layout: !auto.png|thumbnail!
This is the old version, without automatic layout: !manual.png|thumbnail!
Thank you.
> [DMN Designer] Automatic Layout Feature Workbench Integration
> -------------------------------------------------------------
>
> Key: DROOLS-3067
> URL: https://issues.jboss.org/browse/DROOLS-3067
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: DMCommunity Challenge - March 2017.dmn, auto.png, manual.png
>
>
> Integrate the Automatic Layout feature into workbench, so during opening an imported DMN model its nodes are positioned automatically with this feature.
> h2. Acceptance tests
> # -User is prompted if he wants or not to apply autolayout feature- discussed in comments
> # Positioning is automatically stored after model opening
> # Simple graph, no branches, starting node on left, ending node on right
> # Simple graph, no branches, starting node on bottom, ending node on top
> # Tree, top node in the middle of the screen, some branches to all sides
> # Graph with big crossing of edges, similar to complete graph
> # Large (but sparse) graph, not all nodes visible without scrolling
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3067) [DMN Designer] Automatic Layout Feature Workbench Integration
by Daniel José dos Santos (Jira)
[ https://issues.jboss.org/browse/DROOLS-3067?page=com.atlassian.jira.plugi... ]
Daniel José dos Santos updated DROOLS-3067:
-------------------------------------------
Attachment: auto.png
> [DMN Designer] Automatic Layout Feature Workbench Integration
> -------------------------------------------------------------
>
> Key: DROOLS-3067
> URL: https://issues.jboss.org/browse/DROOLS-3067
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: DMCommunity Challenge - March 2017.dmn, auto.png
>
>
> Integrate the Automatic Layout feature into workbench, so during opening an imported DMN model its nodes are positioned automatically with this feature.
> h2. Acceptance tests
> # -User is prompted if he wants or not to apply autolayout feature- discussed in comments
> # Positioning is automatically stored after model opening
> # Simple graph, no branches, starting node on left, ending node on right
> # Simple graph, no branches, starting node on bottom, ending node on top
> # Tree, top node in the middle of the screen, some branches to all sides
> # Graph with big crossing of edges, similar to complete graph
> # Large (but sparse) graph, not all nodes visible without scrolling
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11144) Remove javax.ejb.api module dependency on javax.rmi.api
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11144?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-11144:
-----------------------------------------
Thanks, David.
> Remove javax.ejb.api module dependency on javax.rmi.api
> -------------------------------------------------------
>
> Key: WFLY-11144
> URL: https://issues.jboss.org/browse/WFLY-11144
> Project: WildFly
> Issue Type: Task
> Components: EJB
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
>
> The javax.ejb.api module depends on javax.rmi.api. But I can't see any reason why; the code in the spec jar does not import anything from any of the classes in the javax.rmi and org.jboss.javax.rmi packages that the javax.rmi.api module exports.
> This is important because javax.rmi.api brings in a huge dependency tree. That module is really just a wrapper around javax.orb.api, exporting a subset of its packages. And javax.orb.api is a misnomer -- it's not just API, it's the entire orb, with implementation dependencies that transitively bring in a large chunk of the entire appserver codebase.
> So if javax.ejb.api does not need javax.rmi.api we need to remove that link.
--
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 Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3053:
-------------------------------------
Thanks [~stetson.robinson], good point! As you suggest works for me - either whatever is already being done consistently in the UI, or lower case.
> 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
[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Stetson Robinson commented on DROOLS-3053:
------------------------------------------
[~uxdlc] fine by me, just choose whether to go with cap "Scenario" or lc "scenario" (one way in first part another in the options). I _think_ UX leans toward caps in the UI fairly consistently, but docs avoids caps intentionally unless referencing cap text in the UI and formal feature/component names. So it's up to you. Whatever is already being done is fine.
> 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
[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3053:
-------------------------------------
[~stetson.robinson]Are you OK with the above, or should I change it?
> 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
[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 commented on WFLY-10336:
-------------------------------------
It seems I found the solution.
> 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: Jan Blizňá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-3092) User can not see all the definition editing custom data ypes
by Daniel José dos Santos (Jira)
Daniel José dos Santos created DROOLS-3092:
----------------------------------------------
Summary: User can not see all the definition editing custom data ypes
Key: DROOLS-3092
URL: https://issues.jboss.org/browse/DROOLS-3092
Project: Drools
Issue Type: Task
Components: DMN Editor
Affects Versions: 7.12.0.Final
Reporter: Daniel José dos Santos
Assignee: Michael Anstis
Attachments: 46597891-4abb2b00-cae2-11e8-9e05-6649abbdeb23.png
When editing "Custom Data Types", not all definitions are visible. This behaviour happens in all browsers.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (ELY-1692) Tests are not run with -Djava8.home java
by Justin Cook (Jira)
[ https://issues.jboss.org/browse/ELY-1692?page=com.atlassian.jira.plugin.s... ]
Justin Cook reassigned ELY-1692:
--------------------------------
Assignee: Justin Cook
> Tests are not run with -Djava8.home java
> ----------------------------------------
>
> Key: ELY-1692
> URL: https://issues.jboss.org/browse/ELY-1692
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Testsuite
> Affects Versions: 1.7.0.CR2
> Reporter: Martin Choma
> Assignee: Justin Cook
> Priority: Blocker
>
> Elytron enforces JDK9+ jdk, but is not possible to run tests with jdk 8.
> {noformat}
> java -version
> java version "11" 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11+28)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
> mvn clean test -Dtest=MechanismDatabaseTest -Dmaven.test.redirectTestOutputToFile=true -Djava8.home=/home/mchoma/app/jdk8u172-b11 -X
> ...
> [DEBUG] Forking command line: /bin/sh -c cd /home/mchoma/git-repo/wildfly-elytron && /home/mchoma/app/jdk-11+28/bin/java
> {noformat}
> Also in surefire reports java8 folder there is java 11 logged
> {noformat}
> <property name="java.vendor" value="Oracle Corporation"/>
> <property name="java.vm.info" value="mixed mode"/>
> <property name="java.vm.version" value="11+28"/>
> {noformat}
> Setting to blocker as currently I dont see way how to run tests on jdk8.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months