Marina,
On Mon, Apr 9, 2012 at 7:50 PM, Marina Vatkina <marina.vatkina_at_oracle.com>wrote:
> John,
>
>
> John D. Ament wrote:
>
>> Marina,
>>
>> Yes, thanks for catching me nodding off slightly :-) I don't seem to
>> have access to edit so if you could correct it..
>>
>
> No, I can't edit text that I didn't enter. You should see an "Edit" link
> on the upper right corner of the text area.
I have no edit link on the page. I can edit comments but not description.
I added a comment noting the correction.
>
>
>> The MDB would use this information in pretty much any way it saw fit. It
>> would be able to access both the standard and non-standard activation
>> config properties as defined in the application deployment. The goal would
>> be to provide some level of configuration to an MDB at deployment time.
>>
>
> Hmmm... EJB container doesn't have a notion of a programmatic change to
> the deployment metadata at deployment time. MDB instance will be created
> lazily to handle the message, and MessageDrivenContext will be created at
> that time, so way passed deployment phase...
>
>
Wouldn't be changing deployment metadata, that would be read only. But the
MDB may want to do something based on the properties passed in.
> -marina
>
>>
>> John
>>
>>
>>
>> On Mon, Apr 9, 2012 at 5:30 PM, Marina Vatkina <marina.vatkina_at_oracle.com<mailto:
>> marina.vatkina_at_oracle.**com <marina.vatkina_at_oracle.com>>> wrote:
>>
>> John
>>
>> You meant
>>
>> public List<ActivationConfigProperty>
>> get*Activation***ConfigProperties();
>>
>> Correct?
>>
>> How would the MDB use this information?
>>
>> thanks,
>> -marina
>>
>>
>> John D. Ament wrote:
>>
>> Hello Experts,
>>
>> I raised this JIRA issue, requesting your feedback. I am
>> requesting to have a method added to MessageDrivenContext to
>> allow MDBs to know more about how they are configured in the
>> environment. Please let me know your thoughts.
>>
>> Thanks,
>>
>> John
>>
>>
>>