Section 2.0 done
This commit is contained in:
parent
43fc5f59a8
commit
a0373f4db7
@ -495,8 +495,52 @@ Initial Release
|
||||
Overview
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Classes Description
|
||||
\begin_layout Standard
|
||||
Open For Business (OFBiz) is a suite of enterprise applications built on
|
||||
a common architecture using common data, logic and process components.
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
The functionality can be divided into the following distinct layers:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
|
||||
\series bold
|
||||
Presentation Layer:
|
||||
\series default
|
||||
Apache OFBiz uses the concept of "screens" to represent the Apache OFBiz
|
||||
pages.
|
||||
Each page is, normally, represented as a screen.
|
||||
A page in Apache OFBiz consists of components.
|
||||
When the page is rendered all the components are combined together as specified
|
||||
in the screen definition.
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
|
||||
\series bold
|
||||
Business Layer:
|
||||
\series default
|
||||
the business, or application layer defines services provided to the user.
|
||||
The services can be of several types: Java methods, SOAP, simple services,
|
||||
workflow, etc.
|
||||
A service engine is responsible for invocation, transactions and security.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
|
||||
\series bold
|
||||
Data Layer:
|
||||
\series default
|
||||
the data layer is responsible for database access, storage and providing
|
||||
a common data interface to the Business layer.
|
||||
Data is accessed not in Object Oriented fashion but in a relational way.
|
||||
Each entity is provided to the business layer as a set of generic values.
|
||||
A generic value is not typed, so fields of an entity are accessed by the
|
||||
column name.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
@ -515,18 +559,6 @@ UrlRegexpTransform
|
||||
.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
All these classes are located in
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
http://mirror.nohup.it/apache/ofbiz/apache-ofbiz-16.11.01.zip
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
, where we can find the source code of Apache OFBiz.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Every class is pretty self-explanatory:
|
||||
\family typewriter
|
||||
@ -545,53 +577,6 @@ rely on the Freemarker template engine to parse and edit URIs
|
||||
.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
***Preso da wikipedia, quindi un po' bisogna cambiare le parole***
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Apache OFBiz is a framework that provides a common data model and a rich
|
||||
set of business process.
|
||||
All applications are built around a common architecture using common data,
|
||||
logic and process components.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
All of Apache OFBiz functionality is built on a common framework.
|
||||
The functionality can be divided into the following distinct layers:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Presentation Layer: Apache OFBiz uses the concept of "screens" to represent
|
||||
the Apache OFBiz pages.
|
||||
Each page is, normally, represented as a screen.
|
||||
A page in Apache OFBiz consists of components.
|
||||
When the page is rendered all the components are combined together as specified
|
||||
in the screen definition.
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Business Layer: The business, or application layer defines services provided
|
||||
to the user.
|
||||
The services can be of several types: Java methods, SOAP, simple services,
|
||||
workflow, etc.
|
||||
A service engine is responsible for invocation, transactions and security.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Data Layer: The data layer is responsible for database access, storage and
|
||||
providing a common data interface to the Business layer.
|
||||
Data is accessed not in Object Oriented fashion but in a relational way.
|
||||
Each entity is provided to the business layer as a set of generic values.
|
||||
A generic value is not typed, so fields of an entity are accessed by the
|
||||
column name.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Functional Roles
|
||||
\end_layout
|
||||
|
||||
\begin_layout Section
|
||||
Issues
|
||||
\end_layout
|
||||
|
Loading…
Reference in New Issue
Block a user