1. 06 4月, 2005 3 次提交
  2. 05 4月, 2005 3 次提交
  3. 04 4月, 2005 1 次提交
  4. 03 4月, 2005 4 次提交
  5. 02 4月, 2005 2 次提交
  6. 31 3月, 2005 2 次提交
  7. 29 3月, 2005 2 次提交
  8. 28 3月, 2005 2 次提交
  9. 26 3月, 2005 1 次提交
  10. 25 3月, 2005 1 次提交
  11. 23 3月, 2005 1 次提交
  12. 22 3月, 2005 1 次提交
  13. 20 3月, 2005 1 次提交
  14. 16 3月, 2005 1 次提交
  15. 10 3月, 2005 2 次提交
  16. 04 3月, 2005 2 次提交
  17. 03 3月, 2005 1 次提交
  18. 01 3月, 2005 1 次提交
  19. 28 2月, 2005 1 次提交
    • L
      Make all custom types and method calls are declared in the 'urn:ActionWebService' · 100015cd
      Leon Breedt 提交于
      namespace as a default, fixes SOAP marshaling for .NET, a regression since the merge.
      
      Make array annotation be recursive in WS::Marshaling::SoapMarshaling, this makes
      typed arrays buried in nested structures still be annotated correctly.
      
      Support :layered dispatching mode for XML-RPC namespaced method names.
      
      Change WS::ParamInfo.create signature to require type_binding, and update all
      uses of this.
      
      Restore #default_api_method functionality, fixes a regression since the merge.
      
      Fix marshalling of ActiveRecord::Base derivatives, fixes a regression since the merge.
      
      This changeset closes #676, #677, and #678.
      
      
      git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@811 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
      100015cd
  20. 26 2月, 2005 1 次提交
    • L
      merged the changes for the upcoming 0.6.0: · 6f5a7b20
      Leon Breedt 提交于
      seperate out protocol marshaling into a small 'ws' library in vendor, so that
      AWS itself only does integration with ActionPack, and so we can keep protocol
      specific code in AWS proper to a minimum. refactor unit tests to get 95%
      code coverage (for a baseline).
      
      be far more relaxed about the types given to us by the remote side, don't do
      any poor man's type checking, just try to cast and marshal to the correct types if
      possible, and if not, return what they gave us anyway. this should make interoperating
      with fuzzy XML-RPC clients easier.
      
      if exception reporting is turned on, do best-effort error responses, so that
      we can avoid "Internal protocol error" with no details if there is a bug in
      AWS itself.
      
      also perform extensive cleanups on AWS proper.
      
      
      git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@800 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
      6f5a7b20
  21. 25 2月, 2005 1 次提交
  22. 20 2月, 2005 1 次提交
  23. 19 2月, 2005 3 次提交