December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14219) Utilize JBoss Modules version 1.8 in module descriptors

by Boris Unckel (Jira)

Boris Unckel created WFLY-14219: ----------------------------------- Summary: Utilize JBoss Modules version 1.8 in module descriptors Key: WFLY-14219 URL: https://issues.redhat.com/browse/WFLY-14219 Project: WildFly Issue Type: Task Components: Server Affects Versions: 22.0.0.Alpha1 Reporter: Boris Unckel Assignee: Brian Stansberry Attachments: 2020-12-13_wildfly-22.0.0.Beta1-SNAPSHOT_modules_15_16_17.txt There are still modules which use 1.5, 1.6 or 1.7 and do not need that. The idea is to run jdeps on each artifact of a modul, add the relevant java.* and jdk.* modules to the dependencies of the module and upgrade to version 1.8. In a first change only none-jdk modules and none which depend on system dependency. List in 2020-12-13_wildfly-22.0.0.Beta1-SNAPSHOT_modules_15_16_17.txt Changes in a first set of modules in WildFly-Core [WFCORE-5229|https://issues.redhat.com/browse/WFCORE-5229] integration tests were successful. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14211) Always clean feature pack modules

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14211?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-14211: ------------------------------------ Issue Type: Enhancement (was: Task) > Always clean feature pack modules > --------------------------------- > > Key: WFLY-14211 > URL: https://issues.redhat.com/browse/WFLY-14211 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > http://maven.apache.org/plugins/maven-clean-plugin/usage.html#Running_the... > ^^^ might be useful for our maven modules that build feature packs. > I often get failed FP builds as i switch from branch to branch and I believe it's because the target dir has stuff left over from a previous build, e.g. layer-spec.xml files etc, that no longer match the current branch. Doing mvn clean install for the whole build is annoying; WF is a huge build. And manually cleaning a few modules is also annoying. But it seems you can turn on a clean as part of the module's own pom. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14211) Always clean feature pack modules

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14211?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-14211: ------------------------------------ Summary: Always clean feature pack modules (was: Always cleaning feature pack modules) > Always clean feature pack modules > --------------------------------- > > Key: WFLY-14211 > URL: https://issues.redhat.com/browse/WFLY-14211 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > http://maven.apache.org/plugins/maven-clean-plugin/usage.html#Running_the... > ^^^ might be useful for our maven modules that build feature packs. > I often get failed FP builds as i switch from branch to branch and I believe it's because the target dir has stuff left over from a previous build, e.g. layer-spec.xml files etc, that no longer match the current branch. Doing mvn clean install for the whole build is annoying; WF is a huge build. And manually cleaning a few modules is also annoying. But it seems you can turn on a clean as part of the module's own pom. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14211) Always cleaning feature pack modules

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14211?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFLY-14211: --------------------------------------- Assignee: Brian Stansberry > Always cleaning feature pack modules > ------------------------------------ > > Key: WFLY-14211 > URL: https://issues.redhat.com/browse/WFLY-14211 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > http://maven.apache.org/plugins/maven-clean-plugin/usage.html#Running_the... > ^^^ might be useful for our maven modules that build feature packs. > I often get failed FP builds as i switch from branch to branch and I believe it's because the target dir has stuff left over from a previous build, e.g. layer-spec.xml files etc, that no longer match the current branch. Doing mvn clean install for the whole build is annoying; WF is a huge build. And manually cleaning a few modules is also annoying. But it seems you can turn on a clean as part of the module's own pom. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5229) Utilize JBoss Modules version 1.8 in module descriptors

by Boris Unckel (Jira)

[ https://issues.redhat.com/browse/WFCORE-5229?page=com.atlassian.jira.plug... ] Boris Unckel updated WFCORE-5229: --------------------------------- Attachment: 2020-12-12_wfcorejdep_14.0.0.Beta5-SNAPSHOT.7z > Utilize JBoss Modules version 1.8 in module descriptors > ------------------------------------------------------- > > Key: WFCORE-5229 > URL: https://issues.redhat.com/browse/WFCORE-5229 > Project: WildFly Core > Issue Type: Task > Components: Modules > Affects Versions: 14.0.0.Beta4 > Reporter: Boris Unckel > Assignee: Richard Opalka > Priority: Major > Attachments: 2020-12-12_wfcorejdep_14.0.0.Beta5-SNAPSHOT.7z > > > There are still modules which use 1.6 or 1.7 and do not need that. The idea is to run jdeps on each artifact of a modul, add the relevant java.* modules to the dependencies of the module and upgrade to version 1.8. In a first only none-jdk modules and none which depend on system dependency. > Full list: > ./system/layers/base/sun/scripting/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="sun.scripting"> > ./system/layers/base/sun/jdk/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="sun.jdk"> > ./system/layers/base/ibm/jdk/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="ibm.jdk"> > ./system/layers/base/io/undertow/core/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="io.undertow.core"> > ./system/layers/base/org/apache/log4j/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.apache.log4j"> > ./system/layers/base/org/apache/commons/logging/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.apache.commons.logging"> > ./system/layers/base/org/fusesource/jansi/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.fusesource.jansi"> > ./system/layers/base/org/slf4j/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.slf4j"> > ./system/layers/base/org/slf4j/impl/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.slf4j.impl"> > ./system/layers/base/org/jboss/stdio/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.stdio"> > ./system/layers/base/org/jboss/jandex/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.jandex"> > ./system/layers/base/org/jboss/vfs/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.vfs"> > ./system/layers/base/org/jboss/staxmapper/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.staxmapper"> > ./system/layers/base/org/jboss/as/domain-http-error-context/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.domain-http-error-context"> > ./system/layers/base/org/jboss/as/core-security-api/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.core-security-api"> > ./system/layers/base/org/jboss/as/version/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.version"> > ./system/layers/base/org/jboss/as/domain-add-user/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.domain-add-user"> > ./system/layers/base/org/jboss/as/management-client-content/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.management-client-content"> > ./system/layers/base/org/jboss/as/deployment-repository/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.deployment-repository"> > ./system/layers/base/org/jboss/as/threads/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.threads"> > ./system/layers/base/org/jboss/as/patching/cli/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.patching.cli"> > ./system/layers/base/org/jboss/as/controller-client/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.controller-client"> > ./system/layers/base/org/jboss/as/standalone/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.standalone"> > ./system/layers/base/org/jboss/logging/jul-to-slf4j-stub/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.logging.jul-to-slf4j-stub"> > ./system/layers/base/org/jboss/logging/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.logging"> > ./system/layers/base/org/jboss/invocation/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.invocation"> > ./system/layers/base/org/jboss/dmr/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.dmr"> > ./system/layers/base/org/wildfly/embedded/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.wildfly.embedded"> > ./system/layers/base/org/wildfly/extension/core-management-client/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.wildfly.extension.core-management-client"> > ./system/layers/base/org/wildfly/security/manager/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.wildfly.security.manager"> > ./system/layers/base/org/wildfly/security/elytron/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.wildfly.security.elytron"> > ./system/layers/base/org/jboss/logging/commons/logging/main/module.xml:<module xmlns="urn:jboss:module:1.7" name="org.jboss.logging.commons.logging"> -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14199) OnOffOpenTracingTestCase leaves the server in a bad state

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14199?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-14199: ----------------------------------------- Thanks, [~jamezp]. This kind of thing seems like an argument for WFCORE-436. Although in general it seems like the basic WF design should allow for stop to be called in any case where some start was called on some type that has a start/stop kind of method pair. It might not be called when application deployment fails during boot, but when the server was reloaded any MSC services that had been started during that failed deployment attempt should have been stopped, allowing cleanup work to happen. And DeploymentUnitPhaseService itself will call undeploy() on any successfully executed DUPs if a subsequent one in its phase fails. Individual MSC services that fail during their own start() method may not be doing cleanup though. > OnOffOpenTracingTestCase leaves the server in a bad state > --------------------------------------------------------- > > Key: WFLY-14199 > URL: https://issues.redhat.com/browse/WFLY-14199 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing, Test Suite > Affects Versions: 22.0.0.Alpha1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > > {color:#333333}OnOffOpenTracingTestCase{color} will leave the server in such a state that SimpleRestClientTestCase will fail. Removing and adding the opentracing subsystem to check that it doesn't work once removed shoudl be reevaluated. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5229) Utilize JBoss Modules version 1.8 in module descriptors

by Boris Unckel (Jira)

Boris Unckel created WFCORE-5229: ------------------------------------ Summary: Utilize JBoss Modules version 1.8 in module descriptors Key: WFCORE-5229 URL: https://issues.redhat.com/browse/WFCORE-5229 Project: WildFly Core Issue Type: Task Components: Modules Affects Versions: 14.0.0.Beta4 Reporter: Boris Unckel Assignee: Richard Opalka There are still modules which use 1.6 or 1.7 and do not need that. The idea is to run jdeps on each artifact of a modul, add the relevant java.* modules to the dependencies of the module and upgrade to version 1.8. In a first only none-jdk modules and none which depend on system dependency. Full list: ./system/layers/base/sun/scripting/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="sun.scripting"> ./system/layers/base/sun/jdk/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="sun.jdk"> ./system/layers/base/ibm/jdk/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="ibm.jdk"> ./system/layers/base/io/undertow/core/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="io.undertow.core"> ./system/layers/base/org/apache/log4j/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.apache.log4j"> ./system/layers/base/org/apache/commons/logging/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.apache.commons.logging"> ./system/layers/base/org/fusesource/jansi/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.fusesource.jansi"> ./system/layers/base/org/slf4j/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.slf4j"> ./system/layers/base/org/slf4j/impl/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.slf4j.impl"> ./system/layers/base/org/jboss/stdio/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.stdio"> ./system/layers/base/org/jboss/jandex/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.jandex"> ./system/layers/base/org/jboss/vfs/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.vfs"> ./system/layers/base/org/jboss/staxmapper/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.staxmapper"> ./system/layers/base/org/jboss/as/domain-http-error-context/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.domain-http-error-context"> ./system/layers/base/org/jboss/as/core-security-api/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.core-security-api"> ./system/layers/base/org/jboss/as/version/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.version"> ./system/layers/base/org/jboss/as/domain-add-user/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.domain-add-user"> ./system/layers/base/org/jboss/as/management-client-content/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.management-client-content"> ./system/layers/base/org/jboss/as/deployment-repository/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.deployment-repository"> ./system/layers/base/org/jboss/as/threads/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.threads"> ./system/layers/base/org/jboss/as/patching/cli/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.patching.cli"> ./system/layers/base/org/jboss/as/controller-client/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.controller-client"> ./system/layers/base/org/jboss/as/standalone/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.as.standalone"> ./system/layers/base/org/jboss/logging/jul-to-slf4j-stub/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.logging.jul-to-slf4j-stub"> ./system/layers/base/org/jboss/logging/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.logging"> ./system/layers/base/org/jboss/invocation/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.invocation"> ./system/layers/base/org/jboss/dmr/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.jboss.dmr"> ./system/layers/base/org/wildfly/embedded/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.wildfly.embedded"> ./system/layers/base/org/wildfly/extension/core-management-client/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.wildfly.extension.core-management-client"> ./system/layers/base/org/wildfly/security/manager/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.wildfly.security.manager"> ./system/layers/base/org/wildfly/security/elytron/main/module.xml:<module xmlns="urn:jboss:module:1.6" name="org.wildfly.security.elytron"> ./system/layers/base/org/jboss/logging/commons/logging/main/module.xml:<module xmlns="urn:jboss:module:1.7" name="org.jboss.logging.commons.logging"> -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14213) Update org.kohsuke.metainf-services 1.8

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14213?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFLY-14213: --------------------------------------- Fix Version/s: 22.0.0.Beta1 Assignee: Boris Unckel (was: Brian Stansberry) Resolution: Done > Update org.kohsuke.metainf-services 1.8 > --------------------------------------- > > Key: WFLY-14213 > URL: https://issues.redhat.com/browse/WFLY-14213 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Affects Versions: 22.0.0.Alpha1 > Reporter: Boris Unckel > Assignee: Boris Unckel > Priority: Major > Fix For: 22.0.0.Beta1 > > Attachments: 2020-12-11_kohsuke_tree.txt > > > Update [metainf-services|https://mvnrepository.com/artifact/org.kohsuke.metainf-s...] > No Release notes published. > [Release-Diff|https://github.com/kohsuke/metainf-services/compare/metainf-...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14177) Update commons-codec 1.15

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14177?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFLY-14177: --------------------------------------- Fix Version/s: 22.0.0.Beta1 Assignee: Boris Unckel (was: Brian Stansberry) Resolution: Done > Update commons-codec 1.15 > ------------------------- > > Key: WFLY-14177 > URL: https://issues.redhat.com/browse/WFLY-14177 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Affects Versions: 22.0.0.Alpha1 > Reporter: Boris Unckel > Assignee: Boris Unckel > Priority: Major > Fix For: 22.0.0.Beta1 > > > Update [Apache commons codec|https://mvnrepository.com/artifact/commons-codec/commons-codec/1.15] > [Release Notes|https://commons.apache.org/proper/commons-codec/changes-report.html...] > [Release-Diff|https://github.com/apache/commons-codec/compare/commons-code...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14162) EE-9 distribution must use jakarta JAXB API & Impl versions

by Jim Ma (Jira)

[ https://issues.redhat.com/browse/WFLY-14162?page=com.atlassian.jira.plugi... ] Jim Ma commented on WFLY-14162: ------------------------------- [~ropalka] Yes. There is regression issue in CXF 3.3.8 : [http://cxf.547215.n5.nabble.com/CXF-8378-Backward-compatible-issue-in-3-4-1-and-3-3-8-td5805386.html] > EE-9 distribution must use jakarta JAXB API & Impl versions > ----------------------------------------------------------- > > Key: WFLY-14162 > URL: https://issues.redhat.com/browse/WFLY-14162 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 22.0.0.Alpha1 > Reporter: Richard Opalka > Assignee: Jim Ma > Priority: Major > Labels: EE9 > > 2020-12-04 10:24:37,138 INFO [stdout] (MSC service thread 1-7) DefaultValidationEventHandler: [ERROR]: unexpected element (uri:"https://jakarta.ee/xml/ns/jakartaee", local:"handler-name"). Expected elements are <\{http://java.sun.com/xml/ns/javaee}display-name>,<\{http://java.sun.com/xml/ns/javaee}init-param>,<\{http://java.sun.com/xml/ns/javaee}soap-role>,<\{http://java.sun.com/xml/ns/javaee}soap-header>,<\{http://java.sun.com/xml/ns/javaee}handler-class>,<\{http://java.sun.com/xml/ns/javaee}icon>,<\{http://java.sun.com/xml/ns/javaee}handler-name>,<\{http://java.sun.com/xml/ns/javaee}description> > 2020-12-04 10:24:37,138 INFO [stdout] (MSC service thread 1-7) Location: node: [handler-name: null] > 2020-12-04 10:24:37,139 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.subunit."WSEjbWSRefAndAddressingCombinedTest.ear"."WSEjbWSRefAndAddressingCombinedTest_ejb.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."WSEjbWSRefAndAddressingCombinedTest.ear"."WSEjbWSRefAndAddressingCombinedTest_ejb.jar".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment "WSEjbWSRefAndAddressingCombinedTest_ejb.jar" of deployment "WSEjbWSRefAndAddressingCombinedTest.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:189) [wildfly-server-14.0.0.Beta3-SNAPSHOT.jar:14.0.0.Beta3-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) [jboss-msc-1.4.12.Final.jar:1.4.12.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) [jboss-msc-1.4.12.Final.jar:1.4.12.Final] > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) [jboss-msc-1.4.12.Final.jar:1.4.12.Final] > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.4.0.Final.jar:2.4.0.Final] > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) [jboss-threads-2.4.0.Final.jar:2.4.0.Final] > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) [jboss-threads-2.4.0.Final.jar:2.4.0.Final] > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) [jboss-threads-2.4.0.Final.jar:2.4.0.Final] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_271] > Caused by: jakarta.xml.ws.WebServiceException: jakarta.xml.ws.WebServiceException: Chain not specified > at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:375) > at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:80) > at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:255) > at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:543) > at org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:236) > at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:97) > at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:59) > at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182) [wildfly-server-14.0.0.Beta3-SNAPSHOT.jar:14.0.0.Beta3-SNAPSHOT] > ... 8 more > Caused by: jakarta.xml.ws.WebServiceException: Chain not specified > at org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilder.buildHandlerChainFromClass(AnnotationHandlerChainBuilder.java:158) > at org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilder.buildHandlerChainFromClass(AnnotationHandlerChainBuilder.java:327) > at org.apache.cxf.jaxws.JaxWsServerFactoryBean.buildHandlerChain(JaxWsServerFactoryBean.java:248) > at org.apache.cxf.jaxws.JaxWsServerFactoryBean.initializeResourcesAndHandlerChain(JaxWsServerFactoryBean.java:227) > at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:212) > at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:460) > at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:338) > ... 16 more > Caused by: java.lang.IllegalArgumentException: Could not unmarshal handler chain > at org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilder.processHandlerElement(AnnotationHandlerChainBuilder.java:313) > at org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilder.processHandlerChainElement(AnnotationHandlerChainBuilder.java:211) > at org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilder.buildHandlerChainFromClass(AnnotationHandlerChainBuilder.java:150) > ... 22 more > Caused by: jakarta.xml.bind.UnmarshalException: unexpected element (uri:"https://jakarta.ee/xml/ns/jakartaee", local:"handler-name"). Expected elements are <\{http://java.sun.com/xml/ns/javaee}display-name>,<\{http://java.sun.com/xml/ns/javaee}init-param>,<\{http://java.sun.com/xml/ns/javaee}soap-role>,<\{http://java.sun.com/xml/ns/javaee}soap-header>,<\{http://java.sun.com/xml/ns/javaee}handler-class>,<\{http://java.sun.com/xml/ns/javaee}icon>,<\{http://java.sun.com/xml/ns/javaee}handler-name>,<\{http://java.sun.com/xml/ns/javaee}description> > at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.handleEvent(UnmarshallingContext.java:713) > at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:232) > at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:227) > at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportUnexpectedChildElement(Loader.java:94) > at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.childElement(Loader.java:75) > at com.sun.xml.bind.v2.runtime.unmarshaller.StructureLoader.childElement(StructureLoader.java:238) > at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext._startElement(UnmarshallingContext.java:543) > at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.startElement(UnmarshallingContext.java:525) > at com.sun.xml.bind.v2.runtime.unmarshaller.InterningXmlVisitor.startElement(InterningXmlVisitor.java:45) > at com.sun.xml.bind.v2.runtime.unmarshaller.SAXConnector.startElement(SAXConnector.java:137) > at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:214) > at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:251) > at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:220) > at com.sun.xml.bind.unmarshaller.DOMScanner.scan(DOMScanner.java:97) > at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:339) > at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:318) > at org.apache.cxf.common.jaxb.JAXBUtils.unmarshall(JAXBUtils.java:203) > at org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilder.processHandlerElement(AnnotationHandlerChainBuilder.java:310) > ... 24 more -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 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 December 2020