Writing an ofbiz Container - Revision history

Sichen at 20:04, 29 July 2008

2008-07-29T20:04:15Z

Sichen at 20:01, 29 July 2008

2008-07-29T20:01:13Z

Sichen: Protected "Writing an ofbiz Container": Sysop page [edit=sysop:move=sysop]

2008-07-29T18:40:29Z

Protected "Writing an ofbiz Container": Sysop page [edit=sysop:move=sysop]

Sichen: New page: The ofbiz framework has a container architecture that allows you to set up containers which load up system infrastructure such as the delegator (database access), dispatcher (business logi...

2008-07-29T18:40:29Z

New page: The ofbiz framework has a container architecture that allows you to set up containers which load up system infrastructure such as the delegator (database access), dispatcher (business logi...

New page

The ofbiz framework has a container architecture that allows you to set up containers which load up system infrastructure such as the delegator (database access), dispatcher (business logic tier), and web servers like Tomcat. When ofbiz is started, it will call a container based on the command line input:

<pre>
$ java -jar ofbiz.jar pojoentities
</pre>

means that it will call up the <tt>pojoentities</tt> container.

@@ Line 8: / Line 8: @@
 causes the following target in the <tt>build.xml</tt> to be called:
 <pre>
+ <target name="make-base-entities">
 </pre>
 which in turn calls ofbiz with the following commandline parameters:
@@ Line 17: / Line 23: @@
 means that it will call up the <tt>pojoentities</tt> container.  When ofbiz starts up, it will look for a file called <tt>pojoentities.properties</tt> in the <tt>org.ofbiz.base.start</tt> package.  This file is in fact located in <tt>framework/base/src/start/org/ofbiz/base/start/pojoentities.properties</tt> and defines the runtime configuration of ofbiz.  For example, it defines where the configuration files are, where the log directory is, and whether the container will shut itself down automatically.  The most important definition is an XML file which configures the container:
-This file is in <tt>framework/base/config</tt>  and defines the loaders for the container and then the container classes.  In this case, it is <tt>org.opentaps.domain.container.PojoGeneratorContainer</tt>.  The XML file also specifies the parameters for the container, which in this case is the name of the delegator and where the template and output file path for the POJOs are:
+Finally, your container must have a standard <tt>init</tt> method, and the <tt>start()</tt> method will call the logic of the container.  You can get the configuration properties of your container like this:
 And everything else can follow from there.

@@ Line 1: / Line 1: @@
-The ofbiz framework has a container architecture that allows you to set up containers which load up system infrastructure such as the delegator (database access), dispatcher (business logic tier), and web servers like Tomcat.  When ofbiz is started, it will call a container based on the command line input:
+The ofbiz framework has a container architecture that allows you to set up containers which load up system infrastructure such as the delegator (database access), dispatcher (business logic tier), and web servers like Tomcat.  The standard containers are used to run opentaps from the Tomcat server, run the POS terminal as a desktop application, or install data or write unit tests.  You can also create your own containers for other purposes.  For example, we created a custom container to generate Java classes for all the entities in the entitymodel XML files.
 <pre>
@@ Line 5: / Line 16: @@
 </pre>
-means that it will call up the <tt>pojoentities</tt> container.
+means that it will call up the <tt>pojoentities</tt> container.  When ofbiz starts up, it will look for a file called <tt>pojoentities.properties</tt> in the <tt>org.ofbiz.base.start</tt> package.  This file is in fact located in <tt>framework/base/src/start/org/ofbiz/base/start/pojoentities.properties</tt> and defines the runtime configuration of ofbiz.  For example, it defines where the configuration files are, where the log directory is, and whether the container will shut itself down automatically.  The most important definition is an XML file which configures the container:

← Older revision	Revision as of 18:40, 29 July 2008
(No difference)