Hi Again,
> WDYT about the whole proposal? Good idea?
Yes. It is. Everybody wants it. Me too! :)
> Note this would only be for beans.xml with the version attribute updated to 1.1 so it wouldn't happen without a user actively doing something. They could upgrade to the 1.1 schema, and set auto-discover to all to keep CDI 1.0 behavior (we would make the auto-discover attribute or element required).
With the auto-discover attribute or element required I would be fine
with defaulting it to false!
> Well, say you use Guice or Spring with JSR-330 scope annotations. If we just enable all scope annotations as bean defining annotations, then these would get picked up. If we just did it for scopes that the CDI container knows it has a context for, they wouldn't. This would have no impact on performance, we would still have to scan these classes, but the CDI container can decide they aren't beans when it loads the class.
More clear now to me. I would go with the suggested behavior.
>>> OPEN ISSUE: Should we extend auto-discover in beans.xml to allow complete disablement of scanning e.g. auto-discover="all|bean-defining-annotations-only|none" ?
>>
> IMO it's mainly to do with the first one - keeping the 1.0 scanning model, whilst taking advantage of other 1.1 beans.xml features.
Yes please :)
- M