I think it wouldn't hurt to add this, although I would expect
readers to infer it from Table 16.
thanks,
-Linda
On 9/24/15 1:03 PM, Tracy Burroughs wrote:
> The 15.5.2 re-write includes the following exception "or its version is
> prior to web-app_2_5"; shouldn't the section 15.5.1 include a similar
> exclusion for the scenario where ejb-jar.xml is prior to version 3.0?
>
> Typically, when the ejb-jar.xml is present and has a version of 2.1 or
> earlier the application was written at a time prior to the introduction
> of annotations. As applications are migrated to servers supporting later
> levels of Java EE, requiring any annotation scanning of such modules
> will at best result in only a performance degradation during deployment,
> and in the worst case could cause changes in application behavior and
> various failures.... if the scanning happens to find a previously
> ignored annotations.
>
> Thanks,
>
>
> -- Tracy Burroughs (tkb_at_us.ibm.com)
> -- WebSphere Application Server Development
> -- IBM Rochester, Dept WG8A C201/030-2
> -- 3605 Hwy 52 North, Rochester MN 55901-7899
>
>
> Inactive hide details for Linda DeMichiel ---09/24/2015 02:36:48
> PM---Greetings, I just circulated this note to the Java EE PlaLinda
> DeMichiel ---09/24/2015 02:36:48 PM---Greetings, I just circulated this
> note to the Java EE Platform Expert
>
> From: Linda DeMichiel <linda.demichiel_at_oracle.com>
> To: jsr345-experts_at_ejb-spec.java.net
> Date: 09/24/2015 02:36 PM
> Subject: [jsr345-experts] Fwd: semantics of metadata-complete
>
> ------------------------------------------------------------------------
>
>
>
> Greetings,
>
> I just circulated this note to the Java EE Platform Expert
> Group regarding clarifications that need to be made to the
> Java EE 8 and EJB specs with regard to the semantics of the
> metadata-complete attribute.
>
> While we are not planning a new EJB JSR for Java EE 8, it is
> likely that we will need a small maintenance release to
> address consistency with regard to planned enhancements to
> other specs. The proposed clarifications appended here would
> be part of that update.
>
> Please review and let me know if you see any problems.
>
> thanks,
>
> -Linda
>
>
>
> -------- Original Message --------
> Subject: semantics of metadata-complete
> Date: Thu, 24 Sep 2015 12:28:42 -0700
> From: Linda DeMichiel <linda.demichiel_at_oracle.com>
> Organization: Oracle Corporation
> To: jsr366-experts_at_javaee-spec.java.net
>
> One of the items that needs to be made clearer in our specs is the
> meaning of a "true" value for the metadata-complete attribute, as we
> have noticed that people seem to get confused as to its exact meeting
> with regard to annotation scanning.
>
> The intent here is not to not process all annotations, but rather to
> not process those annotations that are covered by the metadata of the
> deployment descriptors that specify metadata-complete.
>
> I've attached below proposed clarifications for the Java EE 8 Platform
> spec, which covers the application client descriptor, as well as for
> the EJB spec, with the goal of making this more precise. We are also
> planning similar clarifications for the Servlet spec.
>
> Please let me know if you see any problems.
>
> thanks,
>
> -Linda
>
>
>
>
>
> [attachment "metadata-complete-appclients" deleted by Tracy
> Burroughs/Rochester/IBM] [attachment "metadata-complete-ejb" deleted by
> Tracy Burroughs/Rochester/IBM]
>