I think its not with the context file. The problem is with class level bean
definitions using annotations once the component scan is turned on.
I will try injecting a custom context. Thanks Laszlo.
~Rajani
On 01-Apr-2014, at 12:35 am, Laszlo Hornyak wrote:
> Hi Rajani,
>
> I had a short
Hi Rajani,
I had a short investigation into the problem and that test context is quite
exciting. (which means I would need a lot more time to find all the
details) For a short solution I would recommend you to write another rather
than trying to reuse.
On Sat, Mar 29, 2014 at 11:30 AM, Rajani K
any help?
~Rajani
On 28-Mar-2014, at 9:48 am, Rajani Karuturi wrote:
> Its the testContext.xml we have at server/test/resouces
>
> As the async job dispatcher also comes under server/, i used the same test
> context file.
>
> ~Rajani
>
>
>
> On 28-Mar-2014, at 1:23 am, Laszlo Hornyak
Its the testContext.xml we have at server/test/resouces
As the async job dispatcher also comes under server/, i used the same test
context file.
~Rajani
On 28-Mar-2014, at 1:23 am, Laszlo Hornyak wrote:
> Hi Rajani,
>
> Can you share your spring context file?
>
>
> On Thu, Mar 27, 2014 a
Hi Rajani,
Can you share your spring context file?
On Thu, Mar 27, 2014 at 10:50 AM, Rajani Karuturi <
rajani.karut...@citrix.com> wrote:
> Hi All,
>
> I am trying to write unit tests for ApiAsyncJobDispatcher. This is how I
> defined by Test class @ server/test/com/cloud/api
>
> @RunWith(Sprin