[JBoss JIRA] (WFLY-3669) Deltaspike deployment fails on wildfly 8.1
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3669?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3669:
------------------------------
Affects Version/s: 8.1.0.Final
> Deltaspike deployment fails on wildfly 8.1
> ------------------------------------------
>
> Key: WFLY-3669
> URL: https://issues.jboss.org/browse/WFLY-3669
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 8.1.0.Final
> Reporter: Paa Kojo Konduah Amos
> Assignee: Jason Greene
>
> on addition of the Deltaspike-core dependency in my pom.xml....wildfly 8.1 fails at deployment time.
> 01:45:08,481 INFO [org.apache.deltaspike.core.util.ProjectStageProducer] (MSC service thread 1-4) Computed the following DeltaSpike ProjectStage: Production
> 01:45:12,813 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."jwi.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."jwi.war".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name dsWindowContext resolves to beans:
> Producer Method [WindowContext] with qualifiers [@Default @Named @Any] declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()],
> Producer Method [WindowContext] with qualifiers [@Default @Named @Any] declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()]
> at org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:134)
> at org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:130)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> ... 3 more
> 01:45:12,824 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "jwi.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jwi.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jwi.war\".WeldStartService: Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name dsWindowContext resolves to beans:
> Producer Method [WindowContext] with qualifiers [@Default @Named @Any] declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()],
> Producer Method [WindowContext] with qualifiers [@Default @Named @Any] declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()]"}}
> 01:45:12,919 INFO [org.jboss.as.server] (ServerService Thread Pool – 28) JBAS018559: Deployed "jwi.war" (runtime-name : "jwi.war")
> 01:45:12,928 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.deployment.unit."jwi.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."jwi.war".WeldStartService: Failed to start service
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-3669) Deltaspike deployment fails on wildfly 8.1
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3669?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3669:
------------------------------
Component/s: CDI / Weld
> Deltaspike deployment fails on wildfly 8.1
> ------------------------------------------
>
> Key: WFLY-3669
> URL: https://issues.jboss.org/browse/WFLY-3669
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 8.1.0.Final
> Reporter: Paa Kojo Konduah Amos
> Assignee: Jason Greene
>
> on addition of the Deltaspike-core dependency in my pom.xml....wildfly 8.1 fails at deployment time.
> 01:45:08,481 INFO [org.apache.deltaspike.core.util.ProjectStageProducer] (MSC service thread 1-4) Computed the following DeltaSpike ProjectStage: Production
> 01:45:12,813 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."jwi.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."jwi.war".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name dsWindowContext resolves to beans:
> Producer Method [WindowContext] with qualifiers [@Default @Named @Any] declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()],
> Producer Method [WindowContext] with qualifiers [@Default @Named @Any] declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()]
> at org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:134)
> at org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:130)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> ... 3 more
> 01:45:12,824 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "jwi.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jwi.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jwi.war\".WeldStartService: Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name dsWindowContext resolves to beans:
> Producer Method [WindowContext] with qualifiers [@Default @Named @Any] declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()],
> Producer Method [WindowContext] with qualifiers [@Default @Named @Any] declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()]"}}
> 01:45:12,919 INFO [org.jboss.as.server] (ServerService Thread Pool – 28) JBAS018559: Deployed "jwi.war" (runtime-name : "jwi.war")
> 01:45:12,928 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.deployment.unit."jwi.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."jwi.war".WeldStartService: Failed to start service
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-3669) Deltaspike deployment fails on wildfly 8.1
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3669?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-3669:
---------------------------------
Assignee: Jozef Hartinger (was: Jason Greene)
> Deltaspike deployment fails on wildfly 8.1
> ------------------------------------------
>
> Key: WFLY-3669
> URL: https://issues.jboss.org/browse/WFLY-3669
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 8.1.0.Final
> Reporter: Paa Kojo Konduah Amos
> Assignee: Jozef Hartinger
>
> on addition of the Deltaspike-core dependency in my pom.xml....wildfly 8.1 fails at deployment time.
> 01:45:08,481 INFO [org.apache.deltaspike.core.util.ProjectStageProducer] (MSC service thread 1-4) Computed the following DeltaSpike ProjectStage: Production
> 01:45:12,813 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."jwi.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."jwi.war".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name dsWindowContext resolves to beans:
> Producer Method [WindowContext] with qualifiers [@Default @Named @Any] declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()],
> Producer Method [WindowContext] with qualifiers [@Default @Named @Any] declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()]
> at org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:134)
> at org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:130)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> ... 3 more
> 01:45:12,824 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "jwi.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jwi.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jwi.war\".WeldStartService: Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name dsWindowContext resolves to beans:
> Producer Method [WindowContext] with qualifiers [@Default @Named @Any] declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()],
> Producer Method [WindowContext] with qualifiers [@Default @Named @Any] declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()]"}}
> 01:45:12,919 INFO [org.jboss.as.server] (ServerService Thread Pool – 28) JBAS018559: Deployed "jwi.war" (runtime-name : "jwi.war")
> 01:45:12,928 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.deployment.unit."jwi.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."jwi.war".WeldStartService: Failed to start service
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-1023) Add Missing Error Counts for Servlets
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1023?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar closed WFLY-1023.
-----------------------------
Resolution: Out of Date
jboss web was replaced with undertow in WildFly 8.
There are bunch of runtime metrics avalibale in it.
If anything is missing please create new jira with what exactly is missing and where.
> Add Missing Error Counts for Servlets
> -------------------------------------
>
> Key: WFLY-1023
> URL: https://issues.jboss.org/browse/WFLY-1023
> Project: WildFly
> Issue Type: Enhancement
> Components: Web (JBoss Web)
> Environment: All applicable environments.
> Reporter: Fernando Ribeiro
> Assignee: Remy Maucherat
>
> Unlike in previous versions of AS, there aren't error counts for each servlet, but only a total in the connector.
> These useful counts were used by many monitoring tools (e.g: RHQ/JON and dynaTrace), and should be available in AS 7 too.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-1023) Add Missing Error Counts for Servlets
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1023?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-1023:
---------------------------------
Assignee: Remy Maucherat (was: Stuart Douglas)
> Add Missing Error Counts for Servlets
> -------------------------------------
>
> Key: WFLY-1023
> URL: https://issues.jboss.org/browse/WFLY-1023
> Project: WildFly
> Issue Type: Enhancement
> Components: Web (JBoss Web)
> Environment: All applicable environments.
> Reporter: Fernando Ribeiro
> Assignee: Remy Maucherat
>
> Unlike in previous versions of AS, there aren't error counts for each servlet, but only a total in the connector.
> These useful counts were used by many monitoring tools (e.g: RHQ/JON and dynaTrace), and should be available in AS 7 too.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-1023) Add Missing Error Counts for Servlets
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1023?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-1023:
------------------------------
Component/s: Web (JBoss Web)
(was: Web (Undertow))
> Add Missing Error Counts for Servlets
> -------------------------------------
>
> Key: WFLY-1023
> URL: https://issues.jboss.org/browse/WFLY-1023
> Project: WildFly
> Issue Type: Enhancement
> Components: Web (JBoss Web)
> Environment: All applicable environments.
> Reporter: Fernando Ribeiro
> Assignee: Stuart Douglas
>
> Unlike in previous versions of AS, there aren't error counts for each servlet, but only a total in the connector.
> These useful counts were used by many monitoring tools (e.g: RHQ/JON and dynaTrace), and should be available in AS 7 too.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-1023) Add Missing Error Counts for Servlets
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1023?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-1023:
---------------------------------
Assignee: Stuart Douglas (was: Remy Maucherat)
> Add Missing Error Counts for Servlets
> -------------------------------------
>
> Key: WFLY-1023
> URL: https://issues.jboss.org/browse/WFLY-1023
> Project: WildFly
> Issue Type: Enhancement
> Components: Web (Undertow)
> Environment: All applicable environments.
> Reporter: Fernando Ribeiro
> Assignee: Stuart Douglas
>
> Unlike in previous versions of AS, there aren't error counts for each servlet, but only a total in the connector.
> These useful counts were used by many monitoring tools (e.g: RHQ/JON and dynaTrace), and should be available in AS 7 too.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-3340) Authentication "module-options" inconsistently hash vs list of key/values
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3340?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-3340:
-----------------------------------
I think this was resolved around 7.2.0 times when whole security subsystem moved to resources instead of complex attributes.
> Authentication "module-options" inconsistently hash vs list of key/values
> -------------------------------------------------------------------------
>
> Key: WFLY-3340
> URL: https://issues.jboss.org/browse/WFLY-3340
> Project: WildFly
> Issue Type: Enhancement
> Components: Domain Management, Security
> Affects Versions: JBoss AS7 7.1.1.Final
> Environment: RHEL 6.4, x86_64
> Reporter: Chris Pitman
> Assignee: Brian Stansberry
> Labels: automation, cli, configuration_management
>
> When adding an authentication mechanism to a security domain it is possible to set the module-options with a hash (which is great!). However, as soon as a reload occurs they revert back into a list of key-value pairs. This only makes sense if order matters (which I hope it doesn't) or if keys can be repeated (again, hope not).
> Configuration management tools should only change a value when it needs to, and this is way easier if the value that is set is the same value that is read. Hashes are also far easier to work with in ruby/puppet/chef.
> Steps to reproduce:
> 1. Set the module_options on an already existing authentication mechanism:
> {code}
> /subsystem=security/security-domain=servlet-security-quickstart/authentication=classic:write-attribute(name=login-modules, value=[{"code" => "Database","flag"=>"required","module-options"=>{"dsJndiName" =>
> "java:jboss/datasources/ServletSecurityDS", "principalsQuery" => "SELECT PASSWORD FROM USERS WHERE USERNAME = ?", "role
> sQuery" => "SELECT R.NAME, 'Roles' FROM USERS_ROLES UR INNER JOIN ROLES R ON R.ID = UR.ROLE_ID INNER JOIN USERS U ON U.ID = UR.USER_ID WHERE U.USERNAME = ?"}}])
> {code}
> 2. Read the resource (notice that module-options is till a nice easy to use hash!)
> {code}
> {
> "outcome" => "success",
> "result" => {"login-modules" => [{
> "module-options" => {
> "dsJndiName" => "java:jboss/datasources/ServletSecurityDS",
> "principalsQuery" => "SELECT PASSWORD FROM USERS WHERE USERNAME = ?",
> "rolesQuery" => "SELECT R.NAME, 'Roles' FROM USERS_ROLES UR INNER JOIN ROLES R ON R.ID = UR.ROLE_ID INNER JOIN USERS U ON U.ID = UR.USER_ID WHERE U.USERNAME = ?"
> },
> "flag" => "required",
> "code" => "Database"
> }]},
> "response-headers" => {"process-state" => "reload-required"}
> }
> {code}
> 3. Reload, then read-resource
> {code}
> {
> "outcome" => "success",
> "result" => {"login-modules" => [{
> "code" => "Database",
> "flag" => "required",
> "module-options" => [
> ("dsJndiName" => "java:jboss/datasources/ServletSecurityDS"),
> ("principalsQuery" => "SELECT PASSWORD FROM USERS WHERE USERNAME = ?"),
> ("rolesQuery" => "SELECT R.NAME, 'Roles' FROM USERS_ROLES UR INNER JOIN ROLES R ON R.ID = UR.ROLE_ID INNER JOIN USERS U ON U.ID = UR.USER_ID WHERE U.USERNAME = ?")
> ]
> }]}
> }
> {code}
> 4. module-options is now a list of key-value pairs, and is not equal to what it was set to before
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-3564) Remove support for mixed-domain transforming to < 7.3.0 versions
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3564?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3564:
------------------------------
Summary: Remove support for mixed-domain transforming to < 7.3.0 versions (was: Remove support for mixed-domain transforming to 7.1.x versions)
> Remove support for mixed-domain transforming to < 7.3.0 versions
> ----------------------------------------------------------------
>
> Key: WFLY-3564
> URL: https://issues.jboss.org/browse/WFLY-3564
> Project: WildFly
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Tomaz Cerar
>
> (Deliberately currently unscheduled as I don't want this to become a priority unless there is clear need.)
> We will not support WF 9 mixed domains with slaves running releases prior to 7.2 (and maybe later) so we should remove the various transformer logic meant to deal with the fact that slaves in those early releases did not provide information about the version of subsystems they are running.
> KnownVersions can go, as can bits of logic that logged warns or errors instead of failing the transformation because the master could not know if the slave was going to ignore the resource.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFLY-3564) Remove support for mixed-domain transforming to < 7.3.0 versions
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3564?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3564:
------------------------------
Description:
(Deliberately currently unscheduled as I don't want this to become a priority unless there is clear need.)
We will not support WF 9 mixed domains with slaves running releases prior to 7.3 / EAP 6.2 (and maybe later) so we should remove the various transformer logic meant to deal with the fact that slaves in those early releases did not provide information about the version of subsystems they are running.
KnownVersions can go, as can bits of logic that logged warns or errors instead of failing the transformation because the master could not know if the slave was going to ignore the resource.
was:
(Deliberately currently unscheduled as I don't want this to become a priority unless there is clear need.)
We will not support WF 9 mixed domains with slaves running releases prior to 7.2 (and maybe later) so we should remove the various transformer logic meant to deal with the fact that slaves in those early releases did not provide information about the version of subsystems they are running.
KnownVersions can go, as can bits of logic that logged warns or errors instead of failing the transformation because the master could not know if the slave was going to ignore the resource.
> Remove support for mixed-domain transforming to < 7.3.0 versions
> ----------------------------------------------------------------
>
> Key: WFLY-3564
> URL: https://issues.jboss.org/browse/WFLY-3564
> Project: WildFly
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Tomaz Cerar
>
> (Deliberately currently unscheduled as I don't want this to become a priority unless there is clear need.)
> We will not support WF 9 mixed domains with slaves running releases prior to 7.3 / EAP 6.2 (and maybe later) so we should remove the various transformer logic meant to deal with the fact that slaves in those early releases did not provide information about the version of subsystems they are running.
> KnownVersions can go, as can bits of logic that logged warns or errors instead of failing the transformation because the master could not know if the slave was going to ignore the resource.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months