How to use it

Just put this in your Gemfile:

gem "infopark_reactor"

Supported versions

Following versions of infopark_rails_connector/infopark_fiona_connector and rails are currently supported:

ruby version	rails version	rails_connector version	fiona_connector version
1.9.3-p547	3.2.22	6.9.1.3.22208381	6.9.1.3.22208381
1.9.3-p547	3.2.22	6.9.4	6.9.4
2.0.0-p648	3.2.22.2	6.9.1.3.22208381	6.9.1.3.22208381
2.1.8	4.0.13	none	6.10.0.beta1
2.1.8	4.1.14	none	6.10.0.beta1
2.1.8	4.1.14	none	7.0.0
2.2.4	4.1.14	none	7.0.0
2.2.6	4.2.7.1	none	7.0.1.beta2
2.2.6	4.2.7.1	none	7.0.1
2.2.6	4.2.7.1	none	7.0.1
2.6.6	5.x	none	7.0.1
2.7.x	>5.2	none	7.0.1
2.7.x	~>6.0	none	7.0.1
3.0.4	~>6.0	none	7.0.1
3.1.x	~>6.0	none	7.0.1

Fiona versions: 7.0.2, 7.0.1, 7.0.0, 6.10.2, 6.10.0, 6.9.0, 6.8.0, 6.7.3 and 6.7.2 are supported.

REACTOR

RailsConnector EnhAnCements for TCL lOveRs. You all love RailsConnector. I know you do. It delivers nice features and great performance. And yet... An yet you always knew that something is missing. You had this feeling when writing TCL code. You had this feeling when fiddling in Fiona GUI. Yes. You know it. You are a Rails coder: BeatufiulPage.create(:name => 'Better page', :parent => '/best/pages', :title => 'Yes, it is better'). Write layer is missing in RailsConnector. And it shows.

So, here you have it: REACTOR, writing layer for RailsConnector, tightly integrated with ActiveRecord. Maybe some of you don't like long and creative descriptions. Maybe some of you are convinced with running code:

BeatufiulPage.create(:name => 'Better page', :parent => '/best/pages', :title => 'Yes, it is better') do |page|
  page.body = '<a href="/can/handle/links/too">link</a>'
  page.save!
  page.release!
end

other_page = OtherPage.last
other_page.take!

not_a_page = SomeObject.first
not_a_page.some_attribute = 'a value' # types: string, html, enum
not_a_page.multienum_attr = ['somevalue'] # multienum
not_a_page.some_date_attribute = Time.now # date
not_a_page.some_date_attribute = '20111011083526' # date
not_a_page.some_date_attribute = '2011-11-11'

not_a_page.release! if not_a_page.valid?(:release)

All of the above are examples of what can be done with Persistence, Validations, Attributes. There is more:

• all standard ActiveModel callbacks + *_release callbacks
• Validations in three contexts: create, update, release
• If something works with ActiveRecord, there is a high chance it works with REACTOR too!
• Rails 3 API

What about links? Every object on my page is linked with 1000 other objects! I need links! Don't worry, they are there. Not perfectly supported yet, but you can set them:

some_obj.link_list_attr = 'http://google.com'
some_obj.link_list_attr = Obj.last
some_obj.link_list_attr = '/path/to/obj'

And I haven't forgotten that they are lists of links:

some_obj.link_list_attr = ['http://google.com', Obj.last, '/path/to/obj']

Yes, that is nice, you say, but what if I also wan't to set a link title? No problem, here is how:

some_obj.link_list_attr = {:url => 'http://google.com', :title => 'title of my link'}
some_obj.link_list_attr = {:destination_object => Obj.last, :title => 'title of my link'}
some_obj.link_list_attr = {:destination_object => '/path/to/obj', :title => 'title of my link', :fragment => 'anchor', :search =>'some=get&parameters=true'}

This also works for multiple links:

some_obj.link_list_attr = [ {:url => 'http://google.com', :title => 'title of my link'}, {:destination_object => Obj.last, :title => 'other title'}]

You can also manipulate linklist with array methods (for example #delete_at) and

some_obj.link_list_attr << '/path/to/obj'
some_obj.link_list_attr << {:url => 'http://yahoo.com', :title => 'yahoo link'}

One more thing: you can upload files too!

binary_obj.upload(File.open('/my/file'), 'txt')
binary_obj.save!

Or:

binary_obj.upload(File.read('/my/file'), 'txt')
binary_obj.save!

WARNING If your are planning to upload anything larger than 10kB it is strongly advised to use Reactor::StreamingUpload module. This module allows to stream files of any size (provided you supply them through File.open and not read them yourself into memory). It is also much, much more efficient than the traditional method.

Permissions are checked also! And your user is automatically set according to JSESSIONID cookie.

Workflow support is provided together with comments (just pass your comment as string to the relevant method):

obj.edit!('draft version created')
obj.forward!('please add your text')
# as other user
obj.take!
obj.release!('text added and released')

KNOWN BUGS/ISSUES

Awesome! What is missing/WHAT I NEED TO BE AWARE OF:

• When setting a linklist all links are overwritten. Don't do it like 10 million times if you don't want to risk reaching billion ids.
• Link position cannot be directly manipulated (it is implicit through array order)
• Validations are implemented completely in Rails, there is no call to CM, so all you TCL validation callbacks aren't executed
• You can change the obj_class of an obj, but after save you should get yourself a new instance, otherwise many things are simply broken
• You have to save an object before you can upload data (i.e. upload works only on existing objects)

HOW TO INSTALL

1. Include in your Gemfile
2. bundle
3. Add initializer for Reactor if you haven't done so already
4. Include modules into your Obj

CONFIGURING CMS ACCESS

config/initializers/reactor.rb:

Reactor::Configuration.xml_access = {
  :host => 'localhost', # Fiona host
  :port => 6001, # CM http port (TCL port + 1)
  :id => '1234', # leave it as is

  :username => 'root', # default user for all requests
  :secret => 'password' # instance secret
}

USING WITH THE NEWEST RAILS CONNECTOR

Recent versions of Rails Connector deprecated the usage of ObjExtenions module. Therefore, you have to create an Obj model which inherits the RailsConnector::BasicObj class. **For best compatibility do not call that model anything other that Obj!

app/models/obj.rb:

class Obj < RailsConnector::BasicObj
  include Reactor::Main
end

USING WITH OLDER RAILS CONNECTOR

Older version of Rails Connector support extensions to the RailsConnector::Obj class through ObjExtensions module. Use following code for the best compatibility.

lib/obj_extensions.rb:

require 'meta'
module ObjExtensions
  def self.enable
    Obj.class_eval do
      include RailsConnector::Meta

      include Reactor::Legacy::Base       # core module
      include Reactor::Attributes::Base   # core module
      include Reactor::Persistence::Base  # core module

      include Reactor::Validations::Base  # optional module,
                                          #  enables Rails validations

      include Reactor::Permission::Base   # optional module,
                                          #  enables permission checking

      include Reactor::Workflow::Base     # optional module,
                                          #  enables workflow API

      include Reactor::StreamingUpload::Base
                                          # optional module,
                                          #  enables streaming interface for
                                          #  uploads (strongly recommended!)
    end
  end
end

DOCUMENTATION

Core and optional modules are pretty well documented. If you are looking for example usages, you will find plenty of them in test app under spec folder.

MIGRATIONS

Reactor::Migrations is a Rails gem that makes working with Fiona just as easy as with Rails native migrations. Reactor::Migrations stores it's versioning information inside CM and thus it is compatible with all backup solutions. Please note the fact, that Reactor cannot account for manual modifications made to the CM (although it gives it's best)

Disclaimer

The code has been deployed and run for months. It showed itself to be stable and dependable. It may not work for you, although it should.

Installation

config/initializers/reactor.rb: Reactor::Configuration.xml_access = { :host => 'localhost', # Fiona host :port => 6001, # CM http port (TCL port + 1) :id => '1234', # leave it as is

:username => 'root', # default user for all requests :secret => 'MYSECRET' # instance secret! }

Example

rails g cm:migration ExampleMigration

edit cm/migrate/[timestamp]_example_migration.rb ... def self.up create_attribute :name => "test_attribute", :type => "enum" do set :values, ["value1", "value2"] set :title, "test attr" end

create_class :name => "ExampleClass", :title =>"Beispiel", :type => "publication" do
  set :title, {"Beispielvorlage" => {:lang => :de}, "Example obj class" => {:lang => :en}}
  take :authors, :mandatory => true # adds existing mandatory ! attribute named "authors"
  take :contributors # adds existing attribute named "authors"
  take :test_attribute, :preset => "value2" # we just created it!
  preset :title, "Default title" # sets default value for title of any ExampleClass object
end

create_attribute_group :obj_class => 'ExampleClass', :name => 'my_custom_group' do
  set :title, {'Deutscher Titel' => {:lang => :de}, 'English Title' => {:lang => :en}}
  set :index, 0

  add_attributes ['authors', 'contributors']
end

update_attribute_group :obj_class => 'ExampleClass', :name => 'my_custom_group' do
  add_attributes    [ 'test_attribute' ]
  remove_attributes [ 'contributors' ]

  set :index, 1
end

update_attribute_group :obj_class => 'ExampleClass', :name => 'my_custom_group' do
  # overwrite previous changes
  set :attributes, ['contributors']
end

end

def self.down delete_attribute_group :obj_class => 'ExampleClass', :name => 'my_custom_group' delete_class :name => 'ExampleClass' delete_attribute :name => 'test_attribute' end ... and finally

rake cm:migrate

You can also type

rake cm:migrate VERSION=0

to revert any changes (VERSION allows you to migrate to a specific version too).

That's all! Enjoy!

Copyright (c) 2011-2017 Tomasz Przedmojski, tomasz.przedmojski@infopark.de, Infopark AG

BUGS, FEATURE REQUESTS?

Open issue on github or make a pull request! Don't be shy :)