| | 1 | To configure your services, you have a folder inside the user's path. The folder is called |
| | 2 | .gnowsis and inside that you either have config or data. |
| | 3 | |
| | 4 | |
| | 5 | Suggestion, that is not binding: |
| | 6 | each service has his web-inf folder, where you make a 'default' folder. During |
| | 7 | your config api init, you get the ServiceContext object, which has a method like |
| | 8 | "getServicePath" which returns the folder containing the WEB-INF. ie the |
| | 9 | "epos_context" path is returned. |
| | 10 | |
| | 11 | you then call ConfigBlubManager.checkAndCopy(folderA, folderB) to check and copy |
| | 12 | the defaults. the semantic of checkAndCopy is to copy everything that is to copy |
| | 13 | everything from A to B that is not in B already. if a file in b already exists, |
| | 14 | don't overwrite it. |
| | 15 | |
| | 16 | {{{ |
| | 17 | example for such an config dir: |
| | 18 | blubservice/WEB-INF/default/config/setting.xml |
| | 19 | is copied to |
| | 20 | .gnowsis/config/blubservice/setting.xml |
| | 21 | |
| | 22 | and |
| | 23 | blubservice/WEB-INF/default/data/setting.xml |
| | 24 | is copied to |
| | 25 | .gnowsis/data/blubservice/setting.xml |
| | 26 | }}} |