Although there is no container specific properties, you should be able
to use deployment plans to further configuration an application at
deployment time. You should be able to find information about deployment
plans in our docs.
Sahoo
On Friday 11 January 2013 06:17 AM, Marina Vatkina wrote:
> No. There is no such option.
>
> -marina
>
> On 1/10/13 7:21 AM, Comerford, Sean wrote:
>> So I gather in ejb.jar.xml I can specify metadata-complete="true" and
>> it will ignore the annotations and only look at the descriptor –
>> thanks for that.
>>
>> Follow up question though:
>>
>> Is there a way at the container level to define a particular MDB
>> inside of our app should be disabled?
>>
>> Our scenario is that we have a generic basketball-messaging app built
>> from a single Maven project.
>>
>> We have 3 separate GF instances for NBA, WNBA and NCB (college bball)
>> that we deploy this application to.
>>
>> But WNBA and NCB don't need a few of the MDBs that NBA uses.
>>
>> Rather than repackage the app we'd like to just environmentally
>> disable the irrelevant MDBs.
>>
>> Is there a way to do that via container managed properties to disable
>> a particular MDB?
>>
>> ---
>> Sean Comerford
>> ESPN.com Architecture & Platforms
>>
>>
>> From: Sean Comerford <Sean.Comerford_at_espn.com
>> <mailto:Sean.Comerford_at_espn.com>>
>> Date: Tue, 8 Jan 2013 11:10:07 -0500
>> To: "sanjeeb.sahoo_at_oracle.com <mailto:sanjeeb.sahoo_at_oracle.com>"
>> <sanjeeb.sahoo_at_oracle.com <mailto:sanjeeb.sahoo_at_oracle.com>>,
>> "users_at_glassfish.java.net <mailto:users_at_glassfish.java.net>"
>> <users_at_glassfish.java.net <mailto:users_at_glassfish.java.net>>
>> Subject: Re: Any way to disable @MessageDriven bean?
>>
>> 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
>>>
>>
>