. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.6. Platform Specific Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . main/groovy/ - A collection of scripts written in Groovy └── main/java/ - java source code └── test/groovy/ - A collection of scripts written in Groovy └── test/java/ - java as well as whether authentication is required. • Fire up an event which could be either a piece of code (like a script) or a service. • Define a response to the request. A response could either be another

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.6. Platform Specific Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . src/ ├── docs/ - component documentation source └── main/java/ - java source code └── test/java/ - java unit-tests ├── testdef - Defined integration-tests ├── as well as whether authentication is required. • Fire up an event which could be either a piece of code (like a script) or a service. • Define a response to the request. A response could either be another

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.6. Platform Specific Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . src/ ├── docs/ - component documentation source └── main/java/ - java source code └── test/java/ - java unit-tests ├── testdef - Defined integration-tests ├── as well as whether authentication is required. • Fire up an event which could be either a piece of code (like a script) or a service. • Define a response to the request. A response could either be another

format. However, the widget system allows users, if needed, to drop down to any platform-specific code and mix it with widget designs, thus providing a mix between ease of use, platform independence from Apache OFBiz community. It’s possible to change a property in OFBiz to have link to your own generation. For details about asciidoc rules used in Apache OFBiz have a look to Documentation Guidelines plugin components, there are two ways to read them. On the one hand, the plugin documentation generation process generates one document per plugin, so that you can see the list of documents in the pluginsdoc

format. However, the widget system allows users, if needed, to drop down to any platform-specific code and mix it with widget designs, thus providing a mix between ease of use, platform independence from Apache OFBiz community. It’s possible to change a property in OFBiz to have link to your own generation. For details about asciidoc rules used in Apache OFBiz have a look to Documentation Guidelines plugin components, there are two ways to read them. On the one hand, the plugin documentation generation process generates one document per plugin, so that you can see the list of documents in the pluginsdoc

format. However, the widget system allows users, if needed, to drop down to any platform-specific code and mix it with widget designs, thus providing a mix between ease of use, platform independence from Apache OFBiz community. It’s possible to change a property in OFBiz to have link to your own generation. For details about asciidoc rules used in Apache OFBiz have a look to Documentation Guidelines plugin components, there are two ways to read them. On the one hand, the plugin documentation generation process generates one document per plugin, so that you can see the list of documents in the pluginsdoc

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 6.6. Platform Specific Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . src/ ├── docs/ - component documentation source └── main/java/ - java source code └── test/java/ - java unit-tests ├── testdef - Defined integration-tests ├── as well as whether authentication is required. • Fire up an event which could be either a piece of code (like a script) or a service. • Define a response to the request. A response could either be another

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 6.6. Platform Specific Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . src/ ├── docs/ - component documentation source └── main/java/ - java source code └── test/java/ - java unit-tests ├── testdef - Defined integration-tests ├── as well as whether authentication is required. • Fire up an event which could be either a piece of code (like a script) or a service. • Define a response to the request. A response could either be another

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.6. Code Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . main reason for this choice is 1. all "autocompletion" mechanism and javadoc reading when writing code; 2. having a full IT language. Obviously, usage of java should be very simple for all non IT people test boundary is very clear. A Unit Test is not build to be used by a scenario test, so, if part of code could be used by Scenario Test, dedicated method should be created for that. All methods, like simple

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Code formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . block of configurations only for pdf rendering ⑤ define the title logo image ⑥ use the Rouge source code highlighter ⑦ end block of configurations only for PDF rendering The following configuration options a Sidebar paragraph. [source] This is a Source paragraph. See Code formatting for further examples. This is a Source paragraph. See Code formatting for further examples. 7 This indicates a simple description