September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5617) Refactor MiningModel source generation

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5617?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-5617. ------------------------------------ > Refactor MiningModel source generation > -------------------------------------- > > Key: DROOLS-5617 > URL: https://issues.redhat.com/browse/DROOLS-5617 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Blocker > Labels: TrustyAI > > For code generation, currently, all sources of segment models of a MiningModel are put in the main (container) model sourcemap, and the list of "nested models" is empty. > Scope of this refactor is to populate the list of nested models with the "HasSourcesMap" version of all the models, and populate the "main" sourcemap only with the MiningModel specific sources -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-354) Bootable JAR - jboss-maven-dist plugin param doesn't work as expected

by Marek Kopecky (Jira)

[ https://issues.redhat.com/browse/WFWIP-354?page=com.atlassian.jira.plugin... ] Marek Kopecky resolved WFWIP-354. --------------------------------- Resolution: Not a Bug I close this jira, because current behaviour is expected. cc: [~fburzigo] > Bootable JAR - jboss-maven-dist plugin param doesn't work as expected > ---------------------------------------------------------------------- > > Key: WFWIP-354 > URL: https://issues.redhat.com/browse/WFWIP-354 > Project: WildFly WIP > Issue Type: Bug > Reporter: Marek Kopecky > Assignee: Jean Francois Denise > Priority: Blocker > > Related RFE: EAP7-1385 > This usage of jboss-maven-dist plugin param doesn't work as expected: > [<jboss-maven-dist>/home/mkopecky/jboss-eap-custom-maven-repository/maven-repository</jboss-maven-dist>|https://github.com/marekkopecky/Resteasy/commit/fb29381a9ef9a709f33481af8020a649db002980#diff-8c7ea03eb619e46657b96e8fe8d4f09eR248] > Steps to reproduce: > # clone resteasy 3.12 with this commit: https://github.com/marekkopecky/Resteasy/commit/fb29381a9ef9a709f33481af8... > # update jboss-maven-dist plugin param to your custom repo path > # rm -rf ~/.m2/repository/xerces/xercesImpl/2.12.0.SP03 > # set REPO variable (eg. "REPO=/home/mkopecky/jboss-eap-custom-maven-repository/maven-repository") > # build start tests {code}mvn install -DskipTests -Dmaven.repo.local=$REPO > cd testsuite > mvn install:install-file -Dpackaging=pom -Dfile=pom.xml -DpomFile=pom.xml -Dmaven.repo.local=$REPO > cd integration-tests > mvn clean install -Dts.bootable -Ddefault=false -Ddisable.microprofile.tests -Dserver.version=21.0.0.Beta1-SNAPSHOT -Dserver.home=placeholder -Dmaven.repo.local=$REPO -Dmaven.test.redirectTestOutputToFile=false{code} > # see the results: org.jboss.modules.ModuleLoadException, because xercesImpl 2.12.0.SP03 is downloaded in custom repo, but not present in .m2 > cc [~fburzigo], [~yersan] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13837) Investigate JSP (Jakarta EE 9 Platform) TCK failures

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13837?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-13837: ----------------------------------------- My guess ^^^ is wrong. Problem is org.wildfly.extension.undertow.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:117) is an if/else if quasi-switch block that needs to have a case added for the EE 9 web-app_5_0.xsd. > Investigate JSP (Jakarta EE 9 Platform) TCK failures > ---------------------------------------------------- > > Key: WFLY-13837 > URL: https://issues.redhat.com/browse/WFLY-13837 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Labels: EE9 > > I'm not exactly sure yet where the reference to "DTD Web Application 2.2" is coming from in the follow deployment error that occurring during JSP TCK testing: > {quote} > 2020-09-09 16:48:42,512 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "jsp_arrayelresolver_web.war" (runtime-name: "jsp_arrayelresolver_web.war") > 2020-09-09 16:48:42,625 ERROR [org.jboss.metadata.parser.util.XMLSchemaValidator] (MSC service thread 1-1) Cannot get schema for location: -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN: org.xml.sax.SAXParseException; systemId: file:///mnt/hudson_workspace/customWorkspaceName/wildfly/bin/-//Sun%20Microsystems,%20Inc.//DTD%20Web%20Application%202.2//EN; lineNumber: 81; columnNumber: 3; The markup in the document preceding the root element must be well-formed. > at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:201) > at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:175) > at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:398) > at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:325) > at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:282) > at org.apache.xerces.impl.XMLScanner.reportFatalError(XMLScanner.java:1496) > at org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(XMLDocumentScannerImpl.java:784) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:324) > at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(SchemaParsingConfig.java:623) > at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(SchemaParsingConfig.java:679) > at org.apache.xerces.impl.xs.opti.SchemaDOMParser.parse(SchemaDOMParser.java:527) > at org.apache.xerces.impl.xs.traversers.XSDHandler.getSchemaDocument(XSDHandler.java:2168) > at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:558) > at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:580) > at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:547) > at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:513) > at org.apache.xerces.jaxp.validation.XMLSchemaFactory.newSchema(XMLSchemaFactory.java:234) > at javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:638) [rt.jar:1.8.0_191] > at __redirected.__SchemaFactory.newSchema(__SchemaFactory.java:115) [jboss-modules.jar:1.10.2.Final] > at org.jboss.metadata.parser.util.XMLSchemaValidator.getSchemaForLocation(XMLSchemaValidator.java:117) [jboss-metadata-common-14.0.0.Alpha1.jar:14.0.0.Alpha1] > at org.jboss.metadata.parser.util.XMLSchemaValidator.validate(XMLSchemaValidator.java:85) [jboss-metadata-common-14.0.0.Alpha1.jar:14.0.0.Alpha1] > at org.wildfly.extension.undertow.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:117) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_191] > 2020-09-09 16:48:42,631 WARN [org.jboss.metadata.parser.util.XMLSchemaValidator] (MSC service thread 1-1) Cannot get schema for location: -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN > 2020-09-09 16:48:42,896 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=tsharness, specificationVersion=1.4, title=tsharness] referenced from ResourceRoot [root="/content/jsp_arrayelresolver_web.war"] > 2020-09-09 16:48:42,896 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=cts, specificationVersion=1.4, title=cts] referenced from ResourceRoot [root="/content/jsp_arrayelresolver_web.war"] > 2020-09-09 16:48:43,243 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "jsp_arrayelresolver_web.war")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.jsp_arrayelresolver_web.jsp_arrayelresolver_web.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"] > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13842) Upgrade jbossws-cxf to 5.4.2.Final

by Jim Ma (Jira)

[ https://issues.redhat.com/browse/WFLY-13842?page=com.atlassian.jira.plugi... ] Jim Ma updated WFLY-13842: -------------------------- Description: Upgrade jbossws-cxf to 5.4.2.Final and jbossws-common to 3.3.2.Final. > Upgrade jbossws-cxf to 5.4.2.Final > ---------------------------------- > > Key: WFLY-13842 > URL: https://issues.redhat.com/browse/WFLY-13842 > Project: WildFly > Issue Type: Task > Components: Web Services > Affects Versions: 20.0.1.Final > Reporter: Jim Ma > Assignee: Jim Ma > Priority: Major > Fix For: 21.0.0.Beta1 > > > Upgrade jbossws-cxf to 5.4.2.Final and jbossws-common to 3.3.2.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5102) Upgrade Undertow to 2.2.0.Final

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/WFCORE-5102?page=com.atlassian.jira.plug... ] Flavia Rainone updated WFCORE-5102: ----------------------------------- Description: Upgrade Undertow to 2.2.0.Final (was: Upgrade Undertow to 2.1.4.Final) > Upgrade Undertow to 2.2.0.Final > ------------------------------- > > Key: WFCORE-5102 > URL: https://issues.redhat.com/browse/WFCORE-5102 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Bartosz Spyrko-Smietanko > Assignee: Flavia Rainone > Priority: Blocker > Labels: downstream_dependency > Fix For: 13.0.0.Final > > > Upgrade Undertow to 2.2.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5122) Enable TLS 1.3 by default for the WildFly OpenSSL provider

by Jan Stourac (Jira)

[ https://issues.redhat.com/browse/WFCORE-5122?page=com.atlassian.jira.plug... ] Jan Stourac updated WFCORE-5122: -------------------------------- Description: WFCORE-4842 added support for TLS 1.3 for the WildFly OpenSSL provider but left TLS 1.3 disabled by default if no TLS 1.3 cipher suites have been configured by the user. Relevant commit: https://github.com/wildfly/wildfly-core/pull/4271/commits/12c7c83... Once we are ready to do so, we should enable TLS 1.3 by default. was: WFCORE-4842 added support for TLS 1.3 for the WildFly OpenSSL provider but left TLS 1.3 disabled by default if no TLS 1.3 cipher suites have been configured by the user. Once we are ready to do so, we should enable TLS 1.3 by default. > Enable TLS 1.3 by default for the WildFly OpenSSL provider > ---------------------------------------------------------- > > Key: WFCORE-5122 > URL: https://issues.redhat.com/browse/WFCORE-5122 > Project: WildFly Core > Issue Type: Task > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > > WFCORE-4842 added support for TLS 1.3 for the WildFly OpenSSL provider but left TLS 1.3 disabled by default if no TLS 1.3 cipher suites have been configured by the user. > Relevant commit: https://github.com/wildfly/wildfly-core/pull/4271/commits/12c7c83... > Once we are ready to do so, we should enable TLS 1.3 by default. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4789) Enable TLS 1.3 by default for the JSSE provider

by Jan Stourac (Jira)

[ https://issues.redhat.com/browse/WFCORE-4789?page=com.atlassian.jira.plug... ] Jan Stourac updated WFCORE-4789: -------------------------------- Summary: Enable TLS 1.3 by default for the JSSE provider (was: Enable TLS 1.3 by default for JSSE provider) > Enable TLS 1.3 by default for the JSSE provider > ----------------------------------------------- > > Key: WFCORE-4789 > URL: https://issues.redhat.com/browse/WFCORE-4789 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Priority: Major > > WFCORE-4172 added support for TLS 1.3 but left TLS 1.3 disabled by default for reasons described in WFWIP-160: > https://github.com/wildfly/wildfly-core/pull/3815/commits/4ee03bd5662b1fd... > Once we are ready to do so, we should enable TLS 1.3 by default. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4789) Enable TLS 1.3 by default for JSSE provider

by Jan Stourac (Jira)

[ https://issues.redhat.com/browse/WFCORE-4789?page=com.atlassian.jira.plug... ] Jan Stourac updated WFCORE-4789: -------------------------------- Summary: Enable TLS 1.3 by default for JSSE provider (was: Enable TLS 1.3 by default) > Enable TLS 1.3 by default for JSSE provider > ------------------------------------------- > > Key: WFCORE-4789 > URL: https://issues.redhat.com/browse/WFCORE-4789 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Priority: Major > > WFCORE-4172 added support for TLS 1.3 but left TLS 1.3 disabled by default for reasons described in WFWIP-160: > https://github.com/wildfly/wildfly-core/pull/3815/commits/4ee03bd5662b1fd... > Once we are ready to do so, we should enable TLS 1.3 by default. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13860) Upgrade RESTEasy to 3.13.1.Final

by Lucie Cervakova (Jira)

[ https://issues.redhat.com/browse/WFLY-13860?page=com.atlassian.jira.plugi... ] Lucie Cervakova updated WFLY-13860: ----------------------------------- Pool Team: sst_security_special_projects > Upgrade RESTEasy to 3.13.1.Final > -------------------------------- > > Key: WFLY-13860 > URL: https://issues.redhat.com/browse/WFLY-13860 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Ronald Sigal > Assignee: Ronald Sigal > Priority: Major > Labels: downstream_dependency > Fix For: 21.0.0.Beta1 > > > Upgrade from 3.11.2.Final to 3.12.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13860) Upgrade RESTEasy to 3.13.1.Final

by Ronald Sigal (Jira)

Ronald Sigal created WFLY-13860: ----------------------------------- Summary: Upgrade RESTEasy to 3.13.1.Final Key: WFLY-13860 URL: https://issues.redhat.com/browse/WFLY-13860 Project: WildFly Issue Type: Component Upgrade Components: REST Reporter: Ronald Sigal Assignee: Ronald Sigal Fix For: 21.0.0.Beta1 Upgrade from 3.11.2.Final to 3.12.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2020