Andrew Rouse

What are you trying to fix by adding this? I don't see an explanation of the problem or a linked issue.

Thanks @Ladicek for the explanation on the call. As I understand it now: With portable extensions, you can create a synthetic bean by implementing [`Bean`][bean-t] which also allows you to...

Users can also obtain the injection point via: - `Bean.getInjectionPoints()` - injecting `InjectionPoint` into a dependent-scoped bean If we allow synthetic beans to have an `InjectionPoint` with a `null` member,...

From doing a bit of reading, canonical is supposed to point to the "best" link for the page. It seems fairly clear that canonical shouldn't link to a page with...

We discussed this on the CDI weekly call two weeks ago and came up with quite a few issues. I'll write up what I remember, if anyone else has any...

> If the injection point represents a dynamically obtained instance, the getType() and getQualifiers() methods should return the required type (as defined by Instance.select()), and required qualifiers of the injection...

Actually reading the spec for [Injection point metadata][ip-metadata] again, I think it's fairly clear that it's expected that you get a different `InjectionPoint` for the `Instance` itself and for the...

From a technical point of view I don't think a clarification is _needed_, but if we can find a way of making it easier to read and understand, I think...

Yeah, I agree that we should state that a stereotype is a bean defining annotation in that description. It's sort of implied by the fact you can set a default...

That issue does raise a point that I was thinking about: in some circumstances `@Priority` might already have a meaning when applied to a class. For example, it applies a...