[JBoss JIRA] (DROOLS-3023) [DMN Designer] Data Types - Warnings - User must be warned when some operations affect other Data Types
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3023?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3023:
--------------------------------
Description:
1) When a Structure Data Type (with fields) is updated to a simple type (e.g. String, Number, Date, etc), a warn message must appear informing the user that the fields will be lost.
- tPerson
-- uuid
-- name
-- city (Structure) <-- If this data type is updated to "String", the "uuid" and "name" fields will be lost.
--- uuid
--- name
----
2) When a Data Type is removed, a warn message must appear informing the user that data types with the removed type will be removed too.
- tCity <-- If the user removes this Data Type
-- uuid
-- name
- tPerson
-- uuid
-- name
-- city (tCity) <-- This field will be removed too..
--- uuid <-- ..and consequently..
--- name <-- ..these two will be removed too.
h2. Manual acceptance test
Check warning list all occurrences:
- Remove item definition used as part of other item definitions (/)
-- Top level, all occurences removed
-- Nested level, top level definition remains
- Remove item definitions used as output data-type for decision node (x)
- Remove item definition used as data-type for expression element (column, parameter, ...) (x)
was:
1) When a Structure Data Type (with fields) is updated to a simple type (e.g. String, Number, Date, etc), a warn message must appear informing the user that the fields will be lost.
- tPerson
-- uuid
-- name
-- city (Structure) <-- If this data type is updated to "String", the "uuid" and "name" fields will be lost.
--- uuid
--- name
----
2) When a Data Type is removed, a warn message must appear informing the user that data types with the removed type will be removed too.
- tCity <-- If the user removes this Data Type
-- uuid
-- name
- tPerson
-- uuid
-- name
-- city (tCity) <-- This field will be removed too..
--- uuid <-- ..and consequently..
--- name <-- ..these two will be removed too.
h2. Manual acceptance test
Check warning list all occurrences:
- Remove item definition used as part of other item definitions
-- Top level, all occurences removed
-- Nested level, top level definition remains
- Remove item definitions used as output data-type for decision node
- Remove item definition used as data-type for expression element (column, parameter, ...)
> [DMN Designer] Data Types - Warnings - User must be warned when some operations affect other Data Types
> -------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3023
> URL: https://issues.jboss.org/browse/DROOLS-3023
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: prototype.png
>
>
> 1) When a Structure Data Type (with fields) is updated to a simple type (e.g. String, Number, Date, etc), a warn message must appear informing the user that the fields will be lost.
> - tPerson
> -- uuid
> -- name
> -- city (Structure) <-- If this data type is updated to "String", the "uuid" and "name" fields will be lost.
> --- uuid
> --- name
> ----
> 2) When a Data Type is removed, a warn message must appear informing the user that data types with the removed type will be removed too.
> - tCity <-- If the user removes this Data Type
> -- uuid
> -- name
> - tPerson
> -- uuid
> -- name
> -- city (tCity) <-- This field will be removed too..
> --- uuid <-- ..and consequently..
> --- name <-- ..these two will be removed too.
> h2. Manual acceptance test
> Check warning list all occurrences:
> - Remove item definition used as part of other item definitions (/)
> -- Top level, all occurences removed
> -- Nested level, top level definition remains
> - Remove item definitions used as output data-type for decision node (x)
> - Remove item definition used as data-type for expression element (column, parameter, ...) (x)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11128) wsconsume/wsprovide failure on wildfly14 + JDK 11
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFLY-11128?page=com.atlassian.jira.plugin... ]
Marek Kopecký updated WFLY-11128:
---------------------------------
Summary: wsconsume/wsprovide failure on wildfly14 + JDK 11 (was: wsconsume failure on wildfly14 + JDK 11)
> wsconsume/wsprovide failure on wildfly14 + JDK 11
> -------------------------------------------------
>
> Key: WFLY-11128
> URL: https://issues.jboss.org/browse/WFLY-11128
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 13.0.0.Final, 14.0.0.Final
> Environment: Windows 7 64bits
> JDK 11
> Wildfly 14
> Reporter: mazen mahmoud
> Assignee: R Searls
> Priority: Critical
> Fix For: 15.0.0.Alpha1
>
> Attachments: HelloWorldService-imported.xml, HelloWorldService.xml, demo-service-code.zip, log.txt, logs.zip
>
>
> running wsconsume on a single jax-ws service with JDK 11 failes. (see attached log.txt file)
> the service is very simple.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11128) wsconsume/wsprovide failure on wildfly14 + JDK 11
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFLY-11128?page=com.atlassian.jira.plugin... ]
Marek Kopecký updated WFLY-11128:
---------------------------------
Description:
running wsconsume/wsprovide on a single jax-ws service with JDK 11 failes. (see attached log.txt file)
the service is very simple.
was:
running wsconsume on a single jax-ws service with JDK 11 failes. (see attached log.txt file)
the service is very simple.
> wsconsume/wsprovide failure on wildfly14 + JDK 11
> -------------------------------------------------
>
> Key: WFLY-11128
> URL: https://issues.jboss.org/browse/WFLY-11128
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 13.0.0.Final, 14.0.0.Final
> Environment: Windows 7 64bits
> JDK 11
> Wildfly 14
> Reporter: mazen mahmoud
> Assignee: R Searls
> Priority: Critical
> Fix For: 15.0.0.Alpha1
>
> Attachments: HelloWorldService-imported.xml, HelloWorldService.xml, demo-service-code.zip, log.txt, logs.zip
>
>
> running wsconsume/wsprovide on a single jax-ws service with JDK 11 failes. (see attached log.txt file)
> the service is very simple.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3125) [DMN Designer][Edge] Cancel data type edit operation throws an error
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3125?page=com.atlassian.jira.plugi... ]
Michael Anstis reassigned DROOLS-3125:
--------------------------------------
Assignee: Guilherme Carreiro (was: Michael Anstis)
> [DMN Designer][Edge] Cancel data type edit operation throws an error
> --------------------------------------------------------------------
>
> Key: DROOLS-3125
> URL: https://issues.jboss.org/browse/DROOLS-3125
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Environment: Windows, Edge
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2018-10-12 10-42-53.png
>
>
> If user tries to cancel data type edit operation, the unexpected error dialog appears and contains this error message:
> *Uncaught exception: Exception caught: (Error) : Could not complete the operation due to error 800a025e. Caused by: (Error) : Could not complete the operation due to error 800a025e.*
> Occurs just on Microsoft Edge
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3125) [DMN Designer][Edge] Cancel data type edit operation throws an error
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3125?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3125:
--------------------------------
Description:
If user tries to cancel data type edit operation, the unexpected error dialog appears and contains this error message:
*Uncaught exception: Exception caught: (Error) : Could not complete the operation due to error 800a025e. Caused by: (Error) : Could not complete the operation due to error 800a025e.*
Occurs just on Microsoft Edge
was:
If user tries to cancel data type edit operation, the unexpected error dialog appears and contains this error message:
*Uncaught exception: Exception caught: (Error) : Could not complete the operation due to error 800a025e. Caused by: (Error) : Could not complete the operation due to error 800a025e.*
Steps to Reproduce:
# Open any exiting dmn model with custom data types inside
# Invoke manage data type dialog - shown in attachment
# Click edito next to any entry there
# Click to cross next to same entry as in previous step to cancel edit operation
# The unexpected error dialog will appear.
> [DMN Designer][Edge] Cancel data type edit operation throws an error
> --------------------------------------------------------------------
>
> Key: DROOLS-3125
> URL: https://issues.jboss.org/browse/DROOLS-3125
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Environment: Windows, Edge
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2018-10-12 10-42-53.png
>
>
> If user tries to cancel data type edit operation, the unexpected error dialog appears and contains this error message:
> *Uncaught exception: Exception caught: (Error) : Could not complete the operation due to error 800a025e. Caused by: (Error) : Could not complete the operation due to error 800a025e.*
> Occurs just on Microsoft Edge
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3125) [DMN Designer][Edge] Cancel data type edit mode throws an error
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3125?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3125:
--------------------------------
Description:
If user tries to cancel data type edit operation, the unexpected error dialog appears and contains this error message:
*Uncaught exception: Exception caught: (Error) : Could not complete the operation due to error 800a025e. Caused by: (Error) : Could not complete the operation due to error 800a025e.*
> [DMN Designer][Edge] Cancel data type edit mode throws an error
> ---------------------------------------------------------------
>
> Key: DROOLS-3125
> URL: https://issues.jboss.org/browse/DROOLS-3125
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Environment: Windows, Edge
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2018-10-12 10-42-53.png
>
>
> If user tries to cancel data type edit operation, the unexpected error dialog appears and contains this error message:
> *Uncaught exception: Exception caught: (Error) : Could not complete the operation due to error 800a025e. Caused by: (Error) : Could not complete the operation due to error 800a025e.*
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3125) [DMN Designer][Edge] Cancel data type edit operation throws an error
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3125?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3125:
--------------------------------
Summary: [DMN Designer][Edge] Cancel data type edit operation throws an error (was: [DMN Designer][Edge] Cancel data type edit mode throws an error)
> [DMN Designer][Edge] Cancel data type edit operation throws an error
> --------------------------------------------------------------------
>
> Key: DROOLS-3125
> URL: https://issues.jboss.org/browse/DROOLS-3125
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Environment: Windows, Edge
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2018-10-12 10-42-53.png
>
>
> If user tries to cancel data type edit operation, the unexpected error dialog appears and contains this error message:
> *Uncaught exception: Exception caught: (Error) : Could not complete the operation due to error 800a025e. Caused by: (Error) : Could not complete the operation due to error 800a025e.*
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11137) Make undertow extension module's dependency on org.jboss.as.security module optional
by Jean-Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFLY-11137?page=com.atlassian.jira.plugin... ]
Jean-Francois Denise commented on WFLY-11137:
---------------------------------------------
[~brian.stansberry], could direct deps from undertow to org.picketbox and org.jboss.security.negotiation be made optional too?
> Make undertow extension module's dependency on org.jboss.as.security module optional
> ------------------------------------------------------------------------------------
>
> Key: WFLY-11137
> URL: https://issues.jboss.org/browse/WFLY-11137
> Project: WildFly
> Issue Type: Task
> Components: Security, Web (Undertow)
> Reporter: Brian Stansberry
> Assignee: Yeray Borges
> Priority: Major
>
> Don't require the legacy security subsystem module if it's not actually used.
> Usage looks like this:
> {code}
> wildfly bstansberry$ cd undertow/
> undertow bstansberry$ git grep org.jboss.as.security
> src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentInfoService.java:import org.jboss.as.security.plugins.SecurityDomainContext;
> src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentProcessor.java:import org.jboss.as.security.deployment.AbstractSecurityDeployer;
> src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentProcessor.java:import org.jboss.as.security.deployment.SecurityAttachments;
> src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentProcessor.java:import org.jboss.as.security.plugins.SecurityDomainContext;
> src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentProcessor.java:import org.jboss.as.security.service.JaccService;
> src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentProcessor.java:import org.jboss.as.security.service.SecurityDomainService;
> src/main/java/org/wildfly/extension/undertow/security/DigestCredentialImpl.java:import org.jboss.as.security.DigestCredential;
> src/main/java/org/wildfly/extension/undertow/security/JAASIdentityManagerImpl.java:import org.jboss.as.security.plugins.SecurityDomainContext;
> src/main/java/org/wildfly/extension/undertow/security/SecurityContextThreadSetupAction.java:import org.jboss.as.security.plugins.SecurityDomainContext;
> src/main/java/org/wildfly/extension/undertow/security/jacc/WarJACCDeployer.java:import org.jboss.as.security.deployment.AbstractSecurityDeployer;
> src/main/java/org/wildfly/extension/undertow/security/jacc/WarJACCDeployer.java:import org.jboss.as.security.service.JaccService;
> src/main/java/org/wildfly/extension/undertow/security/jacc/WarJACCService.java:import org.jboss.as.security.service.JaccService;
> {code}
> Dropping the use of SecurityAttachments from UndertowDeploymentProcessor and instead having it check for the presence of the org.wildfly.legacy-security capability will go a long way here. After that, most if not all of the other uses only get called either as a result of that check being true, or some config attribute that directly or indirectly references a security domain. IOW the other uses are only needed if the security subsystem is known to be configured.
> Per Intellij, DigestCredentialImpl is unused.
--
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:
-------------------------------------
This issue is more complex. To get rid of the {{SoapFault: MustUnderstand headers}} exception we need to add a message handler implementing {{SOAPHandler}} and configure it in the configuration file annotated in the service EchoService {{@HandlerChain(file = "dummmy-ws-handler.xml")}}. This handler overrides {{getHeaders}} method to process the security header. The handler-chain will now look like
{code:title=dummmy-ws-handler.xml}
<handler-chain>
<handler>
<handler-name>ContextHandler</handler-name>
<handler-class>org.jboss.as.test.integration.ws.authentication.policy.HeaderWSContextProcessor</handler-class>
</handler>
<handler>
<handler-name>SAML2Handler</handler-name>
<handler-class>org.picketlink.trust.jbossws.handler.SAML2Handler</handler-class>
</handler>
</handler-chain>
{code}
SAML2Handler is used for the security context creation and HeaderWSContextProcessor processes the header. When those two headers are used in the chain and the AuthenticationPolicyContextTestCase is run together with another test (EJBSignTestCase), the second test fails with the {{org.apache.cxf.binding.soap.SoapFault: MustUnderstand headers}}. This behaviour occurs on Wildfly and on IMB JDK.
We also found out when running the tests with a parameter {{-DreuseForks=false}} this issue does not occur any more. The problem might be in the line https://github.com/wildfly/wildfly/blob/master/testsuite/integration/ws/s... {{assertion = wsClient.issueToken(SAMLUtil.SAML2_TOKEN_TYPE);}}. When this line is omitted the exception stops appearing. We still don't know the solution of this and must abort the investigation for now.
> 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