Mailing-List: contact abdera-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: abdera-user@incubator.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Reply-To: <remy.gendron@arrova.ca>
From: "Remy Gendron" <remy.gendron@arrova.ca>
To: <abdera-user@incubator.apache.org>,
	<remy.gendron@arrova.ca>
References: <191EA8B5569E448F87050FF229175C76@ArrovaL001>
 <4DD5FA4BA57941448B3B142644923FE4@ArrovaL001>
 <4782A101.9000203@mulesource.com>
 <4ED60A854162433A9D4D68D46FA14B92@ArrovaL001>
In-Reply-To: <4ED60A854162433A9D4D68D46FA14B92@ArrovaL001>
Subject: RE: collectionProvider attribute is null
Date: Tue, 8 Jan 2008 09:58:27 -0500
Organization: @rrova
Message-ID: <4546AB8B69E9419EBC5D677EB1E2D28D@ArrovaL001>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1250"
Content-Transfer-Encoding: 7bit
Thread-Index: AchReNTokYHvAQRUSg6w/qM7Tqd34QAhvILAAAGw2xA=

Everything works great using the ServiceProvider as the target resolver. No
more need for the Regex stuff. Thanks!

And the collection providers do not have to register themselves with the
application context. OK there.

Thanks Dan! I would forgo the need to have backward compatibility with a
specific RegexTargetResolver. Simplicity is always best.

Thanks again!

- Remy

-----Original Message-----
From: Remy Gendron [mailto:remy.gendron@arrova.ca] 
Sent: 08 January 2008 09:10
To: abdera-user@incubator.apache.org
Subject: RE: collectionProvider attribute is null

Thanks for the reply. It makes sense that the service provider, having all
the necessary information about workspaces and collection providers, is able
to automatically route incoming requests.

I did use a specific instance of RegexTargetResolver because that was how it
was done in the server unit tests.

I'm going to try using the service provider as the resolver.

Thanks for the heads-up...

- Remy


-----Original Message-----
From: Dan Diephouse [mailto:dan.diephouse@mulesource.com] 
Sent: 07 January 2008 17:01
To: abdera-user@incubator.apache.org
Subject: Re: collectionProvider attribute is null

Remy Gendron wrote:
> The regex target resolver is now gone from the unit test initialization?
Can
> you provide a short explanation?

This could actually be the issue.

I changed the AbstractServiceProvider so that it implements 
Resolver<Target> now. Which means that people don't have to use 
RegexTargetResult. They simply need to supply the ServiceProvider as 
their Resolver.

I wasn't really thinking about the use case where people still have 
their own resolvers though. I'm going to have to look into how to make 
these two things work together. It may not be possible because 
ServiceProviders assume a very specific layout.

Have you specified the ServiceProvider as the Resolver for your 
application? Or did you just remove the RegexTargetResolver?

- Dan

-- 
Dan Diephouse
MuleSource
http://mulesource.com | http://netzooid.com/blog

No virus found in this incoming message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.17.13/1213 - Release Date: 2008.01.07
09:14
 

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.17.13/1213 - Release Date: 2008.01.07
09:14
 

No virus found in this incoming message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.17.13/1213 - Release Date: 2008.01.07
09:14
 

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.17.13/1213 - Release Date: 2008.01.07
09:14