Hopefully Jakarta EE specifications don't need to be one-to-one with
EE4J projects, and the Jakarta EE platform project can produce
multiple specifications. Yes, the project scope needs to cover it.
Kevin Sutter wrote on 4/29/19 12:30 PM:
Hi Arjan,
Yes, so my question is what about Jakarta?
Should this be considered part of the Jakarta Platform
Project? Since it's a separate Specification, do we need to
recognize its existence in one of the Jakarta projects?
Especially as we are considering and finalizing the
Specification Project names and Scopes...
-----
Original message -----
From: arjan tijms <arjan.tijms@xxxxxxxxx>
Sent by: ee4j-pmc-bounces@xxxxxxxxxxx
To: EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Cc:
Subject: Re: [ee4j-pmc] Managed Beans 1.0 ?
Date: Mon, Apr 29, 2019 1:34 PM
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
|
