abdera-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Calavera <david.calav...@gmail.com>
Subject Re: Spring + FileSystemAdapters
Date Tue, 20 Jan 2009 15:20:33 GMT
Hi Cris,

can you open a ticket in our jira and propose a solution or a patch to fix



On Tue, Jan 20, 2009 at 4:04 PM, Chris K Wensel <chris@wensel.net> wrote:

> Hey all
> I'm spending a little time to get to know Abdera and was thinking for a
> simple setup I would use the FileSystemAdapters (before diving into the JCR
> rabbit hole).
> But it seems they only work with a ManagedProvider.
> But wanting a little flexibility without writing my own Provider class, I
> thought I would throw Spring in the mix.
> But BasicProvider isn't so Spring friendly (doesn't accept "base" on the
> ctor). So I thought I would give the Spring friendly DefaultProvider a
> different "workspaceManager", namely BasicProvider (as it implements the
> proper interface).
> But, it seems DefaultProvider has no setter for workspaceManager.
> I've likely answered my own question, but seeing that the Spring
> support/schema allows for a fair bit of flexibility, I'm wondering maybe I
> missed something and I can convince a Spring configured Abdera to
> dynamically load FileSystemAdapters and I just haven't found the right
> voodoo.
> am using abdera trunk, had same issues with 0.4.0-incubator.
> I can write a sub-class that is Spring friendly, but if I can use Spring
> instead of custom code, that would be great.
> cheers,
> ckw
> --
> Chris K Wensel
> chris@wensel.net
> http://www.cascading.org/
> http://www.scaleunlimited.com/

David Calavera

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message