. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 22.1. Help file organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . documents in the pluginsdoc directory and thus read each of them; On the other hand, each plugin master file is included in the plugin chapter of the user manual or developer manual, depending on whether the anchor generated (something like _the_title , with only lowercase), for example by looking in the html file generated. 4. In the screen add a

0 码力 | 237 页 | 2.74 MB | 1 年前

3

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 21.1. Help file organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . documents in the pluginsdoc directory and thus read each of them; On the other hand, each plugin master file is included in the plugin chapter of the user manual or developer manual, depending on whether the anchor generated (something like _the_title , with only lowercase), for example by looking in the html file generated. 4. In the screen add a

0 码力 | 307 页 | 5.64 MB | 1 年前

3

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 21.1. Help file organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . documents in the pluginsdoc directory and thus read each of them; On the other hand, each plugin master file is included in the plugin chapter of the user manual or developer manual, depending on whether the anchor generated (something like _the_title , with only lowercase), for example by looking in the html file generated. 4. In the screen add a

0 码力 | 304 页 | 5.21 MB | 1 年前

3

Components The basic unit in OFBiz is called "component". A component is at a minimum a folder with a file inside of it called "ofbiz-component.xml" Every application in OFBiz is a component. For example written in minilang (deprecated) ├── ofbiz-component.xml - The OFBiz main component configuration file ├── servicedef - Defined services. ├── src/ ├── docs/ - component documentation webapp folder. The main configuration for routing happens in controller.xml. The purpose of this file is to map requests to responses. Request Map A request in the control servlet might contain the

Components The basic unit in OFBiz is called "component". A component is at a minimum a folder with a file inside of it called "ofbiz-component.xml" Every application in OFBiz is a component. For example written in minilang (deprecated) ├── ofbiz-component.xml - The OFBiz main component configuration file ├── servicedef - Defined services. ├── src/ ├── docs/ - component documentation webapp folder. The main configuration for routing happens in controller.xml. The purpose of this file is to map requests to responses. 4 Request Map A request in the control servlet might contain

Components The basic unit in OFBiz is called "component". A component is at a minimum a folder with a file inside of it called "ofbiz-component.xml" Every application in OFBiz is a component. For example written in minilang (deprecated) ├── ofbiz-component.xml - The OFBiz main component configuration file ├── servicedef - Defined services. ├── src/ ├── docs/ - component documentation webapp folder. The main configuration for routing happens in controller.xml. The purpose of this file is to map requests to responses. 4 Request Map A request in the control servlet might contain

. . 4 2.3. file organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.4. File name conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 5. Importing files or file includes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . configurations only for PDF rendering The following configuration options are set globally in the Gradle build file. They are not configured in the document itself and are listed for reference only: build.gradle

. . 4 2.3. file organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.4. File name conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 5. Importing files or file includes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . configurations only for PDF rendering The following configuration options are set globally in the Gradle build file. They are not configured in the document itself and are listed for reference only: build.gradle

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.3. File name conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5. Importing files or file includes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . configurations only for PDF rendering The following configuration options are set globally in the Gradle build file. They are not configured in the document itself and are listed for reference only: build.gradle

. . 4 2.3. file organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.4. File name conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 5. Importing files or file includes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . configurations only for PDF rendering The following configuration options are set globally in the Gradle build file. They are not configured in the document itself and are listed for reference only: build.gradle