The ordering logic should already be sufficiently tested by the
TestOrderer test. I suppose you'll only have to test that the name
attribute properly overrides the service-id attribute.

--knut

On Sun, 27 Feb 2005 09:18:37 -0500, James Carman
<[EMAIL PROTECTED]> wrote:
> Just found that!  Thanks.  It took a bit of digging, but I found it.  Also,
> does anyone know of a test case that tests the ordering logic for
> interceptors?  I need to put in a specific test case for when the name is
> overridden.
> 
> -----Original Message-----
> From: Knut Wannheden [mailto:[EMAIL PROTECTED]
> Sent: Sunday, February 27, 2005 9:15 AM
> To: [email protected]
> Subject: Re: AOPAlliance Service Interceptors...
> 
> James,
> 
> On Sun, 27 Feb 2005 08:53:01 -0500, James Carman
> <[EMAIL PROTECTED]> wrote:
> >
> >
> > I am already implementing it by adding a "name" attribute to
> > ServiceInterceptorContribution (and its impl class and the code that
> builds
> > it)...
> >
> 
> I'm not sure if you've found out already (as it's not all that
> obvious), but to extend the syntax you have to edit
> DescriptorParser.properties.
> 
> --knut
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to