Recent changes to Class Overview

Class Overview modified by Pieter van der Merwe

Pieter van der Merwe — Thu, 23 May 2013 12:31:43 -0000

--- v4
+++ v5
@@ -17,7 +17,7 @@

 OpenERPCommand
 ---
-The OpenERPCommand class wraps around the basic OpenERP commands.  It does no validation, error checking or conversions.  If you find the ObjectAdapter too restrictive in its validation, you can go back to the OpenERPCommand object (but please also start a [discussion](https://sourceforge.net/p/openerpjavaapi/discussion/) or raise a [ticket](https://sourceforge.net/p/openerpjavaapi/tickets/) to get it fixed).  See the [Conversion Considerations] section for a couple of type conversion hints.
+The OpenERPCommand class wraps around the basic OpenERP commands.  It does no validation, error checking or conversions.  If you find the ObjectAdapter too restrictive in its validation, you can go back to the OpenERPCommand object (but please also raise a [ticket](https://github.com/DeBortoliWines/openerp-java-api/issues) to get it fixed).  See the Conversion Considerations section on this page for a couple of type conversion hints.

 Unsupported functions
 ---

WikiPage Class Overview modified by Pieter van der Merwe

Pieter van der Merwe — Wed, 21 Sep 2011 00:33:37 -0000

--- v3 
+++ v4 
@@ -25,6 +25,6 @@
 
 Conversion Considerations
 ---
-If you do make use of the OpenERPCommand or Session object to communicate with the server, the following needs to be taken into account.  Python dictionaries map to Java HashMap objects and Python lists map to Object\[\].  OpenERP does not support [extended XMLRPC types](http://ws.apache.org/xmlrpc/types.html) (ie floats etc, you have to use doubles) and null values map to the boolean 'false' (sending and receiving).  Each function may also have different requirements, for example the import_data function requires that many2many values are a comma separated list of field names (yes, names not ids).  See the OpenERP website for how many2many fields are handled when using the create/write functions (remembering that lists are Object\[\]).
+If you do make use of the OpenERPCommand or Session object to communicate with the server, the following needs to be taken into account.  Python dictionaries map to Java HashMap objects and Python lists map to Object\[\].  OpenERP does not support [extended XMLRPC types](http://ws.apache.org/xmlrpc/types.html) (ie floats etc, you have to use doubles) and null values map to the boolean 'false' (sending and receiving).  Each function may also have different requirements, for example the import_data function requires that many2many values are a comma separated list of object names (yes, names not ids).  See the OpenERP website for how many2many fields are handled when using the create/write functions (remembering that lists are Object\[\]).
 
 Unless the call is very simple or you are forced to use the other classes, the ObjectAdapter is the suggested method of communicating with the server.  It takes all conversion considerations into account.

WikiPage Class Overview modified by Pieter van der Merwe

Pieter van der Merwe — Wed, 21 Sep 2011 00:31:34 -0000

--- v2 
+++ v3 
@@ -6,7 +6,7 @@
 
 Wrapper Classes
 ---
-The two main classes used to communicate to the OpenERP server are:
+The two main classes used to communicate with the OpenERP server are:
 1. ObjectAdapter
 2. OpenERPCommand

WikiPage Class Overview modified by Pieter van der Merwe

Pieter van der Merwe — Tue, 20 Sep 2011 13:40:31 -0000

WikiPage Overview modified by Pieter van der Merwe

Pieter van der Merwe — Tue, 20 Sep 2011 13:40:01 -0000

This section provides a brief overview of the main objects the API provides. Session Class --- The starting point for communicating with the OpenERP server is the Session class. The session class holds session credentials and the context object. It provides the 'executeCommand' method used by other classes to communicate with the server. Wrapper Classes --- The two main classes used to communicate to the OpenERP server are: 1. ObjectAdapter 2. OpenERPCommand ObjectAdapter --- The Object Adapter class is the preferred way of communicating with the OpenERP server. It does error checking on filters and data, converts data types, formats values and wraps OpenERP responses into RowCollection objects. OpenERPCommand --- The OpenERPCommand class wraps around the basic OpenERP commands. It does no validation, error checking or conversions. If you find the ObjectAdapter too restrictive in its validation, you can go back to the OpenERPCommand object (but please also start a [discussion](https://sourceforge.net/p/openerpjavaapi/discussion/) or raise a [ticket](https://sourceforge.net/p/openerpjavaapi/tickets/) to get it fixed). See the [Conversion Considerations] section for a couple of type conversion hints. Unsupported functions --- If you find that the ObjectAdapter and OpenERPCommand classes don't wrap around the function you want to use, you can call the 'executeCommand' function on the Session object. Conversion Considerations --- If you do make use of the OpenERPCommand or Session object to communicate with the server, the following needs to be taken into account. Python dictionaries map to Java HashMap objects and Python lists map to Object\[\]. OpenERP does not support [extended XMLRPC types](http://ws.apache.org/xmlrpc/types.html) (ie floats etc, you have to use doubles) and null values map to the boolean 'false' (sending and receiving). Each function may also have different requirements, for example the import_data function requires that many2many values are a comma separated list of field names (yes, names not ids). See the OpenERP website for how many2many fields are handled when using the create/write functions (remembering that lists are Object\[\]). Unless the call is very simple or you are forced to use the other classes, the ObjectAdapter is the suggested method of communicating with the server. It takes all conversion considerations into account.