gemfire-jruby 0.0.3 → 0.0.4

data/VERSION

@@ -1 +1 @@
-0.0.3
+0.0.4

data/gemfire-jruby.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{gemfire-jruby}
-  s.version = "0.0.3"
+  s.version = "0.0.4"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Alan McKean"]
-  s.date = %q{2010-01-28}
+  s.date = %q{2010-01-29}
   s.description = %q{"Uses Memcached API"}
   s.email = %q{alan.mckean@gemstone.com}
   s.extra_rdoc_files = [
@@ -45,54 +45,6 @@ Gem::Specification.new do |s|
      "doc/fr_method_index.html",
      "doc/index.html",
      "doc/rdoc-style.css",
-     "gemfire-jruby-demo/README",
-     "gemfire-jruby-demo/Rakefile",
-     "gemfire-jruby-demo/app/controllers/application_controller.rb",
-     "gemfire-jruby-demo/app/helpers/application_helper.rb",
-     "gemfire-jruby-demo/cache.xml",
-     "gemfire-jruby-demo/config/boot.rb",
-     "gemfire-jruby-demo/config/database.yml",
-     "gemfire-jruby-demo/config/environment.rb",
-     "gemfire-jruby-demo/config/environments/development.rb",
-     "gemfire-jruby-demo/config/environments/production.rb",
-     "gemfire-jruby-demo/config/environments/test.rb",
-     "gemfire-jruby-demo/config/initializers/backtrace_silencers.rb",
-     "gemfire-jruby-demo/config/initializers/inflections.rb",
-     "gemfire-jruby-demo/config/initializers/mime_types.rb",
-     "gemfire-jruby-demo/config/initializers/new_rails_defaults.rb",
-     "gemfire-jruby-demo/config/initializers/session_store.rb",
-     "gemfire-jruby-demo/config/locales/en.yml",
-     "gemfire-jruby-demo/config/routes.rb",
-     "gemfire-jruby-demo/db/seeds.rb",
-     "gemfire-jruby-demo/doc/README_FOR_APP",
-     "gemfire-jruby-demo/log/production.log",
-     "gemfire-jruby-demo/log/server.log",
-     "gemfire-jruby-demo/log/test.log",
-     "gemfire-jruby-demo/my.properties",
-     "gemfire-jruby-demo/public/404.html",
-     "gemfire-jruby-demo/public/422.html",
-     "gemfire-jruby-demo/public/500.html",
-     "gemfire-jruby-demo/public/favicon.ico",
-     "gemfire-jruby-demo/public/images/rails.png",
-     "gemfire-jruby-demo/public/index.html",
-     "gemfire-jruby-demo/public/javascripts/application.js",
-     "gemfire-jruby-demo/public/javascripts/controls.js",
-     "gemfire-jruby-demo/public/javascripts/dragdrop.js",
-     "gemfire-jruby-demo/public/javascripts/effects.js",
-     "gemfire-jruby-demo/public/javascripts/prototype.js",
-     "gemfire-jruby-demo/public/robots.txt",
-     "gemfire-jruby-demo/script/about",
-     "gemfire-jruby-demo/script/console",
-     "gemfire-jruby-demo/script/dbconsole",
-     "gemfire-jruby-demo/script/destroy",
-     "gemfire-jruby-demo/script/generate",
-     "gemfire-jruby-demo/script/performance/benchmarker",
-     "gemfire-jruby-demo/script/performance/profiler",
-     "gemfire-jruby-demo/script/plugin",
-     "gemfire-jruby-demo/script/runner",
-     "gemfire-jruby-demo/script/server",
-     "gemfire-jruby-demo/test/performance/browsing_test.rb",
-     "gemfire-jruby-demo/test/test_helper.rb",
      "gemfire-jruby.gemspec",
      "lib/gemfire-jruby.rb",
      "test/helper.rb",

data/lib/gemfire-jruby.rb

@@ -6,6 +6,8 @@ import com.gemstone.gemfire.distributed.DistributedSystem
 import com.gemstone.gemfire.cache.CacheFactory
 import com.gemstone.gemfire.cache.AttributesFactory
 import com.gemstone.gemfire.cache.client.PoolManager
+import com.gemstone.gemfire.cache.DataPolicy
+import com.gemstone.gemfire.cache.Scope
 
 include Java
 
@@ -20,22 +22,103 @@ module ActiveSupport
     	private_class_method :new
       
     	# GemFire is a Singleton. new() is hidden, so use getInstance() to both create the GemFire instance and to launch GemFire.
-    	#   There is an optional Hash that you can use to override any GemFire properties'.
-    	#   For example, GemFire.getInstance('locators' => 'localhost[10355]', 'mcast-port' => '0')
+    	#   The required Hash is used to configure clients and servers.
+    	#   For example, GemFire.getInstance('server', {'region-name'=> 'data', 'locators' => 'localhost:10355'})
     	# Since it is a Singleton, successive calls to GemFire.getInstance() will return the single
     	# instance that was instantiated by the first call.
-    	def GemFire.getInstance(hashOfGemFireProperties={})
-      	self.instance ||= new(hashOfGemFireProperties)
+      def GemFire.getInstance(role, options={})
+      	self.instance ||= new(role, options)
       end
 
-      def initialize(hashOfGemFireProperties)
+      def check_required_options(role, options)
+        # role must be client or server
+        if(role != 'client' && role != 'server') then
+          raise "The member role must be either client or server"
+        end
+        # ensure that we are using locators ... no multicast distribution is allowed
+        if (!options.include?('locators')) then
+          raise "Locators must be specified in the options"
+        end
+        if (role == 'server' && !options.include?('cacheserver-port')) then
+            raise "The server must have a cacheserver-port specified in the options"
+          end          
+        if (!options.include?('region-name')) then
+          raise "The region name must be specified in the options"
+        end
+      end
+      
+      def get_gemfire_properties(role, options)
         properties = Properties.new
-        hashOfGemFireProperties.each do |key, value|
-          properties.setProperty(key, value)
+        properties.setProperty('mcast-port', '0')
+        options.each do |key, value|
+          properties.setProperty(key, value) unless ((key == 'cacheserver-port') || (key == 'region-name') || (key == 'locators' && role == 'client'))
+        end
+        properties
+      end
+      
+      def get_client_attributes(options)
+        # configure the region attributes for client usage
+        attributesFactory = AttributesFactory.new
+        # clients have a Pool
+        poolFactory = PoolManager.createFactory
+        ipAndPort = options['locators'].split(':')
+        puts ipAndPort[0]
+        puts ipAndPort[1]
+        poolFactory.addLocator(ipAndPort[0], ipAndPort[1].to_i)
+        poolFactory.create("clientPool")
+        # clients do no peer-to-peer distribution
+        attributesFactory.setScope(Scope::LOCAL)
+        # clients either cache data locally (DataPolicy::NORMAL) or not (DataPolicy::EMPTY)
+        if (options['caching-enabled'] == 'true') then
+          attributesFactory.setDataPolicy(DataPolicy::NORMAL)
+        else
+          attributesFactory.setDataPolicy(DataPolicy::EMPTY)
         end
+        attributesFactory.setPoolName("clientPool")
+  	    regionAttributes = attributesFactory.create
+      end
+      
+      def get_server_attributes(options)
+        attributesFactory = AttributesFactory.new
+    	  if (options['data-policy'] == 'partition') then
+	        # it's a partitioned region
+	        attributesFactory.setDataPolicy(DataPolicy::PARTITION)
+    	    if (options['redundant-copies']) then
+      	    partitionAttributesFactory = PartitionAttributesFactory.new
+  	        partitionattributesFactory.setRedundantCopies(options['redundant-copies'].to_s)
+  	        partitionAttributes = partitionAttributesFactory.create
+  	        attributesFactory.setPartitionAttributes(partitionAttributes)
+	        end
+    	  elsif (!options['data-policy'] || (options['data-policy'] == 'replicate'))
+	        # it's a replicate region
+    	    attributesFactory.setDataPolicy(DataPolicy::REPLICATE)
+    	  else
+    	    raise "Data policy must be either 'replicate', 'partition', or unset (the default is replicate)"
+  	    end
+  	    regionAttributes = attributesFactory.create
+      end
+      
+      def initialize(role, options)      
+        # fill the GemFire properties from the options
+        self.check_required_options(role, options)
+        # join the distributed system
+        properties = get_gemfire_properties(role, options)
         system = DistributedSystem.connect(properties)
+      	# create the cache ... this will read a cache.xml
       	@cache = CacheFactory.create(system)
-      	@region = @cache.getRegion(System.getProperty("cachingRegionName") || "default")
+        # there is only one region
+        regionAttributes = nil
+      	if(role == 'client') then
+      	  # it's a client
+      	  regionAttributes = get_client_attributes(options)
+      	else
+      	  # it's a server
+          cacheServer = @cache.addCacheServer
+          cacheServer.setPort(options['cacheserver-port'])
+          cacheServer.start
+      	  regionAttributes = get_server_attributes(options)
+      	end 
+      	@region = @cache.createRegion(options['region-name'], regionAttributes)
       rescue CacheException => e
           logger.error("GemfireCache Creation Error (#{e}): #{e.message}")
     	end
@@ -125,6 +208,8 @@ module ActiveSupport
         result = query.execute
         selectResults?(result) ? toList(result) : result
       end
+      
+      private :check_required_options, :get_gemfire_properties, :get_server_attributes, :get_client_attributes,:toList, :selectResults?
     end
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: gemfire-jruby
 version: !ruby/object:Gem::Version 
-  version: 0.0.3
+  version: 0.0.4
 platform: ruby
 authors: 
 - Alan McKean
@@ -9,7 +9,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-01-28 00:00:00 -08:00
+date: 2010-01-29 00:00:00 -08:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -60,54 +60,6 @@ files:
 - doc/fr_method_index.html
 - doc/index.html
 - doc/rdoc-style.css
-- gemfire-jruby-demo/README
-- gemfire-jruby-demo/Rakefile
-- gemfire-jruby-demo/app/controllers/application_controller.rb
-- gemfire-jruby-demo/app/helpers/application_helper.rb
-- gemfire-jruby-demo/cache.xml
-- gemfire-jruby-demo/config/boot.rb
-- gemfire-jruby-demo/config/database.yml
-- gemfire-jruby-demo/config/environment.rb
-- gemfire-jruby-demo/config/environments/development.rb
-- gemfire-jruby-demo/config/environments/production.rb
-- gemfire-jruby-demo/config/environments/test.rb
-- gemfire-jruby-demo/config/initializers/backtrace_silencers.rb
-- gemfire-jruby-demo/config/initializers/inflections.rb
-- gemfire-jruby-demo/config/initializers/mime_types.rb
-- gemfire-jruby-demo/config/initializers/new_rails_defaults.rb
-- gemfire-jruby-demo/config/initializers/session_store.rb
-- gemfire-jruby-demo/config/locales/en.yml
-- gemfire-jruby-demo/config/routes.rb
-- gemfire-jruby-demo/db/seeds.rb
-- gemfire-jruby-demo/doc/README_FOR_APP
-- gemfire-jruby-demo/log/production.log
-- gemfire-jruby-demo/log/server.log
-- gemfire-jruby-demo/log/test.log
-- gemfire-jruby-demo/my.properties
-- gemfire-jruby-demo/public/404.html
-- gemfire-jruby-demo/public/422.html
-- gemfire-jruby-demo/public/500.html
-- gemfire-jruby-demo/public/favicon.ico
-- gemfire-jruby-demo/public/images/rails.png
-- gemfire-jruby-demo/public/index.html
-- gemfire-jruby-demo/public/javascripts/application.js
-- gemfire-jruby-demo/public/javascripts/controls.js
-- gemfire-jruby-demo/public/javascripts/dragdrop.js
-- gemfire-jruby-demo/public/javascripts/effects.js
-- gemfire-jruby-demo/public/javascripts/prototype.js
-- gemfire-jruby-demo/public/robots.txt
-- gemfire-jruby-demo/script/about
-- gemfire-jruby-demo/script/console
-- gemfire-jruby-demo/script/dbconsole
-- gemfire-jruby-demo/script/destroy
-- gemfire-jruby-demo/script/generate
-- gemfire-jruby-demo/script/performance/benchmarker
-- gemfire-jruby-demo/script/performance/profiler
-- gemfire-jruby-demo/script/plugin
-- gemfire-jruby-demo/script/runner
-- gemfire-jruby-demo/script/server
-- gemfire-jruby-demo/test/performance/browsing_test.rb
-- gemfire-jruby-demo/test/test_helper.rb
 - gemfire-jruby.gemspec
 - lib/gemfire-jruby.rb
 - test/helper.rb

data/gemfire-jruby-demo/README

@@ -1,243 +0,0 @@
-== Welcome to Rails
-
-Rails is a web-application framework that includes everything needed to create 
-database-backed web applications according to the Model-View-Control pattern. 
-
-This pattern splits the view (also called the presentation) into "dumb" templates
-that are primarily responsible for inserting pre-built data in between HTML tags.
-The model contains the "smart" domain objects (such as Account, Product, Person,
-Post) that holds all the business logic and knows how to persist themselves to
-a database. The controller handles the incoming requests (such as Save New Account,
-Update Product, Show Post) by manipulating the model and directing data to the view.
-
-In Rails, the model is handled by what's called an object-relational mapping
-layer entitled Active Record. This layer allows you to present the data from
-database rows as objects and embellish these data objects with business logic
-methods. You can read more about Active Record in
-link:files/vendor/rails/activerecord/README.html.
-
-The controller and view are handled by the Action Pack, which handles both
-layers by its two parts: Action View and Action Controller. These two layers
-are bundled in a single package due to their heavy interdependence. This is
-unlike the relationship between the Active Record and Action Pack that is much
-more separate. Each of these packages can be used independently outside of
-Rails.  You can read more about Action Pack in
-link:files/vendor/rails/actionpack/README.html.
-
-
-== Getting Started
-
-1. At the command prompt, start a new Rails application using the <tt>rails</tt> command
-   and your application name. Ex: rails myapp
-2. Change directory into myapp and start the web server: <tt>script/server</tt> (run with --help for options)
-3. Go to http://localhost:3000/ and get "Welcome aboard: You're riding the Rails!"
-4. Follow the guidelines to start developing your application
-
-
-== Web Servers
-
-By default, Rails will try to use Mongrel if it's are installed when started with script/server, otherwise Rails will use WEBrick, the webserver that ships with Ruby. But you can also use Rails
-with a variety of other web servers.
-
-Mongrel is a Ruby-based webserver with a C component (which requires compilation) that is
-suitable for development and deployment of Rails applications. If you have Ruby Gems installed,
-getting up and running with mongrel is as easy as: <tt>gem install mongrel</tt>.
-More info at: http://mongrel.rubyforge.org
-
-Say other Ruby web servers like Thin and Ebb or regular web servers like Apache or LiteSpeed or
-Lighttpd or IIS. The Ruby web servers are run through Rack and the latter can either be setup to use
-FCGI or proxy to a pack of Mongrels/Thin/Ebb servers.
-
-== Apache .htaccess example for FCGI/CGI
-
-# General Apache options
-AddHandler fastcgi-script .fcgi
-AddHandler cgi-script .cgi
-Options +FollowSymLinks +ExecCGI
-
-# If you don't want Rails to look in certain directories,
-# use the following rewrite rules so that Apache won't rewrite certain requests
-# 
-# Example:
-#   RewriteCond %{REQUEST_URI} ^/notrails.*
-#   RewriteRule .* - [L]
-
-# Redirect all requests not available on the filesystem to Rails
-# By default the cgi dispatcher is used which is very slow
-# 
-# For better performance replace the dispatcher with the fastcgi one
-#
-# Example:
-#   RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
-RewriteEngine On
-
-# If your Rails application is accessed via an Alias directive,
-# then you MUST also set the RewriteBase in this htaccess file.
-#
-# Example:
-#   Alias /myrailsapp /path/to/myrailsapp/public
-#   RewriteBase /myrailsapp
-
-RewriteRule ^$ index.html [QSA]
-RewriteRule ^([^.]+)$ $1.html [QSA]
-RewriteCond %{REQUEST_FILENAME} !-f
-RewriteRule ^(.*)$ dispatch.cgi [QSA,L]
-
-# In case Rails experiences terminal errors
-# Instead of displaying this message you can supply a file here which will be rendered instead
-# 
-# Example:
-#   ErrorDocument 500 /500.html
-
-ErrorDocument 500 "<h2>Application error</h2>Rails application failed to start properly"
-
-
-== Debugging Rails
-
-Sometimes your application goes wrong.  Fortunately there are a lot of tools that
-will help you debug it and get it back on the rails.
-
-First area to check is the application log files.  Have "tail -f" commands running
-on the server.log and development.log. Rails will automatically display debugging
-and runtime information to these files. Debugging info will also be shown in the
-browser on requests from 127.0.0.1.
-
-You can also log your own messages directly into the log file from your code using
-the Ruby logger class from inside your controllers. Example:
-
-  class WeblogController < ActionController::Base
-    def destroy
-      @weblog = Weblog.find(params[:id])
-      @weblog.destroy
-      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
-    end
-  end
-
-The result will be a message in your log file along the lines of:
-
-  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1
-
-More information on how to use the logger is at http://www.ruby-doc.org/core/
-
-Also, Ruby documentation can be found at http://www.ruby-lang.org/ including:
-
-* The Learning Ruby (Pickaxe) Book: http://www.ruby-doc.org/docs/ProgrammingRuby/
-* Learn to Program: http://pine.fm/LearnToProgram/  (a beginners guide)
-
-These two online (and free) books will bring you up to speed on the Ruby language
-and also on programming in general.
-
-
-== Debugger
-
-Debugger support is available through the debugger command when you start your Mongrel or
-Webrick server with --debugger. This means that you can break out of execution at any point
-in the code, investigate and change the model, AND then resume execution! 
-You need to install ruby-debug to run the server in debugging mode. With gems, use 'gem install ruby-debug'
-Example:
-
-  class WeblogController < ActionController::Base
-    def index
-      @posts = Post.find(:all)
-      debugger
-    end
-  end
-
-So the controller will accept the action, run the first line, then present you
-with a IRB prompt in the server window. Here you can do things like:
-
-  >> @posts.inspect
-  => "[#<Post:0x14a6be8 @attributes={\"title\"=>nil, \"body\"=>nil, \"id\"=>\"1\"}>,
-       #<Post:0x14a6620 @attributes={\"title\"=>\"Rails you know!\", \"body\"=>\"Only ten..\", \"id\"=>\"2\"}>]"
-  >> @posts.first.title = "hello from a debugger"
-  => "hello from a debugger"
-
-...and even better is that you can examine how your runtime objects actually work:
-
-  >> f = @posts.first
-  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
-  >> f.
-  Display all 152 possibilities? (y or n)
-
-Finally, when you're ready to resume execution, you enter "cont"
-
-
-== Console
-
-You can interact with the domain model by starting the console through <tt>script/console</tt>.
-Here you'll have all parts of the application configured, just like it is when the
-application is running. You can inspect domain models, change values, and save to the
-database. Starting the script without arguments will launch it in the development environment.
-Passing an argument will specify a different environment, like <tt>script/console production</tt>.
-
-To reload your controllers and models after launching the console run <tt>reload!</tt>
-
-== dbconsole
-
-You can go to the command line of your database directly through <tt>script/dbconsole</tt>.
-You would be connected to the database with the credentials defined in database.yml.
-Starting the script without arguments will connect you to the development database. Passing an
-argument will connect you to a different database, like <tt>script/dbconsole production</tt>.
-Currently works for mysql, postgresql and sqlite.
-
-== Description of Contents
-
-app
-  Holds all the code that's specific to this particular application.
-
-app/controllers
-  Holds controllers that should be named like weblogs_controller.rb for
-  automated URL mapping. All controllers should descend from ApplicationController
-  which itself descends from ActionController::Base.
-
-app/models
-  Holds models that should be named like post.rb.
-  Most models will descend from ActiveRecord::Base.
-
-app/views
-  Holds the template files for the view that should be named like
-  weblogs/index.html.erb for the WeblogsController#index action. All views use eRuby
-  syntax.
-
-app/views/layouts
-  Holds the template files for layouts to be used with views. This models the common
-  header/footer method of wrapping views. In your views, define a layout using the
-  <tt>layout :default</tt> and create a file named default.html.erb. Inside default.html.erb,
-  call <% yield %> to render the view using this layout.
-
-app/helpers
-  Holds view helpers that should be named like weblogs_helper.rb. These are generated
-  for you automatically when using script/generate for controllers. Helpers can be used to
-  wrap functionality for your views into methods.
-
-config
-  Configuration files for the Rails environment, the routing map, the database, and other dependencies.
-
-db
-  Contains the database schema in schema.rb.  db/migrate contains all
-  the sequence of Migrations for your schema.
-
-doc
-  This directory is where your application documentation will be stored when generated
-  using <tt>rake doc:app</tt>
-
-lib
-  Application specific libraries. Basically, any kind of custom code that doesn't
-  belong under controllers, models, or helpers. This directory is in the load path.
-
-public
-  The directory available for the web server. Contains subdirectories for images, stylesheets,
-  and javascripts. Also contains the dispatchers and the default HTML files. This should be
-  set as the DOCUMENT_ROOT of your web server.
-
-script
-  Helper scripts for automation and generation.
-
-test
-  Unit and functional tests along with fixtures. When using the script/generate scripts, template
-  test files will be generated for you and placed in this directory.
-
-vendor
-  External libraries that the application depends on. Also includes the plugins subdirectory.
-  If the app has frozen rails, those gems also go here, under vendor/rails/.
-  This directory is in the load path.