Hi, Matej,

So, let's say we go with your comment above. Now let's say we want to have 200 instances in a cluster. Are you proposing we create 200 groups? Sounds like something very hack-y and workaround-y that we don't want to do.

In any case, your solution only works because two different versions of the app with the same "runtime deployment name" is artificially isolated in a group that contains only one app.

Payara/GlassFish have always had a way to set a "runtime name" for a WAR, but they have to be unique per management domain, thus doesn't really help me any.

Besides, all of this is a moot point, as you don't only want Weld to work properly only in WildFly with one (hack) group per clustered instance.
My solution is very easy, and it doesn't have any sideffects, and has a very valid use case.