I expected we would contribute the spec document to the platform
project, just like it was done for Java EE. If the PMC wants to
create a new project just for this, we can contribute the spec
document there instead, but we need to decide soon.
I don't believe there is a standalone TCK, and the API is part of
Common Annotations, so there wouldn't be much in the spec project
other than the spec document itself. And the requirements defined
by the spec really have platform-wide impact, which is why it was
done in the platform project.
arjan tijms wrote on 4/29/19 11:31 AM:
Hi Kevin,
Managed Beans 1.0 is defined in the Java EE 6 spec.
(It's a short document, but quite an interesting read,
as it sets the stage for things we still haven't done yet,
but IMHO should)
Kind regards,
Arjan
Hi,
But, what about the Spec itself? If I look
at the Common Annotations specification, the very first
sentence in section 2.16 indicates...
"The ManagedBean
annotation
is used to declare a Managed Bean as specified in the Managed
Beans specification."
Did we miss this Spec Project when we first
defined them? Or, was it expected to be part of
Common Annotations? There are some rules and
requirements defined the Managed Beans 1.0 spec that
are not part of the Common Annotations 2.16
section...
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
|
