December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14166) Upgrade WildFly Core to 14.0.0.Beta3

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-14166?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFLY-14166: ------------------------------- Component/s: Management (was: Server) > Upgrade WildFly Core to 14.0.0.Beta3 > ------------------------------------ > > Key: WFLY-14166 > URL: https://issues.redhat.com/browse/WFLY-14166 > Project: WildFly > Issue Type: Component Upgrade > Components: Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > > Dev tag: https://github.com/wildfly/wildfly-core/releases/tag/14.0.0.Beta2 > Diff to previous integrated release: https://github.com/wildfly/wildfly-core/compare/14.0.0.Beta1...14.0.0.Beta2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14166) Upgrade WildFly Core to 14.0.0.Beta3

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-14166?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFLY-14166: ------------------------------- Reporter: Jeff Mesnil (was: Lin Gao) > Upgrade WildFly Core to 14.0.0.Beta3 > ------------------------------------ > > Key: WFLY-14166 > URL: https://issues.redhat.com/browse/WFLY-14166 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Labels: downstream_dependency > Fix For: 22.0.0.Beta1 > > > Dev tag: https://github.com/wildfly/wildfly-core/releases/tag/14.0.0.Beta2 > Diff to previous integrated release: https://github.com/wildfly/wildfly-core/compare/14.0.0.Beta1...14.0.0.Beta2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14166) Upgrade WildFly Core to 14.0.0.Beta3

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-14166?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFLY-14166: ------------------------------- Fix Version/s: (was: 22.0.0.Beta1) > Upgrade WildFly Core to 14.0.0.Beta3 > ------------------------------------ > > Key: WFLY-14166 > URL: https://issues.redhat.com/browse/WFLY-14166 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Labels: downstream_dependency > > Dev tag: https://github.com/wildfly/wildfly-core/releases/tag/14.0.0.Beta2 > Diff to previous integrated release: https://github.com/wildfly/wildfly-core/compare/14.0.0.Beta1...14.0.0.Beta2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14166) Upgrade WildFly Core to 14.0.0.Beta3

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-14166?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFLY-14166: ------------------------------- Labels: (was: downstream_dependency) > Upgrade WildFly Core to 14.0.0.Beta3 > ------------------------------------ > > Key: WFLY-14166 > URL: https://issues.redhat.com/browse/WFLY-14166 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > > Dev tag: https://github.com/wildfly/wildfly-core/releases/tag/14.0.0.Beta2 > Diff to previous integrated release: https://github.com/wildfly/wildfly-core/compare/14.0.0.Beta1...14.0.0.Beta2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14166) Upgrade WildFly Core to 14.0.0.Beta3

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-14166: ---------------------------------- Summary: Upgrade WildFly Core to 14.0.0.Beta3 Key: WFLY-14166 URL: https://issues.redhat.com/browse/WFLY-14166 Project: WildFly Issue Type: Component Upgrade Components: Server Reporter: Lin Gao Assignee: Jeff Mesnil Fix For: 22.0.0.Beta1 Dev tag: https://github.com/wildfly/wildfly-core/releases/tag/14.0.0.Beta2 Diff to previous integrated release: https://github.com/wildfly/wildfly-core/compare/14.0.0.Beta1...14.0.0.Beta2 -- 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 Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14162?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-14162: ------------------------------------ Labels: EE9 (was: ) > 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

[Red Hat JIRA] (WFLY-14033) app-client unable to inject EJB unless also deployed locally to app client process

by Ivo Studensky (Jira)

[ https://issues.redhat.com/browse/WFLY-14033?page=com.atlassian.jira.plugi... ] Ivo Studensky reassigned WFLY-14033: ------------------------------------ Assignee: (was: Ivo Studensky) According to Darran's plan this involves a lot of refactoring so I am getting it back to Unassigned for the moment. > app-client unable to inject EJB unless also deployed locally to app client process > ---------------------------------------------------------------------------------- > > Key: WFLY-14033 > URL: https://issues.redhat.com/browse/WFLY-14033 > Project: WildFly > Issue Type: Bug > Components: Application Client > Reporter: Darran Lofthouse > Priority: Major > Fix For: 22.0.0.Beta1 > > > The current app-client quickstart uses a single ear for both server side and client side, this did not make sense as it means the EJBs are also deployed to the client process even though the client process is invoking remote EJBs exclusively. > I have attempted some refactoring to make the quickstart clearer so users can see the server side requirement and the client side requirement: > https://github.com/darranl/wildfly-quickstart/tree/WFLY-14027 > The problem is starting app-client now fails with this error: > {code} > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0406: No EJB found with interface of type 'org.jboss.as.quickstarts.appclient.server.api.StatelessSession' for binding org.jboss.as.quickstarts.appclient.acc.client.Main/slsb > at org.jboss.as.ejb3.deployment.processors.EjbInjectionSource.getResourceValue(EjbInjectionSource.java:90) > at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.addJndiBinding(ModuleJndiBindingProcessor.java:271) > at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:242) > at org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:54) > at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:246) > at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:160) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182) [wildfly-server-14.0.0.Beta1.jar:14.0.0.Beta1] > ... 8 more > {code} > This feels as though the injection should either be a proxy which has not yet connected to the remote process or should connect to the remote process first to identify the available beans. > The reason for delayed connection may be to enable authentication before the application uses the EJBs but deploying server side components on the client doesn't feel like the correct solution. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5216) EAP Pod fails to start when env JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} is set

by Ivo Studensky (Jira)

[ https://issues.redhat.com/browse/WFCORE-5216?page=com.atlassian.jira.plug... ] Ivo Studensky moved JBEAP-20654 to WFCORE-5216: ----------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-5216 (was: JBEAP-20654) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Scripts (was: OpenShift) Affects Version/s: (was: 7.3.1.GA) Fix Version/s: (was: 7.3.5.GA) > EAP Pod fails to start when env JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} is set > ------------------------------------------------------------------------------------- > > Key: WFCORE-5216 > URL: https://issues.redhat.com/browse/WFCORE-5216 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > > Since JBoss EAP 7.3 for OpenShift, if environment variable JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} which contains bash variable is set via DeploymentConfig, EAP Pod fails to start with the following messages: > {noformat} > INFO Duration: 347 milliseconds > ERROR Error applying /tmp/cli-configuration-script-1594252654.cli CLI script. > org.jboss.modules.ModuleNotFoundException: org.jboss.as.cli > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:297) > at org.jboss.modules.Main.main(Main.java:371) > {noformat} > This issue does not occur on JBoss EAP 7.2 container. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14165) Move the EE 9 EJB API spec jar to the final 4.0.0 release

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14165?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-14165: ------------------------------------ Labels: EE9 (was: ) > Move the EE 9 EJB API spec jar to the final 4.0.0 release > --------------------------------------------------------- > > Key: WFLY-14165 > URL: https://issues.redhat.com/browse/WFLY-14165 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Labels: EE9 > > jakarta.ejb:jakarta.ejb-api:4.0.0 is now available in maven central. Move to it from 4.0.0-RC2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5877) Support MVEL BLiteral in the exec model

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5877?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5877: --------------------------------- Description: It seems like it's already supported in the consequence [https://github.com/kiegroup/drools/blob/6408b5e1caa1e5c5fe94e45f82e1bedfb...] {code:java} @Test public void prova() { final String str = "global java.util.List list\n" + "import " + Person.class.getCanonicalName() + ";" + "rule R when\n" + "$p1 : Person(age >= 18B)" + "then\n" + " System.out.println($p1);" + "end\n"; KieSession ksession = getKieSession( str ); List<String> results = new ArrayList<>(); ksession.setGlobal("list", results); ksession.insert( new Person( "Mark", 37 ) ); ksession.insert( new Person( "Edson", 35 ) ); ksession.insert( new Person( "Mario", 40 ) ); ksession.fireAllRules(); }{code} was: {code:java} @Test public void prova() { final String str = "global java.util.List list\n" + "import " + Person.class.getCanonicalName() + ";" + "rule R when\n" + "$p1 : Person(age >= 18B)" + "then\n" + " System.out.println($p1);" + "end\n"; KieSession ksession = getKieSession( str ); List<String> results = new ArrayList<>(); ksession.setGlobal("list", results); ksession.insert( new Person( "Mark", 37 ) ); ksession.insert( new Person( "Edson", 35 ) ); ksession.insert( new Person( "Mario", 40 ) ); ksession.fireAllRules(); }{code} > Support MVEL BLiteral in the exec model > --------------------------------------- > > Key: DROOLS-5877 > URL: https://issues.redhat.com/browse/DROOLS-5877 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > It seems like it's already supported in the consequence > > [https://github.com/kiegroup/drools/blob/6408b5e1caa1e5c5fe94e45f82e1bedfb...] > > > {code:java} > @Test > public void prova() { > final String str = > "global java.util.List list\n" + > "import " + Person.class.getCanonicalName() + ";" + > "rule R when\n" + > "$p1 : Person(age >= 18B)" + > "then\n" + > " System.out.println($p1);" + > "end\n"; > KieSession ksession = getKieSession( str ); > List<String> results = new ArrayList<>(); > ksession.setGlobal("list", results); > ksession.insert( new Person( "Mark", 37 ) ); > ksession.insert( new Person( "Edson", 35 ) ); > ksession.insert( new Person( "Mario", 40 ) ); > ksession.fireAllRules(); > }{code} -- 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