similar to: Rails article on consuming a web service

There (yet) another discussion going on on the O''Reilly web logs about J E5, complexity and the competitors (i.e. Rails et al). See http://www.oreillynet.com/windows/blog/2006/07/the_beginning_of_the_end_for_j.html. Seems this was spawned by my own article available at: http://www.soaranch.com/articles/2006/7/11/soa-and-rails-part-1.html. My response to this discussion is at:

I am trying to copy files to a password protected drive which is "Ranch" at TACC from another network drive. I am logged in to the source drive and can run R there. The following code does not even find the destination folder. file.copy("sourcedrive/file.tar", " username@ranch.tacc.utexas.edu/uniqueID/destinationfolder/file.tar", overwrite = FALSE) Thanks in

Hi all - I have a Player model. The database looks like this: +-------------------+--------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +-------------------+--------------+------+-----+---------+----------------+ | id | int(11) | NO | PRI | NULL | auto_increment | | fname |

hey, i have made a webservice http://twodecode.pilot.localhost.be:3000/backend/wsdl here i can see the wsdl file i have a method string Authenticate(string twa, string login, string pass) when i do /invoke i can test it, this all works backend_api.rb class BackendApi < ActionWebService::API::Base api_method :authenticate, :expects => [{:twa =>:string},{:login

Can someone shed some light on how to convert an Exception to a SOAPFault on Rails 1.0/AWS 1.0? I''ve been digging through the source code and see that in soap_protocol.rb there is a method called encode_response() that seems to perform the translation of an Exception to a SOAPFault. However, if I use the following code block within my Web Service controller: def

Hi! I''ve successfully created a Rails web service. I can connect to it with an XML-RPC client, without any problems at all. However, when I try to use a gSOAP application to connect to the web service, it doesn''t work. The back trace that I get is at the end of this message. From the back trace, it appears that the SOAP request is not being recognized as a SOAP

Hi! I''ve successfully created a Rails web service. I can connect to it with an XML-RPC client, without any problems at all. However, when I try to use a gSOAP application to connect to the web service, it doesn''t work. The back trace that I get is at the end of this message. From the back trace, it appears that the SOAP request is not being recognized as a SOAP request, and

I am experiencing a similar problem, not with gSOAP, but with Apache''s SOAP library. Just like Guido, XML-RPC works perfectly, but the SOAP request processing fails during protocol discovery. Rail''s SOAP client also works perfectly, so I''m fairly certain the error is not in my code. I am new to both ActionWebService and the Ruby XMLRPC module, so I''m

I have defined a web service to return information from a database as follows. class BackendApi < ActionWebService::API::Base api_method :find_all_vobs, :returns => [[:int]] api_method :find_vob_by_id, :expects => [:int], :returns => [Vob] class BackendController < ApplicationController wsdl_service_name ''Backend''

Besides ranch networks and borderware, what other SIP aware firewalls for the SOHO/medium market exists? -- ------------------------------------------------------------ Erick Perez Panama Sistemas Integradores de Telefonia IP y Soluciones Para Centros de Datos Panama, Republica de Panama Cel Panama. +(507) 6694-4780 ------------------------------------------------------------

I''d like to split up my directly dispatched controller into a layered dispatch setup with one controller and two services derived from ActionWebService::Base. However, in doing this I found that logger is not a class_variable of AWS::Base. This kind of scares me away from using the layered dispatch mode, as I''d like to have logging in the method implementations. Is there a clean

I''m working with an ActionWebService client talking to an ActionWebService server through one of DataPower''s XS40 XML Security Gateways. One of the intrinsic functions of this gateway is automatic SOAP schema validation. When testing some failure cases, I noticed that SOAP Faults returned by ActionWebService aren''t schema valid to the SOAP 1.1 schema, specifically:

I am working on building a prototype for a Rails Web Service that will be used potentially by non-ruby/rails languages. When testing using the *invoke* scaffold I have no problem getting the correct result, however when using a 3rd party PHP client I get a *NoMethodError (undefined method `collect'' for #<SOAP::SOAPNil:0x24ea1bc>):* exception from the rails Webrick web server.

This deals with the Rails book, but ActionWebService in general. I''m having trouble getting the Rails book''s example in the Web Service chapter working. Everything else works (all the ''depot'' site features up to that point have been built and work). I don''t think it''s an issue with the book code being wrong, because the ActionWebService API

I''m trying to consume a webservice from my rails application and have discovered an interesting problem. I can call webservice functions just fine, as long as they do not require any arguments, but function that do require arguments do not work. The arguments are sent as either null or an empty string. My API has these method definitions: api_method :otherFunction,

>> There is no link between SOA and NS except they share the zone.... Really... ? i dont agree.. SOA specifies the DNS server providing authoritative information about a domain, so looks to me its direcly related to NameServers. SOA contains the primary (NS) server of the domain. Looks to me its related... Below it nice explained how DNS works. That a SOA not (always) related is

Running into a strange bug using the mongrel upload progress plugin handler, sitting in front of a simple mongrel. The bug appears on an old Xserve (mac OS X 10.3.9 powerpc), but not on my macbook pro, or even a generic 686 linux box. http://pastie.textmate.org/98341 The gist of the pastie above shows that attempts through the browser and curl are actually hitting the filesController, as

So I''m playing with AWS. I''ve got a thing called a gallery. I''d like to return a list of them. I can do this fine if I want to return my ActiveRecord objects: class WxApiApi < ActionWebService::API::Base api_method :list_galleries, :expects=>[{:login=>:string}], :returns => [[Gallery]] end But the ActiveRecord object exposes a

Hello, I have seen some odd behaviour of my Web Services code plus some ''similar'' postings to this list, so I believe this may be a bug in Rails. But I''m failry new to RoR, so maybe I''m doing something wrong. I''ll explain: I have a WS API defined, communicating with a remote system that expects a stucture: When defined like this (all

Hi, I just upgraded to soap4r 1.5.5, and now all my Rails Functional tests for the action_web_services fail as follows, any ideas what I did wrong? Thanks TypeError: can''t modify frozen object /usr/local/lib/ruby/1.8/xsd/qname.rb:78:in `name='' /usr/local/lib/ruby/1.8/soap/rpc/element.rb:118:in `set_param''