Zend Framework

SOAP Support

Details

Description

Support both producing and consuming a SOAP service.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Wil Sinclair added a comment -

Resetting 'fix version priority' and 'fix version' to be re-evaluated for next release.

Show
Wil Sinclair added a comment - Resetting 'fix version priority' and 'fix version' to be re-evaluated for next release.
Hide
Permalink
Helgi Hrafn Halldórsson added a comment -

I would love to participate in this task if that is possible. I have been looking a bit into this, here at my company we are about to create web services and have come to conclusion to use SOAP. I have already started creating a controller named Foo_Controller_Action_Soap_Server which would be extended by the actual controller (eg. within a module). The idea is to create a controller that has a SoapServer (or Zend_Soap_Server) to handle requests, and then have actions that would be something like these;

  1. indexAction - http://example.com/module/controller/ - If a POST request the server will handle it, otherwise forward to funcsAction.
  2. wsdlAction - http://example.com/module/controller/wsdl - Construct and display the WSDL file
  3. funcsAction - http://example.com/module/controller/funcs - List available function list with arguments and types
  4. viewAction - http://example.com/module/controller/view/function/someFunction - View a selected function with more detailed information from the docblock

This was at least the idea, and with Zend_Soap_Server and the WSDL Generation this will be allot easier.

Show
Helgi Hrafn Halldórsson added a comment - I would love to participate in this task if that is possible. I have been looking a bit into this, here at my company we are about to create web services and have come to conclusion to use SOAP. I have already started creating a controller named Foo_Controller_Action_Soap_Server which would be extended by the actual controller (eg. within a module). The idea is to create a controller that has a SoapServer (or Zend_Soap_Server) to handle requests, and then have actions that would be something like these;
  1. indexAction - http://example.com/module/controller/ - If a POST request the server will handle it, otherwise forward to funcsAction.
  2. wsdlAction - http://example.com/module/controller/wsdl - Construct and display the WSDL file
  3. funcsAction - http://example.com/module/controller/funcs - List available function list with arguments and types
  4. viewAction - http://example.com/module/controller/view/function/someFunction - View a selected function with more detailed information from the docblock
This was at least the idea, and with Zend_Soap_Server and the WSDL Generation this will be allot easier.
Hide
Permalink
Alexander Veremyev added a comment -

Hi Helgi!

You are really welcome! Do not hesitate to take SOAP tasks you prefer.

PS Take a look into incubator to check tasks are already done.

Show
Alexander Veremyev added a comment - Hi Helgi! You are really welcome! Do not hesitate to take SOAP tasks you prefer. PS Take a look into incubator to check tasks are already done.
Hide
Permalink
Sébastien Cramatte added a comment -

Where can I download somes examples ?
Might be I can give an hand...

Show
Sébastien Cramatte added a comment - Where can I download somes examples ? Might be I can give an hand...
Hide
Permalink
Alexander Veremyev added a comment -

ZF-3273 SOAP access to controllers subtask is converted to separate issue. So this issue becomes resolved.

Show
Alexander Veremyev added a comment - ZF-3273 SOAP access to controllers subtask is converted to separate issue. So this issue becomes resolved.

People

Vote (3)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Zend Framework. Try JIRA - bug tracking software for your team.