May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12089) jboss-deployment-structure.xml with fails to parse when annotations=true on a sub-deployment module

by Bartosz Spyrko (Jira)

[ https://issues.jboss.org/browse/WFLY-12089?page=com.atlassian.jira.plugin... ] Bartosz Spyrko moved JBEAP-16922 to WFLY-12089: ----------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12089 (was: JBEAP-16922) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Server (was: Server) Affects Version/s: (was: 7.2.0.GA) (was: 7.1.6.GA) > jboss-deployment-structure.xml with fails to parse when annotations=true on a sub-deployment module > --------------------------------------------------------------------------------------------------- > > Key: WFLY-12089 > URL: https://issues.jboss.org/browse/WFLY-12089 > Project: WildFly > Issue Type: Bug > Components: Server > Reporter: Bartosz Spyrko > Assignee: Bartosz Spyrko > Priority: Major > > Follow up to JBEAP-13094 and JBEAP-14310 > annotations=true on a sub deployment module reference fails to deploy. > This is the same test app from JBEAP-13094, the only change is the api jar is listed as a module in application.xml and then the j-d-s.xml depends on its deployment module. > {code} > <?xml version="1.0" encoding="UTF-8" standalone="no"?> > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> > <sub-deployment name="application-exception-ejb.jar"> > <dependencies> > <module name="deployment.application-exception-api.jar" annotations="true" meta-inf="export"/> > </dependencies> > </sub-deployment> > <sub-deployment name="application-exception-client-singleton.jar"> > <dependencies> > <module name="deployment.application-exception-api.jar" annotations="true" meta-inf="export"/> > </dependencies> > </sub-deployment> > </jboss-deployment-structure> > {code} > {code} > 23:28:46,235 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "application-exception-using-dynamic-module.ear")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.module.service.\"deployment.application-exception-using-dynamic-module.ear.application-exception-api.jar\".main"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > "jboss.deployment.subunit.\"application-exception-using-dynamic-module.ear\".\"application-exception-client-singleton.jar\".PARSE is missing [jboss.module.service.\"deployment.application-exception-using-dynamic-module.ear.application-exception-api.jar\".main]", > "jboss.deployment.subunit.\"application-exception-using-dynamic-module.ear\".\"application-exception-ejb.jar\".PARSE is missing [jboss.module.service.\"deployment.application-exception-using-dynamic-module.ear.application-exception-api.jar\".main]" > ] > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4475) jboss-deployment-structure.xml with fails to parse when annotations=true on a sub-deployment module

by Bartosz Spyrko (Jira)

[ https://issues.jboss.org/browse/WFCORE-4475?page=com.atlassian.jira.plugi... ] Bartosz Spyrko moved WFLY-12089 to WFCORE-4475: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4475 (was: WFLY-12089) Component/s: Server (was: Server) > jboss-deployment-structure.xml with fails to parse when annotations=true on a sub-deployment module > --------------------------------------------------------------------------------------------------- > > Key: WFCORE-4475 > URL: https://issues.jboss.org/browse/WFCORE-4475 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Bartosz Spyrko > Assignee: Bartosz Spyrko > Priority: Major > > Follow up to JBEAP-13094 and JBEAP-14310 > annotations=true on a sub deployment module reference fails to deploy. > This is the same test app from JBEAP-13094, the only change is the api jar is listed as a module in application.xml and then the j-d-s.xml depends on its deployment module. > {code} > <?xml version="1.0" encoding="UTF-8" standalone="no"?> > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> > <sub-deployment name="application-exception-ejb.jar"> > <dependencies> > <module name="deployment.application-exception-api.jar" annotations="true" meta-inf="export"/> > </dependencies> > </sub-deployment> > <sub-deployment name="application-exception-client-singleton.jar"> > <dependencies> > <module name="deployment.application-exception-api.jar" annotations="true" meta-inf="export"/> > </dependencies> > </sub-deployment> > </jboss-deployment-structure> > {code} > {code} > 23:28:46,235 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "application-exception-using-dynamic-module.ear")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.module.service.\"deployment.application-exception-using-dynamic-module.ear.application-exception-api.jar\".main"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > "jboss.deployment.subunit.\"application-exception-using-dynamic-module.ear\".\"application-exception-client-singleton.jar\".PARSE is missing [jboss.module.service.\"deployment.application-exception-using-dynamic-module.ear.application-exception-api.jar\".main]", > "jboss.deployment.subunit.\"application-exception-using-dynamic-module.ear\".\"application-exception-ejb.jar\".PARSE is missing [jboss.module.service.\"deployment.application-exception-using-dynamic-module.ear.application-exception-api.jar\".main]" > ] > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11300) BOM Builder Maven Plugin

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-11300?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-11300: ----------------------------------- Component/s: Build System (was: Quickstarts) > BOM Builder Maven Plugin > ------------------------ > > Key: WFLY-11300 > URL: https://issues.jboss.org/browse/WFLY-11300 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > Client BOMs are painful to maintain manually, and should be replaced by poms creating the BOMs (and installing to maven repo) through a maven plugin, with many similarities with the plugin that builds wildfly's component matrix. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11300) BOM Builder Maven Plugin

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-11300?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-11300: ----------------------------------- Description: BOMs are painful to maintain manually, and should be replaced by poms creating the BOMs (and installing to maven repo) through a maven plugin, with many similarities with the plugin that builds wildfly's component matrix. (was: Client BOMs are painful to maintain manually, and should be replaced by poms creating the BOMs (and installing to maven repo) through a maven plugin, with many similarities with the plugin that builds wildfly's component matrix.) > BOM Builder Maven Plugin > ------------------------ > > Key: WFLY-11300 > URL: https://issues.jboss.org/browse/WFLY-11300 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > BOMs are painful to maintain manually, and should be replaced by poms creating the BOMs (and installing to maven repo) through a maven plugin, with many similarities with the plugin that builds wildfly's component matrix. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11300) BOM Builder Maven Plugin

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-11300?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-11300: ----------------------------------- Summary: BOM Builder Maven Plugin (was: Client BOMs Builder Maven Plugin) > BOM Builder Maven Plugin > ------------------------ > > Key: WFLY-11300 > URL: https://issues.jboss.org/browse/WFLY-11300 > Project: WildFly > Issue Type: Enhancement > Components: Quickstarts > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > Client BOMs are painful to maintain manually, and should be replaced by poms creating the BOMs (and installing to maven repo) through a maven plugin, with many similarities with the plugin that builds wildfly's component matrix. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1810) (Intermittent) stuck start with secmgr after enabling Elytron JACC for undertow/application-security-domain

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1810?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1810: ---------------------------------- Fix Version/s: 1.6.3.CR1 1.9.1.CR1 > (Intermittent) stuck start with secmgr after enabling Elytron JACC for undertow/application-security-domain > ----------------------------------------------------------------------------------------------------------- > > Key: ELY-1810 > URL: https://issues.jboss.org/browse/ELY-1810 > Project: WildFly Elytron > Issue Type: Bug > Components: EE > Affects Versions: 1.6.2.Final, 1.9.0.Final > Reporter: Ondrej Kotek > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.6.3.CR1, 1.9.1.CR1 > > Attachments: Second.txt > > > After enabling JACC on {{undertow/application-security-domain=other}}, the server can get stuck when starting with Security Manager turned on. It stops responding and cannot be terminated by Ctrl-C. > After disabling JACC, or when starting without Security Manager, the server starts as expected. > This behaviour blocks customers that uses JACC with Security Manager. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1810) (Intermittent) stuck start with secmgr after enabling Elytron JACC for undertow/application-security-domain

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1810?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse moved WFLY-12081 to ELY-1810: ---------------------------------------------- Project: WildFly Elytron (was: WildFly) Key: ELY-1810 (was: WFLY-12081) Component/s: EE (was: Security) Affects Version/s: 1.9.0.Final 1.6.2.Final (was: 17.0.0.Alpha1) > (Intermittent) stuck start with secmgr after enabling Elytron JACC for undertow/application-security-domain > ----------------------------------------------------------------------------------------------------------- > > Key: ELY-1810 > URL: https://issues.jboss.org/browse/ELY-1810 > Project: WildFly Elytron > Issue Type: Bug > Components: EE > Affects Versions: 1.9.0.Final, 1.6.2.Final > Reporter: Ondrej Kotek > Assignee: Darran Lofthouse > Priority: Blocker > Attachments: Second.txt > > > After enabling JACC on {{undertow/application-security-domain=other}}, the server can get stuck when starting with Security Manager turned on. It stops responding and cannot be terminated by Ctrl-C. > After disabling JACC, or when starting without Security Manager, the server starts as expected. > This behaviour blocks customers that uses JACC with Security Manager. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3888) rules in spreadsheet does not behave same way with drl.

by Andrej Podhradsky (Jira)

[ https://issues.jboss.org/browse/DROOLS-3888?page=com.atlassian.jira.plugi... ] Andrej Podhradsky closed DROOLS-3888. ------------------------------------- > rules in spreadsheet does not behave same way with drl. > ------------------------------------------------------- > > Key: DROOLS-3888 > URL: https://issues.jboss.org/browse/DROOLS-3888 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 7.18.0.Final > Reporter: Hiroko Miura > Assignee: Mario Fusco > Priority: Major > Labels: support > Fix For: 7.21.0.Final > > > In 7.18.0.Final (RHDM7.3.0), the change introduced by [DROOLS-3523|https://issues.jboss.org/browse/DROOLS-3523] as stated in the following knowledge. > Rules don't fire after upgrading to RHDM 7.3.0 > https://access.redhat.com/solutions/4014541 > Therefore, DroolsTest.java in JBDS Drools sample project does not fire rules as expected. > However, DecisionTableTest.java still works even tough 'packages' attribute in kmodule.xml still specify folder instead of package, which is inconsistent behavior with DRL sample. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3888) rules in spreadsheet does not behave same way with drl.

by Andrej Podhradsky (Jira)

[ https://issues.jboss.org/browse/DROOLS-3888?page=com.atlassian.jira.plugi... ] Andrej Podhradsky updated DROOLS-3888: -------------------------------------- Fix Version/s: 7.21.0.Final > rules in spreadsheet does not behave same way with drl. > ------------------------------------------------------- > > Key: DROOLS-3888 > URL: https://issues.jboss.org/browse/DROOLS-3888 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 7.18.0.Final > Reporter: Hiroko Miura > Assignee: Mario Fusco > Priority: Major > Labels: support > Fix For: 7.21.0.Final > > > In 7.18.0.Final (RHDM7.3.0), the change introduced by [DROOLS-3523|https://issues.jboss.org/browse/DROOLS-3523] as stated in the following knowledge. > Rules don't fire after upgrading to RHDM 7.3.0 > https://access.redhat.com/solutions/4014541 > Therefore, DroolsTest.java in JBDS Drools sample project does not fire rules as expected. > However, DecisionTableTest.java still works even tough 'packages' attribute in kmodule.xml still specify folder instead of package, which is inconsistent behavior with DRL sample. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3888) rules in spreadsheet does not behave same way with drl.

by Andrej Podhradsky (Jira)

[ https://issues.jboss.org/browse/DROOLS-3888?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on DROOLS-3888: ------------------------------------------- Verified with CodeReady Studio IS 12.11.0.GA (contains Drools plugin 7.21.0.Final). All 3 test classes printed the expected output. The classes are * DecisionTableTest * DroolsTest * ProcessTest > rules in spreadsheet does not behave same way with drl. > ------------------------------------------------------- > > Key: DROOLS-3888 > URL: https://issues.jboss.org/browse/DROOLS-3888 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 7.18.0.Final > Reporter: Hiroko Miura > Assignee: Mario Fusco > Priority: Major > Labels: support > Fix For: 7.21.0.Final > > > In 7.18.0.Final (RHDM7.3.0), the change introduced by [DROOLS-3523|https://issues.jboss.org/browse/DROOLS-3523] as stated in the following knowledge. > Rules don't fire after upgrading to RHDM 7.3.0 > https://access.redhat.com/solutions/4014541 > Therefore, DroolsTest.java in JBDS Drools sample project does not fire rules as expected. > However, DecisionTableTest.java still works even tough 'packages' attribute in kmodule.xml still specify folder instead of package, which is inconsistent behavior with DRL sample. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 May 2019