December 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11196) The javax.orb.api module's dependencies on the iiop-opendk and transaction subsystem modules should be optional

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11196?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11196: --------------------------------- Fix Version/s: 15.0.0.Final > The javax.orb.api module's dependencies on the iiop-opendk and transaction subsystem modules should be optional > --------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11196 > URL: https://issues.jboss.org/browse/WFLY-11196 > Project: WildFly > Issue Type: Enhancement > Components: IIOP > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > The javax.orb.api module depends on org.wildfly.iiop-openjdk and org.jboss.as.transactions in order to allow the ORB to initialize using classes that the iiop-openjdk subsystem will configure. > But if there is no iiop-openjdk subsystem in the config, then no such configuration will occur. Which means the dependencies are optional. > This is meaningful because javax.orb.api is relatively widely used as an API module, both directly and via the org.omg.api and javax.rmi.api modules that 'wrap' it. When Galleon is trying to provision an optimized footprint server we don't want the mere fact that some required module has an API dependency on one of those to result in a big set of transitive dependencies. Marking the iiop-openjdk and transaction subsystem modules as optional dependencies as such will allow Galleon to decide not to provision them if the config doesn't specify them. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11137) Make undertow extension module's dependency on org.jboss.as.security module optional

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11137?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11137: --------------------------------- Fix Version/s: 15.0.0.Final > Make undertow extension module's dependency on org.jboss.as.security module optional > ------------------------------------------------------------------------------------ > > Key: WFLY-11137 > URL: https://issues.jboss.org/browse/WFLY-11137 > Project: WildFly > Issue Type: Task > Components: Security, Web (Undertow) > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > Don't require the legacy security subsystem module if it's not actually used. > Usage looks like this: > {code} > wildfly bstansberry$ cd undertow/ > undertow bstansberry$ git grep org.jboss.as.security > src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentInfoService.java:import org.jboss.as.security.plugins.SecurityDomainContext; > src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentProcessor.java:import org.jboss.as.security.deployment.AbstractSecurityDeployer; > src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentProcessor.java:import org.jboss.as.security.deployment.SecurityAttachments; > src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentProcessor.java:import org.jboss.as.security.plugins.SecurityDomainContext; > src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentProcessor.java:import org.jboss.as.security.service.JaccService; > src/main/java/org/wildfly/extension/undertow/deployment/UndertowDeploymentProcessor.java:import org.jboss.as.security.service.SecurityDomainService; > src/main/java/org/wildfly/extension/undertow/security/DigestCredentialImpl.java:import org.jboss.as.security.DigestCredential; > src/main/java/org/wildfly/extension/undertow/security/JAASIdentityManagerImpl.java:import org.jboss.as.security.plugins.SecurityDomainContext; > src/main/java/org/wildfly/extension/undertow/security/SecurityContextThreadSetupAction.java:import org.jboss.as.security.plugins.SecurityDomainContext; > src/main/java/org/wildfly/extension/undertow/security/jacc/WarJACCDeployer.java:import org.jboss.as.security.deployment.AbstractSecurityDeployer; > src/main/java/org/wildfly/extension/undertow/security/jacc/WarJACCDeployer.java:import org.jboss.as.security.service.JaccService; > src/main/java/org/wildfly/extension/undertow/security/jacc/WarJACCService.java:import org.jboss.as.security.service.JaccService; > {code} > Dropping the use of SecurityAttachments from UndertowDeploymentProcessor and instead having it check for the presence of the org.wildfly.legacy-security capability will go a long way here. After that, most if not all of the other uses only get called either as a result of that check being true, or some config attribute that directly or indirectly references a security domain. IOW the other uses are only needed if the security subsystem is known to be configured. > Per Intellij, DigestCredentialImpl is unused. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10999) Upgrade Infinispan to 9.4.0.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-10999?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10999: --------------------------------- Fix Version/s: 15.0.0.Final > Upgrade Infinispan to 9.4.0.Final > --------------------------------- > > Key: WFLY-10999 > URL: https://issues.jboss.org/browse/WFLY-10999 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 14.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11104) JCA distributed work manager doesn't allow to add more than one

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11104?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11104: --------------------------------- Fix Version/s: 15.0.0.Final > JCA distributed work manager doesn't allow to add more than one > --------------------------------------------------------------- > > Key: WFLY-11104 > URL: https://issues.jboss.org/browse/WFLY-11104 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Claudio Miranda > Assignee: Stefano Maestri > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > There is an error trying to add a 2nd JCA distributed work manager. > {code} > [standalone@localhost:9990 /] batch > [standalone@localhost:9990 / #] /subsystem=jca/distributed-workmanager=dwm2:add(name=dwm2) > [standalone@localhost:9990 / #] /subsystem=jca/distributed-workmanager=dwm2/short-running-threads=dwm2:add(max-threads=11,queue-length=22) > [standalone@localhost:9990 / #] run-batch > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): > WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed: > Step: step-1 > Operation: /subsystem=jca/distributed-workmanager=dwm2:add(name=dwm2) > Failure: WFLYCTL0436: Cannot register capability > 'org.wildfly.connector.workmanager' at location '[ > ("subsystem" => "jca"), > ("distributed-workmanager" => "dwm2") > ]' as it is already registered in context 'global' at location(s) '[[ > ("subsystem" => "jca"), > ("distributed-workmanager" => "dwm1") > ]]' > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11108) short-running-threads requirement should be verified when distributed workmanager is required

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11108?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11108: --------------------------------- Fix Version/s: 15.0.0.Final > short-running-threads requirement should be verified when distributed workmanager is required > --------------------------------------------------------------------------------------------- > > Key: WFLY-11108 > URL: https://issues.jboss.org/browse/WFLY-11108 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Claudio Miranda > Assignee: Stefano Maestri > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > A distributed-workmanager is allowed to remove its short-running-threads, but it is a required resource to a dwm and once the short-running-threads, Wildfly fails to start the dwm. > To add a distributed-workmanager: > {code} > batch > /subsystem=jca/distributed-workmanager=dwm1:add(name=dwm1) > /subsystem=jca/distributed-workmanager=dwm1/short-running-threads=dwm1:add(max-threads=11,queue-length=22) > run-batch > {code} > Remove the short-running-threads > {code} > /subsystem=jca/distributed-workmanager=dwm1/short-running-threads=dwm1:remove() > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {code} > Then Wildfly fails to reload the dwm > {code} > 12:31:34,497 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "jca"), > ("distributed-workmanager" => "dwm1") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.thread.executor.short-running-threads.dwm1"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.connector.workmanager.dwm1 is missing [jboss.thread.executor.short-running-threads.dwm1]"] > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11199) Upgrade WildFly Core 7.0.0.Alpha4

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11199?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11199: --------------------------------- Fix Version/s: 15.0.0.Final > Upgrade WildFly Core 7.0.0.Alpha4 > --------------------------------- > > Key: WFLY-11199 > URL: https://issues.jboss.org/browse/WFLY-11199 > Project: WildFly > Issue Type: Component Upgrade > Components: Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11113) Update to JAXB 2.3.1

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11113?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11113: --------------------------------- Fix Version/s: 15.0.0.Final > Update to JAXB 2.3.1 > -------------------- > > Key: WFLY-11113 > URL: https://issues.jboss.org/browse/WFLY-11113 > Project: WildFly > Issue Type: Component Upgrade > Components: REST, Web Services > Affects Versions: 14.0.0.Final > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Priority: Major > Labels: Java11 > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > The new release of JAXB should fix some issues with JDK11 (such as warnings WFLY-11044) > Full diff https://github.com/javaee/jaxb-v2/compare/2.3.0...2.3.1 > Note: this release no longer contains jaxb-core artifact which was merged into jaxb-runtime https://github.com/javaee/jaxb-v2/commit/32fda2fbee71c2df04c52fc8eb368769... > Note2: there is a change in dependencies, some of the org.glassfish.jaxb:* artifacts used to depend on relaxngDatatype:relaxngDatatype (which is excluded in WF \[1\],\[2\],\[3\]), now replaced with com.sun.xml.bind.external:relaxng-datatype. WF is using com.github.relaxng:relaxngDatatype instead, not sure, if it is compatible out of the box. > \[1\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L1293-L1298 > \[2\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L3848-L3853 > \[3\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L6728 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11207) Remove link to a constant from java doc

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11207?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11207: --------------------------------- Fix Version/s: 15.0.0.Final > Remove link to a constant from java doc > --------------------------------------- > > Key: WFLY-11207 > URL: https://issues.jboss.org/browse/WFLY-11207 > Project: WildFly > Issue Type: Task > Affects Versions: No Release > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > This task follows up https://issues.jboss.org/browse/WFLY-11137 and fix the java doc where a link to a constant was added. We must use the string name instead. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11215) Quickstart batch-processing uses deprecated methods/types

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11215?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11215: --------------------------------- Fix Version/s: 15.0.0.Final > Quickstart batch-processing uses deprecated methods/types > ---------------------------------------------------------- > > Key: WFLY-11215 > URL: https://issues.jboss.org/browse/WFLY-11215 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Environment: Fedora 27, Red Hat Developer Studio 12.0, jdk 1.8.0_162, 7.2.0.Beta.CR1 EAP/Maven/QS > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > batch-processing quickstart Import results in following warnings: > {noformat} > The method randomAlphabetic(int) from the type RandomStringUtils is deprecated BatchController.java /batch-processing/src/main/java/org/jboss/as/quickstarts/batch/controller line 73 > The method randomNumeric(int) from the type RandomStringUtils is deprecated BatchController.java /batch-processing/src/main/java/org/jboss/as/quickstarts/batch/controller line 74 > The type RandomStringUtils is deprecated BatchController.java /batch-processing/src/main/java/org/jboss/as/quickstarts/batch/controller line 44 > The type RandomStringUtils is deprecated BatchController.java /batch-processing/src/main/java/org/jboss/as/quickstarts/batch/controller line 73 > The type RandomStringUtils is deprecated BatchController.java /batch-processing/src/main/java/org/jboss/as/quickstarts/batch/controller line 74 > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11216) Quickstarts: deprecated Hibernate annotations

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11216?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11216: --------------------------------- Fix Version/s: 15.0.0.Final > Quickstarts: deprecated Hibernate annotations > --------------------------------------------- > > Key: WFLY-11216 > URL: https://issues.jboss.org/browse/WFLY-11216 > Project: WildFly > Issue Type: Enhancement > Components: Quickstarts > Environment: openjdk 11 2018-09-25 > OpenJDK Runtime Environment 18.9 (build 11+28) > OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode) > Red Hat Developer Studio 12.0.0.GA > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > While importing to Red Hat Developer Studio the following quickstarts: > * bean-validation > * contacts-jquerymobile > * hibernate > * kitchensink > * kitchensink-angularjs > * kitchensink-ear > * kitchensink-jsp > * kitchensink-ml > * spring-kitchensink-basic > have the following warnings: > {noformat} > The type Email is deprecated (org.hibernate.validator.constraints.Email) > The type NotEmpty is deprecated (org.hibernate.validator.constraints.NotEmpty) > {noformat} > Used software versions are in the issue environment section. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 2018