[JBoss JIRA] (WFCORE-4159) WildFly Core Test Suite: Standalone Integration Tests doesn't compile on JDKs other than Oracle Java 1.8
by Vilém Obrátil (Jira)
[ https://issues.jboss.org/browse/WFCORE-4159?page=com.atlassian.jira.plugi... ]
Vilém Obrátil updated WFCORE-4159:
----------------------------------
Environment:
OS:
RHEL 6 (x86_64)
RHEL 7
JDKs:
OpenJDK 1.8
OpenJDK 11
Oracle Java 11
IBM Java 1.8
Maven:
Apache Maven 3.5.3
was:
OS:
RHEL 6 (x86_64)
RHEL 7
JDKs:
OpenJDK 1.8
OpenJDK 11
Oracle Java 11
IBM Java 1.8
> WildFly Core Test Suite: Standalone Integration Tests doesn't compile on JDKs other than Oracle Java 1.8
> --------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4159
> URL: https://issues.jboss.org/browse/WFCORE-4159
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 7.0.0.Alpha3
> Environment: OS:
> RHEL 6 (x86_64)
> RHEL 7
> JDKs:
> OpenJDK 1.8
> OpenJDK 11
> Oracle Java 11
> IBM Java 1.8
> Maven:
> Apache Maven 3.5.3
> Reporter: Vilém Obrátil
> Assignee: Jean-Francois Denise
> Priority: Major
>
> Running the testsuite in on JDKs other than Oracle Java 1.8 causes Maven to run into a compilation error with the following message:
> ...
> 00:20:08 [INFO] WildFly Core Test Suite: Shared .................... SUCCESS [ 1.555 s]
> 00:20:08 [INFO] WildFly: Vault Test Feature Pack ................... SUCCESS [ 0.203 s]
> 00:20:08 [INFO] WildFly Core Test Suite: Aggregator ................ SUCCESS [ 0.599 s]
> 00:20:08 [INFO] WildFly Core Test Suite: Standalone Integration Tests FAILURE [ 4.565 s]
> 00:20:08 [INFO] WildFly Core Test Suite: Elytron Integration Tests . SUCCESS [01:54 min]
> 00:20:08 [INFO] WildFly Core Test Suite: Embedded Integration Tests SUCCESS [ 31.858 s]
> 00:20:08 [INFO] wildfly-script-tests ............................... SUCCESS [ 17.741 s]
> 00:20:08 [INFO] WildFly Core Test Suite: Role Based Access Control . SUCCESS [02:51 min]
> 00:20:08 [INFO] WildFly Core Test Suite: Domain Mode Integration Tests SUCCESS [26:36 min]
> 00:20:08 [INFO] WildFly Core Test Suite: Manual Mode Tests ......... SUCCESS [11:26 min]
> 00:20:08 [INFO] WildFly Core Test Suite: Patching 7.0.0.Alpha3-SNAPSHOT SUCCESS [14:21 min]
> 00:20:08 [INFO] ------------------------------------------------------------------------
> 00:20:08 [INFO] BUILD FAILURE
> 00:20:08 [INFO] ------------------------------------------------------------------------
> 00:20:08 [INFO] Total time: 01:14 h
> 00:20:08 [INFO] Finished at: 2018-10-09T00:20:07Z
> 00:20:08 [INFO] ------------------------------------------------------------------------
> 00:20:08 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile (default-testCompile) on project wildfly-core-testsuite-standalone: Compilation failure: Compilation failure:
> 00:20:08 [ERROR] /home/hudson/hudson_workspace/workspace/eap-7.x-as-testsuite-core-rhel/28995480/testsuite/standalone/src/test/java/org/jboss/as/test/integration/management/cli/LongOutputTestCase.java:[3,27] package com.sun.javafx.util does not exist
> 00:20:08 [ERROR] /home/hudson/hudson_workspace/workspace/eap-7.x-as-testsuite-core-rhel/28995480/testsuite/standalone/src/test/java/org/jboss/as/test/integration/management/cli/LongOutputTestCase.java:[240,13] cannot find symbol
> 00:20:08 [ERROR] symbol: variable Utils
> 00:20:08 [ERROR] location: class org.jboss.as.test.integration.management.cli.LongOutputTestCase
> ...
> Probably caused by a change in [WFCORE-4096|https://issues.jboss.org/browse/WFCORE-4096].
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFCORE-4159) WildFly Core Test Suite: Standalone Integration Tests doesn't compile on JDKs other than Oracle Java 1.8
by Vilém Obrátil (Jira)
Vilém Obrátil created WFCORE-4159:
-------------------------------------
Summary: WildFly Core Test Suite: Standalone Integration Tests doesn't compile on JDKs other than Oracle Java 1.8
Key: WFCORE-4159
URL: https://issues.jboss.org/browse/WFCORE-4159
Project: WildFly Core
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.0.0.Alpha3
Environment: OS:
RHEL 6 (x86_64)
RHEL 7
JDKs:
OpenJDK 1.8
OpenJDK 11
Oracle Java 11
IBM Java 1.8
Reporter: Vilém Obrátil
Assignee: Jean-Francois Denise
Running the testsuite in on JDKs other than Oracle Java 1.8 causes Maven to run into a compilation error with the following message:
...
00:20:08 [INFO] WildFly Core Test Suite: Shared .................... SUCCESS [ 1.555 s]
00:20:08 [INFO] WildFly: Vault Test Feature Pack ................... SUCCESS [ 0.203 s]
00:20:08 [INFO] WildFly Core Test Suite: Aggregator ................ SUCCESS [ 0.599 s]
00:20:08 [INFO] WildFly Core Test Suite: Standalone Integration Tests FAILURE [ 4.565 s]
00:20:08 [INFO] WildFly Core Test Suite: Elytron Integration Tests . SUCCESS [01:54 min]
00:20:08 [INFO] WildFly Core Test Suite: Embedded Integration Tests SUCCESS [ 31.858 s]
00:20:08 [INFO] wildfly-script-tests ............................... SUCCESS [ 17.741 s]
00:20:08 [INFO] WildFly Core Test Suite: Role Based Access Control . SUCCESS [02:51 min]
00:20:08 [INFO] WildFly Core Test Suite: Domain Mode Integration Tests SUCCESS [26:36 min]
00:20:08 [INFO] WildFly Core Test Suite: Manual Mode Tests ......... SUCCESS [11:26 min]
00:20:08 [INFO] WildFly Core Test Suite: Patching 7.0.0.Alpha3-SNAPSHOT SUCCESS [14:21 min]
00:20:08 [INFO] ------------------------------------------------------------------------
00:20:08 [INFO] BUILD FAILURE
00:20:08 [INFO] ------------------------------------------------------------------------
00:20:08 [INFO] Total time: 01:14 h
00:20:08 [INFO] Finished at: 2018-10-09T00:20:07Z
00:20:08 [INFO] ------------------------------------------------------------------------
00:20:08 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile (default-testCompile) on project wildfly-core-testsuite-standalone: Compilation failure: Compilation failure:
00:20:08 [ERROR] /home/hudson/hudson_workspace/workspace/eap-7.x-as-testsuite-core-rhel/28995480/testsuite/standalone/src/test/java/org/jboss/as/test/integration/management/cli/LongOutputTestCase.java:[3,27] package com.sun.javafx.util does not exist
00:20:08 [ERROR] /home/hudson/hudson_workspace/workspace/eap-7.x-as-testsuite-core-rhel/28995480/testsuite/standalone/src/test/java/org/jboss/as/test/integration/management/cli/LongOutputTestCase.java:[240,13] cannot find symbol
00:20:08 [ERROR] symbol: variable Utils
00:20:08 [ERROR] location: class org.jboss.as.test.integration.management.cli.LongOutputTestCase
...
Probably caused by a change in [WFCORE-4096|https://issues.jboss.org/browse/WFCORE-4096].
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11112) WildFly intermittently fails to add pooled-connection-factory but it still got registered after
by Ivan Straka (Jira)
[ https://issues.jboss.org/browse/WFLY-11112?page=com.atlassian.jira.plugin... ]
Ivan Straka edited comment on WFLY-11112 at 10/9/18 4:23 AM:
-------------------------------------------------------------
[~kabirkhan] We haven't seen the issue with 7.2.0.CD14.CR1
[~ehugonnet] I hit the issue for several times during WF master testing. So 14.0.0.Final is wrong.
was (Author: istraka):
[~kabirkhan] We haven't seen the issue with 7.2.0.GA.
[~ehugonnet] I hit the issue for several times during WF master testing. So 14.0.0.Final is wrong.
> WildFly intermittently fails to add pooled-connection-factory but it still got registered after
> -----------------------------------------------------------------------------------------------
>
> Key: WFLY-11112
> URL: https://issues.jboss.org/browse/WFLY-11112
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 15.0.0.Alpha1
> Reporter: Ivan Straka
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: server.log, standalone-full.xml
>
>
> We see following error in log of WildFly (master):
> {code}
> 2018-10-03 22:28:02,503 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default"),
> ("pooled-connection-factory" => "activemq-ra")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.JmsXA-bkp"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.JmsXA-bkp]"]
> }
> {code}
> Factory is defined:
> {code:java}
> <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA-bkp java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/>
> {code}
> However factory is registered after and deployment is able to use it. Error is logged intermittently.
> Log file and xml configuration file are enclosed.
--
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:
-------------------------------------
I can simulate it locally right now, but still don't know where is the problem.
> 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] (WFLY-11112) WildFly intermittently fails to add pooled-connection-factory but it still got registered after
by Ivan Straka (Jira)
[ https://issues.jboss.org/browse/WFLY-11112?page=com.atlassian.jira.plugin... ]
Ivan Straka updated WFLY-11112:
-------------------------------
Affects Version/s: (was: 14.0.0.Final)
> WildFly intermittently fails to add pooled-connection-factory but it still got registered after
> -----------------------------------------------------------------------------------------------
>
> Key: WFLY-11112
> URL: https://issues.jboss.org/browse/WFLY-11112
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 15.0.0.Alpha1
> Reporter: Ivan Straka
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: server.log, standalone-full.xml
>
>
> We see following error in log of WildFly (master):
> {code}
> 2018-10-03 22:28:02,503 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default"),
> ("pooled-connection-factory" => "activemq-ra")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.JmsXA-bkp"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.JmsXA-bkp]"]
> }
> {code}
> Factory is defined:
> {code:java}
> <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA-bkp java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/>
> {code}
> However factory is registered after and deployment is able to use it. Error is logged intermittently.
> Log file and xml configuration file are enclosed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11112) WildFly intermittently fails to add pooled-connection-factory but it still got registered after
by Ivan Straka (Jira)
[ https://issues.jboss.org/browse/WFLY-11112?page=com.atlassian.jira.plugin... ]
Ivan Straka commented on WFLY-11112:
------------------------------------
[~kabirkhan] We haven't seen the issue with 7.2.0.GA.
[~ehugonnet] I hit the issue for several times during WF master testing. So 14.0.0.Final is wrong.
> WildFly intermittently fails to add pooled-connection-factory but it still got registered after
> -----------------------------------------------------------------------------------------------
>
> Key: WFLY-11112
> URL: https://issues.jboss.org/browse/WFLY-11112
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 15.0.0.Alpha1
> Reporter: Ivan Straka
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: server.log, standalone-full.xml
>
>
> We see following error in log of WildFly (master):
> {code}
> 2018-10-03 22:28:02,503 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default"),
> ("pooled-connection-factory" => "activemq-ra")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.JmsXA-bkp"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.JmsXA-bkp]"]
> }
> {code}
> Factory is defined:
> {code:java}
> <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA-bkp java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/>
> {code}
> However factory is registered after and deployment is able to use it. Error is logged intermittently.
> Log file and xml configuration file are enclosed.
--
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 Martin Choma (Jira)
Martin Choma created ELY-1692:
---------------------------------
Summary: 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
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
[JBoss JIRA] (DROOLS-3022) [DMN Designer] Data Types - Validations - Validate the uniqueness and the presence of a Data Type name
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3022?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3022:
--------------------------------
Description:
The Data Type name must be unique at the level that it's defined; e.g.
- tPerson
-- uuid
-- name
-- city (Structure)
--- uuid
--- name
The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels.
----
Prototype:
!validation.png|thumbnail!
h2. Manaul Acceptance Test
- Try to put same name by Typing (/)
- Try to put same name by Copy and paste (/)
- Do not allow empty name (/)
- Allow spaces in name (/)
- Allow multibyte chars in name (/)
- Allow special characters in name (/)
- Allow lower upper case in name (/)
- Save when error shown (/)
- Cancel edit when error shown (/)
- Invoke other edit when error shown (/)
-- https://github.com/kiegroup/kie-wb-common/pull/2161#issuecomment-427978978
was:
The Data Type name must be unique at the level that it's defined; e.g.
- tPerson
-- uuid
-- name
-- city (Structure)
--- uuid
--- name
The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels.
----
Prototype:
!validation.png|thumbnail!
h2. Manaul Acceptance Test
- Try to put same name by Typing (/)
- Try to put same name by Copy and paste (/)
- Do not allow empty name (/)
- Allow spaces in name (/)
- Allow multibyte chars in name (/)
- Allow special characters in name (/)
- Allow lower upper case in name (/)
- Save when error shown (x)
- Cancel edit when error shown (x)
- Invoke other edit when error shown (x)
> [DMN Designer] Data Types - Validations - Validate the uniqueness and the presence of a Data Type name
> ------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3022
> URL: https://issues.jboss.org/browse/DROOLS-3022
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: validation.png
>
>
> The Data Type name must be unique at the level that it's defined; e.g.
> - tPerson
> -- uuid
> -- name
> -- city (Structure)
> --- uuid
> --- name
> The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels.
> ----
> Prototype:
> !validation.png|thumbnail!
> h2. Manaul Acceptance Test
> - Try to put same name by Typing (/)
> - Try to put same name by Copy and paste (/)
> - Do not allow empty name (/)
> - Allow spaces in name (/)
> - Allow multibyte chars in name (/)
> - Allow special characters in name (/)
> - Allow lower upper case in name (/)
> - Save when error shown (/)
> - Cancel edit when error shown (/)
> - Invoke other edit when error shown (/)
> -- https://github.com/kiegroup/kie-wb-common/pull/2161#issuecomment-427978978
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11123) Illegal reflective access by org.wildfly.extension.elytron.SSLDefinitions
by mazen mahmoud (Jira)
[ https://issues.jboss.org/browse/WFLY-11123?page=com.atlassian.jira.plugin... ]
mazen mahmoud commented on WFLY-11123:
--------------------------------------
com.sun packages are considered an implementation details, and they are not part of the JDK public API, thus they are not intended for direct usage.
Direct access is removed or deprecated on many classes. We need to switch for provided public API. Many internal classes have wrapper classes in
public APIs. I guess no worries for now.
> Illegal reflective access by org.wildfly.extension.elytron.SSLDefinitions
> -------------------------------------------------------------------------
>
> Key: WFLY-11123
> URL: https://issues.jboss.org/browse/WFLY-11123
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 14.0.1.Final
> Environment: Windows 7 x64. Java 11: OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11+28-201810022317, mixed mode)
> Reporter: Marco Del Percio
> Assignee: Darran Lofthouse
> Priority: Critical
> Labels: Java11, access, elytron, illegal, reflective, wildfly
>
> After configuring HTTPS using the following guide: [Enable One-way SSL/TLS for Applications|http://docs.wildfly.org/14/WildFly_Elytron_Security.html#con...], configuration seems ok and server boots fine however an illegal reflective access warning comes up from jar within Elytron:
> {color:red}
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.wildfly.extension.elytron.SSLDefinitions (jar:file:/D:/wildfly-14.0.1.Final_FleetManager/modules/system/layers/base/org/wildfly/extension/elytron/main/wildfly-elytron-integration-6.0.2.Final.jar!/) to method com.sun.net.ssl.internal.ssl.Provider.isFIPS()
> WARNING: Please consider reporting this to the maintainers of org.wildfly.extension.elytron.SSLDefinitions
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> {color}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11128) wsconsume failure on wildfly14 + JDK 11
by mazen mahmoud (Jira)
[ https://issues.jboss.org/browse/WFLY-11128?page=com.atlassian.jira.plugin... ]
mazen mahmoud updated WFLY-11128:
---------------------------------
Attachment: HelloWorldService-imported.xml
> wsconsume 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: 14.0.0.Final
> Environment: Windows 7 64bits
> JDK 11
> Wildfly 14
> Reporter: mazen mahmoud
> Assignee: R Searls
> Priority: Major
> 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