[wildfly-dev] Component error ids change

[Brian Stansberry]

IMHO WildFly is not responsible for the message codes of components it
consumes.

If Artemis had two messages with the same code, and it changed the code for
one to correct the duplication, there's nothing wrong with that. WildFly
doesn't guarantee bug-for-bug compatibility across releases so I don't see
why Artemis should.

If it took a code and re-used it for some other message unrelated to its
previous use(s), well that's not good but IMO not something WF can try and
correct.

If it completely reworked its message code scheme, well we did too in WF 8.
And again not something we can try and correct.


On Fri, Oct 26, 2018 at 8:13 AM, Emmanuel Hugonnet <ehugonne at redhat.com>
wrote:

> Hello,
>
> I'm looking to use the Apache Artemis upstream 2.6.x branch as a component
> for WildFly. The error ids have changed because of some
> duplication cf. [1]).
>
> Is it ok for those ids to change ? Do we have to manage that change at the
> subsystem level ?
>
> Cheers,
>
> Emmanuel
>
>
> [1]: https://issues.apache.org/jira/browse/ARTEMIS-1018
>
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>



-- 
Brian Stansberry
Manager, Senior Principal Software Engineer
Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20181026/f24a6258/attachment.html