I think it's not a well known feature and it suffers somewhat from us not having
a standard deployment tool. Presumably all vendors support it since it's a spec
requirement, but since they all probably do it differently it's hard to tell
people how to use it.
arjan tijms wrote on 09/02/14 14:50:
> Yes, so "alt-dd' is a kind of version 0.5 IMHO of what the configuration spec
> should be about. To be really useable it should be much more dynamic and
> flexible.
>
> I wonder how many people have actually used the "alt-dd" feature in practice
> and what their experiences are with it.
>
>
>
> On Tue, Sep 2, 2014 at 11:07 PM, Bill Shannon <bill.shannon_at_oracle.com
> <mailto:bill.shannon_at_oracle.com>> wrote:
>
> Note that the "alt-dd" feature provides much of this, although certainly
> it could be improved. When you deploy an application you can provide an
> alternative deployment descriptor to be used in place of the deployment
> descriptor in the application. This gives you some ability to specify
> environment-specific per-deployment configuration information.
>
> arjan tijms wrote on 08/27/14 05:36:
>> On Wed, Aug 27, 2014 at 1:09 PM, Romain Manni-Bucau
>> <rmannibucau_at_gmail.com <mailto:rmannibucau_at_gmail.com>> wrote:
>>
>> I wouldn't go this way without config jsr otherwise we'll add another
>> layer which will conflict with some other jsr. The making it more
>> standard should be easier and can even be part of config jsr 1.1 I
>> guess.
>>
>>
>> I've discussed this option off list with various stakeholders of the
>> config JSR and this indeed seems to be one of the wishes;
>>
>> Use the exact syntax that's already available for the in-archive
>> descriptors, and provide that externally. It doesn't even have to be
>> specifically about data sources. Just have the ability to add (and
>> optionally override and perhaps even subtract) any descriptor fragment,
>> and the ability to define data source externally comes automatically.
>
>