Paul Codding's Weblog » RoR http://www.paulcodding.com/blog My miscellaneous ramblings and how-to's Sat, 17 Jul 2010 02:59:34 +0000 en hourly 1 http://wordpress.org/?v=3.0.4 Upgrading a large RoR Project from 1.2.6 to 2.0.2 http://www.paulcodding.com/blog/2008/01/21/upgrading-a-large-ror-project-from-126-to-202/ http://www.paulcodding.com/blog/2008/01/21/upgrading-a-large-ror-project-from-126-to-202/#comments Tue, 22 Jan 2008 04:23:12 +0000 Paul Codding http://www.paulcodding.com/blog/2008/01/21/upgrading-a-large-ror-project-from-126-to-202/ This evening while upgrading a large Ruby on Rails application that I’ve been working on for the past year and a half, I ran into some issues upgrading to 2.0.2.  As you may know actionwebservice has been ousted from rails in favor of REST.  For those of us that depend on using SOAP for interoperability with other applications, we need it to work.  After spending a great deal of time googling to remove the following error:

`report_activate_error':
RubyGem version error: actionpack(2.0.2 not = 1.13.6) (Gem::LoadError)



I found this very helpful article about getting actionwebservices to run under Rails 2.0.2. I’ve yet to see the issues that some other users have seen when using actionwebservices with Rails 2.0.2, but we shall see in the coming days of using it. One thing I had to do that I didn’t really like was to freeze the rails gems into the project. I would rather not have them in my subversion repository.Another issue encountered was with installing gems that needed compilation on my OS X Leopard machine.  Luckily I found a great article detailing the use of the ARCHFLAGS environmental variable. So to install my postgres gem all I had to do was this:

$ sudo -s# export ARCHFLAGS="-arch i386"# gem install postgres

After that, the gem was installed and I no longer received any compile time errors. This stems from the universal binary support mechanism in OS X.

]]> http://www.paulcodding.com/blog/2008/01/21/upgrading-a-large-ror-project-from-126-to-202/feed/ 2 Utilizing Ruby on Rails Web Services with Java http://www.paulcodding.com/blog/2007/03/31/utilizing-ruby-on-rails-web-services-with-java/ http://www.paulcodding.com/blog/2007/03/31/utilizing-ruby-on-rails-web-services-with-java/#comments Sun, 01 Apr 2007 03:29:24 +0000 Paul Codding http://www.paulcodding.com/blog/?p=4 As part of a project I’m currently working on, I’ve had to integrate a RoR application with another developer’s Java code. At first glance, things looked to be fairly simple as I envisioned a simple Web Service communication between Java and Ruby would be a breeze…not so fast. Getting the two to play nice with each other took some time as I was unaware that RoR only supports the RPC/encoded style/use and not Document/literal. After getting a prototyped client written read using Spring-ws (does not support RPC/encoded) I quickly found out that it was going to go nowhere fast. I ended up choosing to use Apache Axis as I’ve used it for a previous project, and I knew for sure it supported RPC/encoded.

Part of the reason for this blog is to share information from developer to developer issues that I’ve encountered that have either been unable or too busy to find solutions to. In this case my solution is to let the reader know that the best bet client to use when consuming RoR web services in Java is Apache Axis. If anyone would enjoy a code example or two I’d be glad to oblige…although the artifacts generated by Axis 1.4 are fairly involved, the process is fairly easy especially when using the SoapUI tool to generate the artifacts based on the RoR WSDL e.g. http://localhost:3000/web_service_name/service.wsdl .

]]> http://www.paulcodding.com/blog/2007/03/31/utilizing-ruby-on-rails-web-services-with-java/feed/ 1