omponents.xml did before?
>Then you don't need to override but just insert before.
>
>--Alex
>
>> -Original Message-
>> From: prasanna [mailto:srivatsav.prasa...@gmail.com] On Behalf Of
>> Prasanna Santhanam
>> Sent: Tuesday, April 16, 2013 11:5
y, April 16, 2013 11:56 PM
> To: dev@cloudstack.apache.org
> Subject: Re: inheritable componentContexts
>
> On Tue, Apr 16, 2013 at 09:43:47AM -0700, Kelven Yang wrote:
> >
> >
> > On 4/16/13 1:15 AM, "Prasanna Santhanam" wrote:
> >
> > >Thi
On Wed, Apr 17, 2013 at 10:21:58AM -0700, Kelven Yang wrote:
>
>
> On 4/16/13 11:55 PM, "Prasanna Santhanam" wrote:
>
> >On Tue, Apr 16, 2013 at 09:43:47AM -0700, Kelven Yang wrote:
> >>
> >>
> >> On 4/16/13 1:15 AM, "Prasanna Santhanam" wrote:
> >>
> >> >This is probably a question for the
On 4/16/13 11:55 PM, "Prasanna Santhanam" wrote:
>On Tue, Apr 16, 2013 at 09:43:47AM -0700, Kelven Yang wrote:
>>
>>
>> On 4/16/13 1:15 AM, "Prasanna Santhanam" wrote:
>>
>> >This is probably a question for the Spring community but I'll ask here
>> >anyway. Every so often when the component
On Tue, Apr 16, 2013 at 09:43:47AM -0700, Kelven Yang wrote:
>
>
> On 4/16/13 1:15 AM, "Prasanna Santhanam" wrote:
>
> >This is probably a question for the Spring community but I'll ask here
> >anyway. Every so often when the componentContext.xml.in changes I find
> >that I have to fix up simul
On 4/16/13 1:15 AM, "Prasanna Santhanam" wrote:
>This is probably a question for the Spring community but I'll ask here
>anyway. Every so often when the componentContext.xml.in changes I find
>that I have to fix up simulatorComponentContext.xml.in similarly to
>make the beans load appropriately
