-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relax the scope requirement for public fields #496
Relax the scope requirement for public fields #496
Conversation
61bdd60
to
71942ea
Compare
@Ladicek shouldn't we add a test that verifies this for |
We could, but it's not like we can ever be exhaustive. For normal scopes, we only test |
True, I only mentioned this as it is a notable difference from previous version of specification. |
I could add a test for OK, I will do it :-) |
This is a TCK counterpart to the specification change that allows all pseudo-scoped beans to have public fields. It updates the text in `tck-audit-cdi.xml` files, fixes naming in the relevant tests and adds a test that a `@Singleton` bean can have a public field.
71942ea
to
b52a23d
Compare
Done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you and sorry for the bother :)
This is a TCK counterpart to the specification change that allows all pseudo-scoped beans to have public fields. It updates the text in
tck-audit-cdi.xml
files, fixes naming in the relevant tests and adds a test that a@Singleton
bean can have a public field.