ooor 1.4.1 → 1.4.2

data/README.md

@@ -44,11 +44,17 @@ But OOOR makes it straightforward to use a standard OpenERP models as your persi
 
 An other reason why you might want to use OOOR is because you would like to code essentially a Rails or say web application
 (because you know it better, because the framework is cleaner or because you will reuse something, possibly Java libraries though JRuby)
-but you still want to benefit from OpenERP features.
+but you still want to benefit from OpenERP features. Notice that despite its name OOOR doens't hold a dependency upon Rails anymore.
 
 Yet an other typicall use case would be to test your OpenERP application/module using Rails best of bread BDD Ruby frameworks such as RSpec or Cucumber.
+We use RSpec to test OOOR againt OpenERP [here](http://github.com/rvalyi/ooor/blob/master/spec/ooor_spec.rb) and thanks to the initiative of CampToCamp, the OpenERP community tests OpenERP business features extensively
+using Cucumber in [OEPScenario](http://launchpad.net/oerpscenario).
 
-Finally you might also want to use OOOR simply to expose your OpenERP through REST to other consumer applications. Since OOOR just does that too out of the box.
+An other usage of OOOR, is it ability to bridge the OpenERP Python world and and the Java world thanks to its JRuby compatibility. This is especially useful in to do extensive "Data Integration" with OpenERP and benefit from the
+most powerful Java based ETL's. The main project here is [TerminatOOOR](http://github.com/rvalyi/terminatooor), a Pentaho ETL Kettle 4 plugin allowing to push/pull data into/from OpenERP with an incomparable flexibility and yet benefit
+all standard ETL features, including the AgileBI OLAP business intelligence plugin.
+
+Finally you might also want to use OOOR simply to expose your OpenERP through REST to other consumer applications using [the OOOREST project](http://github.com/rvalyi/ooorest).
 
 
 
@@ -56,9 +62,9 @@ How?
 ------------
 
 OpenERP is a Python based open source ERP. Every action in OpenERP is actually invokable as a webservice (SOA orientation, close to being RESTful).
-OOOR just takes advantage of brings this power your favorite web development tool - Rails - with OpenERP domain objects and business methods.
+OOOR just takes advantage of it.
 
-OOOR aims at being a very simple piece of code (< 500 lines of code; e.g no bug, easy to evolve) adhering to Rails standards.
+OOOR aims at being a very simple piece of code (< 500 lines of code; e.g no bug, [heavility tested](http://github.com/rvalyi/ooor/blob/master/spec/ooor_spec.rb), easy to evolve) adhering to Rails standards.
 So instead of re-inventing the wheel, OOOR basically just sits on the top of Rails [ActiveResource::Base](http://api.rubyonrails.org/classes/ActiveResource/Base.html), the standard way of remoting you ActiveRecord Rails models with REST.
 
 Remember, ActiveResource is actually simpler than [ActiveRecord](http://api.rubyonrails.org/classes/ActiveRecord/Base.html). It's aimed at remoting ANY object model, not necessarily ActiveRecord models.
@@ -66,13 +72,21 @@ So ActiveResource is only a subset of ActiveRecord, sharing the common denominat
 
 OOOR implements ActiveResource public API almost fully. It means that you can remotely work on any OpenERP model using [the standard ActiveResource API](http://api.rubyonrails.org/classes/ActiveResource/Base.html).
 
-But, OOOR goes actually a bit further: it does implements model associations (one2many, many2many, many2one, single table inheritance).
+But, OOOR goes actually a bit further: it does implements model associations (one2many, many2many, many2one, single table inheritance, polymorphic associations...).
 Indeed, when loading the OpenERP models, we load the relational meta-model using OpenERP standard datamodel introspection services.
 Then we cache that relational model and use it in OpenObjectResource.method_missing to load associations as requested.
 
 OOOR also extends ActiveResource a bit with special request parameters (like :domain or :context) that will just map smoothly to the OpenERP native API, see API.
 
 
+Trying it simply
+------------
+
+If you have Java 1.6+ installed, then the easiest way to tryout OOOR might be to download the [TerminatOOOR zip](http://github.com/rvalyi/terminatooor/downloads)
+and double-click on jruby-ooor.jar or launch it by command line with java -jar jruby-ooor.jar: it will launch an OOOR console with helpful auto-completion (hit 'tab') on OpenERP business objects.
+
+
+
 Installation
 ------------
 
@@ -95,6 +109,8 @@ Let's test OOOR in an irb console (irb command):
 This should load all your OpenERP models into Ruby proxy Activeresource objects. Of course there are option to load only some models.
 Let's try to retrieve the user with id 1:
     $ ResUsers.find(1)
+	
+(in case you have an error like "no such file to load -- net/https", then on Debian/Ubuntu, you might need to do before: apt-get install libopenssl-ruby)
     
     
 ### (J)Ruby on Rails application:
@@ -115,8 +131,8 @@ You can then use all the OOOR API upon all loaded OpenERP models in your regular
 A good way to start playing with OOOR is inside the console, using:
     $ ruby script/console #or jruby script/console on JRuby of course
 
-Note: when boostraping Ooor in a Rails application, the default Ooor instance is stored in the OOOR constant.
-So for instance you can know all loaded models doing OOOR.all_loaded_models; this is used by [OooREST](http://github.com/rvalyi/ooorest) to register all the REST controllers.
+Note: when boostraping Ooor in a Rails application, the default Ooor instance is stored in the Ooor.default_ooor variable.
+So for instance you can know all loaded models doing Ooor.default_ooor variable.loaded_models; this is used by [OooREST](http://github.com/rvalyi/ooorest) to register all the REST controllers.
 
 Enabling REST HTTP routes to your OpenERP models:
 The REST Controller layer of OOOR has been moved as a thin separate gem called [OooREST](http://github.com/rvalyi/ooorest).
@@ -273,7 +289,7 @@ Call old style wizards:
     $ TODO test and document new osv_memory wizards API
 
 
-Absolute OpeNERP ids aka ir_model_data:
+Absolute OpenERP ids aka ir_model_data:
 
 just like Rails fixtures, OpenERP supports absolute ids for its records, especially those imported from XML or CSV.
 We are here speaking about the string id of the XML or CSV records, eventually prefixed by the module name.

data/lib/app/models/open_object_resource.rb

@@ -40,7 +40,7 @@ class OpenObjectResource < ActiveResource::Base
     def const_get(model_key)
       klass_name = class_name_from_model_key(model_key)
       klass = (self.scope_prefix ? Object.const_get(self.scope_prefix) : Object).const_defined?(klass_name) ? (self.scope_prefix ? Object.const_get(self.scope_prefix) : Object).const_get(klass_name) : @ooor.define_openerp_model({'model' => model_key}, self.scope_prefix)
-      klass.reload_fields_definition unless klass.fields_defined
+      klass.reload_fields_definition()
       klass
     end
 
@@ -175,7 +175,7 @@ class OpenObjectResource < ActiveResource::Base
     end
 
     def cast_answer_to_ruby!(answer)
-      reload_fields_definition() unless self.fields_defined
+      reload_fields_definition()
 
       def cast_map_to_ruby!(map)
         map.each do |k, v|
@@ -219,7 +219,7 @@ class OpenObjectResource < ActiveResource::Base
           domain.push [k.to_s, '=', v]
         end
       end
-      ids = rpc_execute('search', domain, context)
+      ids = rpc_execute('search', domain, options[:offset] || 0, options[:limit] || false,  options[:order] || false, context)
       !ids.empty? && ids[0].is_a?(Integer) && find_single(ids, options) || []
     end
 
@@ -324,7 +324,7 @@ class OpenObjectResource < ActiveResource::Base
   def reload_from_record!(record) load(record.attributes, record.relations) end
 
   def load(attributes, relations={})#an attribute might actually be a relation too, will be determined here
-    self.class.reload_fields_definition() unless self.class.fields_defined
+    self.class.reload_fields_definition()
     raise ArgumentError, "expected an attributes Hash, got #{attributes.inspect}" unless attributes.is_a?(Hash)
     @prefix_options, attributes = split_options(attributes)
     @relations = relations
@@ -381,7 +381,8 @@ class OpenObjectResource < ActiveResource::Base
     if default_get_list == []
       load(attributes)
     else
-      load(rpc_execute("default_get", default_get_list || self.class.fields && self.class.fields.keys || rpc_execute("fields_get").keys, @object_session[:context]).symbolize_keys!.merge(attributes.symbolize_keys!))
+      self.class.reload_fields_definition()
+      load(rpc_execute("default_get", default_get_list || self.class.fields.keys + self.class.relations_keys, @object_session[:context]).symbolize_keys!.merge(attributes.symbolize_keys!))
     end
   end
 
@@ -398,7 +399,7 @@ class OpenObjectResource < ActiveResource::Base
 
   #compatible with the Rails way but also supports OpenERP context
   def update(context={}, reload=true)
-    rpc_execute('write', self.id, to_openerp_hash!, context)
+    rpc_execute('write', [self.id], to_openerp_hash!, context)
     reload_from_record!(self.class.find(self.id, :context => context)) if reload
   end
 
@@ -442,9 +443,9 @@ class OpenObjectResource < ActiveResource::Base
   # ******************** fake associations like much like ActiveRecord according to the cached OpenERP data model ********************
 
   def relationnal_result(method_name, *arguments)
-    self.class.reload_fields_definition unless self.class.fields_defined
+    self.class.reload_fields_definition()
     if self.class.many2one_relations.has_key?(method_name)
-      load_relation(self.class.many2one_relations[method_name]['relation'], @relations[method_name][0], *arguments)
+      load_relation(self.class.many2one_relations[method_name]['relation'], @relations[method_name].is_a?(Integer) && @relations[method_name] || @relations[method_name][0], *arguments)
     elsif self.class.one2many_relations.has_key?(method_name)
       load_relation(self.class.one2many_relations[method_name]['relation'], @relations[method_name], *arguments)
     elsif self.class.many2many_relations.has_key?(method_name)
@@ -464,7 +465,7 @@ class OpenObjectResource < ActiveResource::Base
     return super if attributes.has_key?(method_key)
     return rpc_execute(method_name, *arguments) unless arguments.empty? || is_assign
 
-    self.class.reload_fields_definition() unless self.class.fields_defined
+    self.class.reload_fields_definition()
 
     if is_assign
       known_relations = self.class.relations_keys + self.class.many2one_relations.collect {|k, field| self.class.const_get(field['relation']).relations_keys}.flatten

data/spec/ooor_spec.rb

@@ -110,6 +110,8 @@ describe Ooor do
       it "should support OpenERP context in finders" do
         p = ProductProduct.find(1, :context => {:my_key => 'value'})
         p.should_not be_nil
+        products = ProductProduct.find(:all, :context => {:lang => 'es_ES'})
+        products.should be_kind_of(Array)
       end
 
       it "should support OpenERP search method" do
@@ -180,7 +182,7 @@ describe Ooor do
       it "should support context when instanciating collections" do
         products = ProductProduct.find([1, 2, 3], :context => {:lang => 'en_US', :user_id=>1, :password => 'admin'})
         p = products[0]
-        p.object_session[:context][:lang] .should == 'en_US'
+        p.object_session[:context][:lang].should == 'en_US'
         p.object_session[:user_id].should == 1
         p.object_session[:password].should == "admin"
         p.save
@@ -239,6 +241,11 @@ describe Ooor do
     end
 
     describe "Relations assignations" do
+      it "should be able to assign many2one relations on new" do
+        s = SaleOrder.new(:partner_id => 2)
+        s.partner_id.id.should == 2
+      end
+
       it "should be able to do product.taxes_id = [1,2]" do
         p = ProductProduct.find(1)
         p.taxes_id = [1, 2]

metadata

@@ -3,34 +3,35 @@ name: ooor
 version: !ruby/object:Gem::Version 
   prerelease: false
   segments: 
-  - 1
-  - 4
-  - 1
-  version: 1.4.1
+    - 1
+    - 4
+    - 2
+  version: 1.4.2
 platform: ruby
 authors: 
-- Raphael Valyi - www.akretion.com
+  - Raphael Valyi - www.akretion.com
 autorequire: 
 bindir: bin
 cert_chain: []
 
-date: 2010-07-06 00:00:00 -03:00
+date: 2010-09-15 00:00:00 -03:00
 default_executable: 
 dependencies: 
-- !ruby/object:Gem::Dependency 
-  name: activeresource
-  prerelease: false
-  requirement: &id001 !ruby/object:Gem::Requirement 
-    requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        segments: 
-        - 2
-        - 3
-        - 1
-        version: 2.3.1
-  type: :runtime
-  version_requirements: *id001
+  - !ruby/object:Gem::Dependency 
+    name: activeresource
+    prerelease: false
+    requirement: &id001 !ruby/object:Gem::Requirement 
+      none: false
+      requirements: 
+        - - ">="
+          - !ruby/object:Gem::Version 
+            segments: 
+              - 2
+              - 3
+              - 1
+            version: 2.3.1
+    type: :runtime
+    version_requirements: *id001
 description: OOOR exposes business object proxies to your Ruby (Rails or not) application, that map seamlessly to your remote OpenObject/OpenERP server using webservices. It extends the standard ActiveResource API.
 email: rvalyi@akretion.com
 executables: []
@@ -40,20 +41,20 @@ extensions: []
 extra_rdoc_files: []
 
 files: 
-- README.md
-- agpl-3.0-licence.txt
-- lib/ooor.rb
-- ooor.yml
-- lib/app/models/open_object_resource.rb
-- lib/app/models/uml.rb
-- lib/app/models/base64.rb
-- lib/app/models/db_service.rb
-- lib/app/models/common_service.rb
-- lib/app/ui/action_window.rb
-- lib/app/ui/client_base.rb
-- lib/app/ui/form_model.rb
-- lib/app/ui/menu.rb
-- spec/ooor_spec.rb
+  - README.md
+  - agpl-3.0-licence.txt
+  - lib/ooor.rb
+  - ooor.yml
+  - lib/app/models/open_object_resource.rb
+  - lib/app/models/uml.rb
+  - lib/app/models/base64.rb
+  - lib/app/models/db_service.rb
+  - lib/app/models/common_service.rb
+  - lib/app/ui/action_window.rb
+  - lib/app/ui/client_base.rb
+  - lib/app/ui/form_model.rb
+  - lib/app/ui/menu.rb
+  - spec/ooor_spec.rb
 has_rdoc: true
 homepage: http://github.com/rvalyi/ooor
 licenses: []
@@ -62,25 +63,27 @@ post_install_message:
 rdoc_options: []
 
 require_paths: 
-- lib
+  - lib
 required_ruby_version: !ruby/object:Gem::Requirement 
+  none: false
   requirements: 
-  - - ">="
-    - !ruby/object:Gem::Version 
-      segments: 
-      - 0
-      version: "0"
+    - - ">="
+      - !ruby/object:Gem::Version 
+        segments: 
+          - 0
+        version: "0"
 required_rubygems_version: !ruby/object:Gem::Requirement 
+  none: false
   requirements: 
-  - - ">="
-    - !ruby/object:Gem::Version 
-      segments: 
-      - 0
-      version: "0"
+    - - ">="
+      - !ruby/object:Gem::Version 
+        segments: 
+          - 0
+        version: "0"
 requirements: []
 
 rubyforge_project: 
-rubygems_version: 1.3.6
+rubygems_version: 1.3.7
 signing_key: 
 specification_version: 3
 summary: OOOR - OpenObject On Rails