The integration pack offers you to provide an arbitrary file storage location for files accessed/stored from the File Browser.

Read on to see how you can refit the system to your needs:


In many situations it is not enough or not possible at all to store files within the context. A connector establishes a bridge between the File Browser and a storage backend, it works as a transparent VFS or proxy which allows you to serve from an arbitrary location like context, local FS, DB, NFS/SMB share, FTP and so on.

The interface

Consult the JavaDocs of the interface net.fckeditor.connector.Connector to see how it works.

Choosing an implementation

You have to choose an implementation, either an existing or a custom one.

Ready-to-go implementations:

If no existing implementation suits your needs, create your own. Implement the interface and resolve the locale the way you want.

Declaring an implementation

After your have chosen your desired implementation, you have to declare it. Put the fully-qualified class name of the implementation in your

  connector.impl=<desired implementation>


A connector (at least a predefined one) interacts very closely with a UserPathBuilder implementation, great care must be exercised while choosing an implementation and userpath properties configuration. An improper configuration may result in erroneous and undefined behavior. See UserPathBuilder for more details.

Keep in mind:
If you write your own Connector implementation, it could be necessary to write your own listener to resolve the files managed by the File Browser inside your webapp.