Ah, I may have something wrong. This is in my components:
org.apache.sling.fsprovider.internal.FsResourceProvider unsatisfied

R

On Oct 23, 2012, at 3:30 PM, Robert A. Decker wrote:

> I think so…
> 
> In my bundles I have:
> Apache Sling Filesystem Resource Provider org.apache.sling.fsresource 
> 1.0.3.SNAPSHOT  sling   Active
> 
> unless there's a different bundle.
> 
> Rob
> 
> On Oct 23, 2012, at 3:26 PM, David G. wrote:
> 
>> Robert - You've installed the Sling FsResourceProvider bundle correct? and 
>> its successfully activated?
>> 
>> -- 
>> David Gonzalez
>> Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
>> 
>> 
>> On Tuesday, October 23, 2012 at 9:22 AM, Robert A. Decker wrote:
>> 
>>> Hello,
>>> 
>>> I'm trying to configuring an instance of FsResourceProvider via an xml file 
>>> in my app's 'install' directory but can't get it to work.
>>> 
>>> I've tried combinations of the following. Should it work to create an 
>>> instance of FsResourceProvider this way? I'm basing it on how the logging 
>>> services were configured and worked for me.
>>> 
>>> org.apache.sling.fsprovider.internal.FsResourceProvider.xml
>>> 
>>> <node>
>>> <name>org.apache.sling.fsprovider.internal.FsResourceProvider</name>
>>> <primaryNodeType>sling:OsgiConfig</primaryNodeType>
>>> <property>
>>> <name>provider.roots</name>
>>> <value>/content/fs/tmp</value>
>>> <type>String</type>
>>> </property>
>>> <property>
>>> <name>provider.file</name>
>>> <value>/tmp</value>
>>> <type>String</type>
>>> </property>
>>> </node>
>>> 
>>> and 
>>> 
>>> 
>>> org.apache.sling.fsprovider.internal.FsResourceProvider-tmp.xml
>>> 
>>> <node>
>>> <name>org.apache.sling.fsprovider.internal.FsResourceProvider-tmp</name>
>>> <primaryNodeType>sling:OsgiConfig</primaryNodeType>
>>> <property>
>>> <name>provider.roots</name>
>>> <value>/content/fs/tmp</value>
>>> <type>String</type>
>>> </property>
>>> <property>
>>> <name>provider.file</name>
>>> <value>/tmp</value>
>>> <type>String</type>
>>> </property>
>>> </node>
>>> 
>>> 
>>> 
>>> Rob 
>> 
> 
> 

Reply via email to