160 11.3. Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 11.3.1. Routing management in . 162 11.4. Routing Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 11.4.1. Routing Task management classical web MVC (Model View Controller) framework. This part of the system is designed for basic routing of web requests and may be considered as the infrastructure or plumbing where everything is wired

170 10.3. Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 10.3.1. Routing management in . 172 10.4. Routing Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 10.4.1. Routing Task management classical web MVC (Model View Controller) framework. This part of the system is designed for basic routing of web requests and may be considered as the infrastructure or plumbing where everything is wired

170 10.3. Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 10.3.1. Routing management in . 172 10.4. Routing Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 10.4.1. Routing Task management classical web MVC (Model View Controller) framework. This part of the system is designed for basic routing of web requests and may be considered as the infrastructure or plumbing where everything is wired

its core is a collection of systems: • A web server (Apache Tomcat) • A web MVC framework for routing and handling requests. • An entity engine to define, load and manipulate data. • A service engine component is in fact a full application as it contains entities, data, services, user interface, routing, tests, and business logic. Both core OFBiz applications as well as plugins are nothing more than application is something which is defined inside a component • control: Tells OFBiz to transfer routing to the control servlet 3 • findInvoices: request name inside the control servlet 1.3.2. Control

its core is a collection of systems: • A web server (Apache Tomcat) • A web MVC framework for routing and handling requests. • An entity engine to define, load and manipulate data. • A service engine component is in fact a full application as it contains entities, data, services, user interface, routing, tests, and business logic. Both core OFBiz applications as well as plugins are nothing more than application is something which is defined inside a component • control: Tells OFBiz to transfer routing to the control servlet • findInvoices: request name inside the control servlet 1.3.2. Control servlet

its core is a collection of systems: • A web server (Apache Tomcat) • A web MVC framework for routing and handling requests. • An entity engine to define, load and manipulate data. • A service engine component is in fact a full application as it contains entities, data, services, user interface, routing, tests, and business logic. Both core OFBiz applications as well as plugins are nothing more than application is something which is defined inside a component • control: Tells OFBiz to transfer routing to the control servlet • findInvoices: request name inside the control servlet 1.3.2. Control servlet

its core is a collection of systems: • A web server (Apache Tomcat) • A web MVC framework for routing and handling requests. • An entity engine to define, load and manipulate data. • A service engine component is in fact a full application as it contains entities, data, services, user interface, routing, tests, and business logic. Both core OFBiz applications as well as plugins are nothing more than application is something which is defined inside a component • control: Tells OFBiz to transfer routing to the control servlet • findInvoices: request name inside the control servlet 1.3.2. Control servlet

its core is a collection of systems: • A web server (Apache Tomcat) • A web MVC framework for routing and handling requests. • An entity engine to define, load and manipulate data. • A service engine component is in fact a full application as it contains entities, data, services, user interface, routing, tests, and business logic. Both core OFBiz applications as well as plugins are nothing more than application is something which is defined inside a component • control: Tells OFBiz to transfer routing to the control servlet • findInvoices: request name inside the control servlet 1.3.2. Control servlet

its core is a collection of systems: • A web server (Apache Tomcat) • A web MVC framework for routing and handling requests. • An entity engine to define, load and manipulate data. • A service engine component is in fact a full application as it contains entities, data, services, user interface, routing, tests, and business logic. Both core OFBiz applications as well as plugins are nothing more than application is something which is defined inside a component 3 • control: Tells OFBiz to transfer routing to the control servlet • findInvoices: request name inside the control servlet 1.3.2. Control servlet

classical web MVC (Model View Controller) framework. This part of the system is designed for basic routing of web requests and may be considered as the infrastructure or plumbing where everything is wired