[
https://issues.jboss.org/browse/WFLY-5621?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-5621:
----------------------------------------
-jboss-as-messaging_x_y.xsd (server configuration files, replaced by
"wildfly-messaging-activemq_1_0.xsd").
This schema is still usable, both in a domain where some slaves can be running earlier
releases, and to launch a standalone server in --admin-only mode and then use the migrate
op.
If the a - jmx.xml using jboss-as-messaging-deployment_1_0.xsd doesn't work any more,
I agree it should be dropped.
Cleanup HornetQ xsd files in "docs/schema" directory
----------------------------------------------------
Key: WFLY-5621
URL:
https://issues.jboss.org/browse/WFLY-5621
Project: WildFly
Issue Type: Bug
Components: Server
Affects Versions: 10.0.0.CR4
Reporter: Wolfgang Knauf
Assignee: Jason Greene
Priority: Minor
The download zip for WildFly 10.0CR4 contains the xsd files for HornetQ messaging
configurations in "docs/schema". Those are obsoleted by ActiveMQ and should be
removed.
-jboss-as-messaging-deployment_1_0.xsd (deployment of a "-jms.xml" file
according to this old schema will fail with an error anyway), replaced by
"wildfly-messaging-activemq-deployment_1_0.xsd")
-jboss-as-messaging_x_y.xsd (server configuration files, replaced by
"wildfly-messaging-activemq_1_0.xsd").
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)