| 76 | | ... |
| | 76 | The basic idea of extending the Connector is to provide interfaces for special user depended issues, |
| | 77 | which can be implemented by the developer of a webapp. All methods get the <<<HttpServletRequest>>>-object, |
| | 78 | so the developer could identify the user with a session attribute for example and return an user |
| | 79 | specific value. We intentionally make no suggestions how to do this, so you have the free of choice to |
| | 80 | implement whatever and however you like. |
| | 81 | |
| | 82 | The fully-qualified class name of the implemented classes can now be set as described in |
| | 83 | {{{fckeditor-properties.html}Configuration settings}}. |
| | 84 | |
| | 85 | At the moment, the integration pack provides two interfaces to extend the connector: |
| | 86 | |
| | 87 | [[1]] {{{apidocs/net/fckeditor/requestcycle/UserPathBuilder.html}<<<net.fckeditor.requestcycle.UserPathBuilder>>>}} |
| | 88 | |
| | 89 | In this interface there is only one method <<<getUserFilesPath(final HttpServletRequest request)>>>, |
| | 90 | return value is a String. There you can implement a user dependent construction of the 'BaseDir' path, |
| | 91 | the path for all resource files. |
| | 92 | |
| | 93 | [[2]] {{{apidocs/net/fckeditor/requestcycle/UserAction.html}<<<net.fckeditor.requestcycle.UserAction>>>}} |
| | 94 | |
| | 95 | There are two methods to authorize users to do file based actions: |
| | 96 | |
| | 97 | * <<<#isEnabledForFileUpload(HttpServletRequest)>>> Enables/disables the user for uploading files. |
| | 98 | |
| | 99 | * <<<#isEnabledForFileBrowsing(HttpServletRequest)>>> Enables/disables the user for browsing files. |
| | 100 | |
| | 101 | [] |
| | 102 | |
| | 103 | For those who wants to enable all users for browsing and uploading files, there is an implementation |
| | 104 | of <<<UserAction>>> you can use: {{{apidocs/net/fckeditor/requestcycle/impl/UserActionImp.html}UserActionImpl}} |