One additional note: if the metadata-complete attribute is set to true,
the annotation processing will be skipped completely for that module
where the standard deployment descriptor is packaged in. There is
currently no mechanism to selectively skip annnotation processing for
certain classes of a module.
On 1/8/2013 11:16 AM, Sahoo wrote:
> All deployment descriptor schemas starting with Java EE 5 have it as
> an attribute in top level element. e.g., ejb-jar, web-app, etc.
>
> Sahoo
> On Tuesday 08 January 2013 09:40 PM, Comerford, Sean wrote:
>> By DD I assume you mean deployment descriptor?
>>
>> And if so dumb question – which one? I don't see metadata-complete as
>> a valid attr / element in any of the relevant descriptor XSDs I can
>> think of.
>>
>> ---
>> Sean Comerford
>> ESPN.com Architecture & Platforms
>>
>>
>> From: Sahoo <sanjeeb.sahoo_at_oracle.com <mailto:sanjeeb.sahoo_at_oracle.com>>
>> Reply-To: "sanjeeb.sahoo_at_oracle.com
>> <mailto:sanjeeb.sahoo_at_oracle.com>" <sanjeeb.sahoo_at_oracle.com
>> <mailto:sanjeeb.sahoo_at_oracle.com>>
>> Date: Tue, 8 Jan 2013 10:55:58 -0500
>> To: "users_at_glassfish.java.net <mailto:users_at_glassfish.java.net>"
>> <users_at_glassfish.java.net <mailto:users_at_glassfish.java.net>>
>> Cc: Sean Comerford <Sean.Comerford_at_espn.com
>> <mailto:Sean.Comerford_at_espn.com>>
>> Subject: Re: Any way to disable @MessageDriven bean?
>>
>> You can specify metadata-complete=true in DD xml and list all the
>> required MDBs there along with all other descriptors.
>>
>> Sahoo
>> On Tuesday 08 January 2013 08:55 PM, Comerford, Sean wrote:
>>> We have a number of message driven MDB applications – basically one
>>> per sport.
>>>
>>> All of them extend a set of "common" MDBs that are in theory
>>> applicable for all sports.
>>>
>>> But of course we've found some of these are NOT always common.
>>>
>>> Is there a way to disable (via deployment descriptor) a bean
>>> annotated with @MessageDriven?
>>>
>>> ---
>>> Sean Comerford
>>> ESPN.com Architecture & Platforms
>>>
>>
>