This is a dilemma everyone is dealing with. Balancing commercial
product deadlines that pay the bills with contribution to the open
source community that advance the project for everyone's benefit.
The chances are that if you don't see this idea through implementation
it will die away. Contributions usually come from developers who need
to solve a pain that they feel on their own. Very rarely one has the
time and energy to solve someone else's pain on a voluntary basis.
Cheers,
Ivelin
On Mar 28, 2011, at 6:45, Vilius Panevėžys <vilius@elitnet.lt> wrote:
> The idea of contributing is always tempting, it's just that I'm
> currently overwhelmed with tasks that have concrete deadlines and
> complications for not meeting them.
>
> I was hoping someone with a bit more free time will pick up the
> idea. :) I may have to resort to some hack for the time being like
> ANT's replacefilters applied when packaging the DU.
>
>
> Regards,
> --
> Vilius Panevėžys
> Elitnet
>
> On 2011-03-28 14:16, Eduardo Martins wrote:
>> Sounds a reasonable enhancement, can you contribute with it? :)
>>
>> -- Eduardo
>> ..............................................
>> http://emmartins.blogspot.com
>> http://redhat.com/solutions/telco
>>
>>
>>
>> 2011/3/28 Vilius Panevėžys<vilius@elitnet.lt>:
>>> Hi,
>>> is there a possibility to define constants in deploy-config.xml ?
>>>
>>> As it's not mentioned in User Guide and AFAICT is not allowed in
>>> the XSD
>>> schema, I would suggest this as a useful extension. If I'm wrong
>>> I'd be
>>> interested in learning how to use that.
>>>
>>> Example use case would be when we have to define multiple RA
>>> Entities with
>>> numerous properties most of which have identical values for all of
>>> them
>>> except for only a couple of them that differ in all of the
>>> entities. In this
>>> case I would prefer to define the common values in a common set of
>>> variables
>>> (constants) at the top of the file (deploy-config.xml) and
>>> reference those
>>> in properties section of each of the entities. That's just common
>>> sense but
>>> it would really ease maintenance of such deployments.
>>>
>>> The first idea that comes to mind for this is to allow declaring
>>> strings,
>>> e.g.
>>> ====== SNIPPET START ======
>>> <!-- [...] -->
>>> <!-- section of common properties -->
>>> <xs:string name="commonPropertyValue">cpv</xs:string>
>>>
>>> <!-- [...] -->
>>> <!-- properties of a particular RA entity-->
>>> <properties>
>>> <property name="commonProperty"
>>> type="java.lang.String" value="{$commonPropertyValue}" />
>>> <!-- [...] -->
>>> </properties>
>>> <!-- [...] -->
>>> ====== SNIPPET END ======
>>>
>>> Thanks!
>>>
>>>
>>> --
>>> Vilius Panevėžys
>>> Elitnet
>>>
>>
>>