You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Shivi S <sd...@gmail.com> on 2008/10/08 12:03:44 UTC
Virtual file system and external database
Hi!
I have a requirement as below.
We need to manage contents of our website using a Webdav client like
Dreamweaver. The website contents are stored as static files in the
webserver as well as dynamic contents in the database. For example, the css,
images, .swf files are stored in the webserver and the html contents are
stored in oracle database.
I need to build a virtual file system that lists both the static and the
database contents as directory / file structure to let the users manage the
content using Dreamweaver with Webdav.
I wonder if I can use Apache Jackrabbit components for implementation.
I am very new to Virtual file system, Webdav and content management. I
checked for some implementation examples but I was unable to find any.
I greatly appreciate for any help / advices provided to me.
Regards
Shivi
Re: Virtual file system and external database
Posted by Matthijs Wensveen <m....@func.nl>.
Shivi S wrote:
> I checked Apache commons as well. I don't see any database related
> implementations.
> If you know any reference examples, please send me.
>
Unfortunately, I don't know of any database implementations. The
provided interfaces are pretty straightforward, so it shouldn't be very
hard to write.
Regards,
Matthijs
> On Wed, Oct 8, 2008 at 4:44 PM, Matthijs Wensveen <m....@func.nl>wrote:
>
>
>> Jukka Zitting wrote:
>>
>>
>>> Hi,
>>>
>>> On Wed, Oct 8, 2008 at 12:28 PM, Shivi S <sd...@gmail.com> wrote:
>>>
>>>
>>>
>>>> I went through some of the documentation of Jackrabbit and a few examples
>>>> from the forums but most of them were based on jackrabbit repositories. I
>>>> also came across a "Virtual file system" that Jackrabbit provides, so I'd
>>>> like to know if it is possible for me to use this without an actual
>>>> content
>>>> repository configured.
>>>>
>>>>
>>>>
>>> The "virtual file system" in Jackrabbit is a feature that allows you
>>> to access the content repository like you would a normal file system
>>> on a network drive. While the related code is reasonably reusable
>>> (i.e. you could adapt it to use another backend), Jackrabbit does not
>>> support other backends out of the box.
>>>
>>> BR,
>>>
>>> Jukka Zitting
>>>
>>>
>>>
>> You might want to check out commons-vfs (http://commons.apache.org/vfs).
>>
>> Regards,
>> Matthijs
>>
>>
>
>
Re: Virtual file system and external database
Posted by Shivi S <sd...@gmail.com>.
I checked Apache commons as well. I don't see any database related
implementations.
If you know any reference examples, please send me.
On Wed, Oct 8, 2008 at 4:44 PM, Matthijs Wensveen <m....@func.nl>wrote:
> Jukka Zitting wrote:
>
>> Hi,
>>
>> On Wed, Oct 8, 2008 at 12:28 PM, Shivi S <sd...@gmail.com> wrote:
>>
>>
>>> I went through some of the documentation of Jackrabbit and a few examples
>>> from the forums but most of them were based on jackrabbit repositories. I
>>> also came across a "Virtual file system" that Jackrabbit provides, so I'd
>>> like to know if it is possible for me to use this without an actual
>>> content
>>> repository configured.
>>>
>>>
>>
>> The "virtual file system" in Jackrabbit is a feature that allows you
>> to access the content repository like you would a normal file system
>> on a network drive. While the related code is reasonably reusable
>> (i.e. you could adapt it to use another backend), Jackrabbit does not
>> support other backends out of the box.
>>
>> BR,
>>
>> Jukka Zitting
>>
>>
> You might want to check out commons-vfs (http://commons.apache.org/vfs).
>
> Regards,
> Matthijs
>
Re: Virtual file system and external database
Posted by Matthijs Wensveen <m....@func.nl>.
Jukka Zitting wrote:
> Hi,
>
> On Wed, Oct 8, 2008 at 12:28 PM, Shivi S <sd...@gmail.com> wrote:
>
>> I went through some of the documentation of Jackrabbit and a few examples
>> from the forums but most of them were based on jackrabbit repositories. I
>> also came across a "Virtual file system" that Jackrabbit provides, so I'd
>> like to know if it is possible for me to use this without an actual content
>> repository configured.
>>
>
> The "virtual file system" in Jackrabbit is a feature that allows you
> to access the content repository like you would a normal file system
> on a network drive. While the related code is reasonably reusable
> (i.e. you could adapt it to use another backend), Jackrabbit does not
> support other backends out of the box.
>
> BR,
>
> Jukka Zitting
>
You might want to check out commons-vfs (http://commons.apache.org/vfs).
Regards,
Matthijs
Re: Virtual file system and external database
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Wed, Oct 8, 2008 at 12:28 PM, Shivi S <sd...@gmail.com> wrote:
> I went through some of the documentation of Jackrabbit and a few examples
> from the forums but most of them were based on jackrabbit repositories. I
> also came across a "Virtual file system" that Jackrabbit provides, so I'd
> like to know if it is possible for me to use this without an actual content
> repository configured.
The "virtual file system" in Jackrabbit is a feature that allows you
to access the content repository like you would a normal file system
on a network drive. While the related code is reasonably reusable
(i.e. you could adapt it to use another backend), Jackrabbit does not
support other backends out of the box.
BR,
Jukka Zitting
Re: Virtual file system and external database
Posted by Shivi S <sd...@gmail.com>.
Hi Jukka,
Thank you for the reply.
We already have the contents set in the normal file system and a database
and therefore the jackrabbit content repository is not required.
I went through some of the documentation of Jackrabbit and a few examples
from the forums but most of them were based on jackrabbit repositories. I
also came across a "Virtual file system" that Jackrabbit provides, so I'd
like to know if it is possible for me to use this without an actual content
repository configured.
Regards
Shivi
On Wed, Oct 8, 2008 at 3:49 PM, Jukka Zitting <ju...@gmail.com>wrote:
> Hi,
>
> On Wed, Oct 8, 2008 at 12:03 PM, Shivi S <sd...@gmail.com> wrote:
> > I need to build a virtual file system that lists both the static and the
> > database contents as directory / file structure to let the users manage
> the
> > content using Dreamweaver with Webdav.
> > I wonder if I can use Apache Jackrabbit components for implementation.
>
> Have you considered using the Jackrabbit content repository as unified
> storage for all your content? The content repository supports both
> file system and database features as well as good WebDAV integration,
> so I think it could be an excellent match for your requirements.
>
> If you're set on using a normal file system and a database as your
> storage backend, then I'm afraid we don't have any OOTB solutions for
> you. The jackrabbit-webapp component contains quite a bit of generic
> WebDAV functionality that you could reuse to implement your own
> virtual WebDAV layer, but doing that requires programming effort and
> WebDAV knowledge from you.
>
> BR,
>
> Jukka Zitting
>
Re: Virtual file system and external database
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Wed, Oct 8, 2008 at 12:03 PM, Shivi S <sd...@gmail.com> wrote:
> I need to build a virtual file system that lists both the static and the
> database contents as directory / file structure to let the users manage the
> content using Dreamweaver with Webdav.
> I wonder if I can use Apache Jackrabbit components for implementation.
Have you considered using the Jackrabbit content repository as unified
storage for all your content? The content repository supports both
file system and database features as well as good WebDAV integration,
so I think it could be an excellent match for your requirements.
If you're set on using a normal file system and a database as your
storage backend, then I'm afraid we don't have any OOTB solutions for
you. The jackrabbit-webapp component contains quite a bit of generic
WebDAV functionality that you could reuse to implement your own
virtual WebDAV layer, but doing that requires programming effort and
WebDAV knowledge from you.
BR,
Jukka Zitting