Removing global exclusion

[Turini]

this is a pain in the head! For some reason users like to use util package:
br.com.caelum.vraptor.util for tests, and since CDI 1.1 global activation
our exclusions affects users app, we're always getting this question. Users
shouldn't use vraptor packages, but this is just an simple way to avoid it.

[garcia-jj]

By spec, beans.xml affects only your own jar. So if we declare this exclusion, users can use util package in their app that won't excluded.

But I don't have to link to spec because I'm on cellphone. But I remember to read about this.

I'm not sure right now.

[Turini]

It was changed on CDI 1.1's spec, with beans.xml global activation.

[garcia-jj]

I think that this pull request is really good because Vetoed is more clear to understand than a xml configuration. So it's too right to merge.

But I'm curious about this behaviour. I didn't see in the spec about global activation, only about "automatically discovery beans". There is no any chapter saying that an exclusion in out beans.xml will propagate to all applications. So I did this exactly test, and works as expected: exclusions in vraptor beans.xml won't propagated to other jars.

But as I said before: I love this pull request, because Vetoed is more beautful than xml config.

⛵

[Turini]

I think that this pull request is really good because Vetoed is more
clear to understand than a xml configuration

Indeed. It makes explicitly that the annotated class isn't managed.

There is no any chapter saying that an exclusion in out beans.xml

This is true! I've sent an email (i couldn't find the link right now) and
the answer was that there is a lot of undocumented things in CDI 1.1
that will became clear on CDI 2.0 (manly on events features, etc...)

So I did this exactly test, and works as expected: exclusions in
vraptor beans.xml won't propagated to other jars.

There is kinda 10 issues opened at our online courses saying the
opposite :) but this is because you've tested on app server, right?
Somehow the behaviour change when using an servlet container

[garcia-jj]

This is true! I've sent an email [...]

What the people involved with spec said about the issue? Exclusions are global or not?

And yes, I'm using Wildfly with EAR app. I'm too sad because this is not the first thing that works differently between managed and not managed apps. Too bad.

[Turini]

What the people involved with spec said about the issue? Exclusions are global or not?

I didn't get an answer for this question, just the comment: "there's a lot of undocumented things [...]". At the time I've accepted it as an "yes, this is global". But I didn't know that the behavior was different on app servers. If you want, you can open a new thread on spec mailing list about it

this is not the first thing that works differently between managed and not managed apps

definitively