Emmanuel (and anyone), WDYT about going back to not having the embedded broker in the OOTB configs in WildFly Preview 27? (Or perhaps 28.) It got restored this summer during the big-bang work in order to make that work easier, but not having it OOTB in WFP was a conscious decision about how we thought forward-looking users should look at things. (Using the embedded broker was still possible, with an example config to illustrate how to set it up; it just wasn't in the standard configs.) We've never done a .Final WFP release with an embedded broker in the standard configs, so if we think we shouldn't have that it's better IMHO to get rid of it before WF 27 Final. I *think* removing it again would be pretty straightforward. The biggest pain associated with not having it was needing to exclude a lot of tests when WFP was used, but I think those exclusions are mostly still there. There's a JIRA for this (https://issues.redhat.com/browse/WFLY-16714) that I've just now scheduled for 27.0.0.Final. That scheduling is just so it appears on my radar screen for WF 27; it's not a demand that we do it. Best regards, Brian

Makes sense to me thanks for the info On Thu, 13 Oct 2022 at 17:05, Brian Stansberry < brian.stansberry(a)redhat.com&gt; wrote: > It seems Emmanuel thinks we should do this. > > https://github.com/wildfly/wildfly/pull/16166 > > ;-) > > On Tue, Oct 11, 2022 at 11:58 AM Brian Stansberry < > brian.stansberry(a)redhat.com&gt; wrote: > >> Emmanuel (and anyone), >> >> WDYT about going back to not having the embedded broker in the OOTB >> configs in WildFly Preview 27? (Or perhaps 28.) It got restored this summer >> during the big-bang work in order to make that work easier, but not having >> it OOTB in WFP was a conscious decision about how we thought >> forward-looking users should look at things. (Using the embedded broker was >> still possible, with an example config to illustrate how to set it up; it >> just wasn't in the standard configs.) >> >> We've never done a .Final WFP release with an embedded broker in the >> standard configs, so if we think we shouldn't have that it's better IMHO to >> get rid of it before WF 27 Final. >> >> I *think* removing it again would be pretty straightforward. The biggest >> pain associated with not having it was needing to exclude a lot of tests >> when WFP was used, but I think those exclusions are mostly still there. >> >> There's a JIRA for this (https://issues.redhat.com/browse/WFLY-16714) >> that I've just now scheduled for 27.0.0.Final. That scheduling is just so >> it appears on my radar screen for WF 27; it's not a demand that we do it. >> >> Best regards, >> Brian >> > > > -- > Brian Stansberry > Principal Architect, Red Hat JBoss EAP > He/Him/His >