Yep, sorry... didn't realize it was the developers list. Thanks for
forwarding my question to the proper list.


On Feb 5, 12:38 pm, "[MA]Pascal" <[email protected]> wrote:
> Javi,
>
> Please ask these kind of question on the symfony-users mailing list
> (http://groups.google.com/group/symfony-users).
>
> This list is for the development of the symfony framework itself
> rather than
> general questions about using symfony.
>
> Regards,
> [MA]Pascal
>
> On Feb 5, 11:26 am, "[email protected]" <[email protected]> wrote:
>
> > Hi there! I just posted this in the forums, but I send it here too
> > wondering if this group is faster. If it's considered "spam" to post
> > in both places please accept my apologies.
>
> > I'm trying to integrate wso wsf php 2.0 (http://wso2.org/projects/wsf/
> > php) in symfony 1.1.1, mainly because I need to send/receive binary
> > attachments in my soap webservices (SOAP-MTOM).
>
> > It looks like everything is correct, but I can't get any response,
> > soapfault or similar from my services. This is what I did:
>
> > - compile and install the wso wsf extension, and configure php to use
> > it (in php.ini).
>
> > - put the php scripts that come with the wso wsf package in my php's
> > include_path.
>
> > - create a symfony project, an app, and a module to test a soap server
> > using the extension.
>
> > - put an include for the file "wso-wsf-include.php" in the app
> > controller.
>
> > then, my actions class looks like this:
>
> > class authActions extends sfActions
> > {
> >    /**
> >     * Index action
> >     * @param sfRequest $poRequest
> >     */
> >    public function executeIndex ( $poRequest )
> >    {
> >       $oService = new WSService(
> >          array (
> >             "serviceName" => "MyServices",
> >             "classes" => array (
> >                "authActions" => array (
> >                   "operations" => array (
> >                      "sayHi" => "executeSayHi"
> >                   )
> >                )
> >             )
> >          )
> >       );
>
> >       return $this->renderText($oService->reply());
> >    }
>
> >    /**
> >     * @param string $psTestParam
> >     * @return string
> >     */
> >    public function executeSayHi ( $psTestParam )
> >    {
> >       return $this->renderText("whatever..." . $psTestParam);
> >    }
>
> > }
>
> > Until here everything ok... Pointing a web browser to the index action
> > "http://localhost/gdServices.php/auth/index"; I can see a page telling
> > me that the "sayHi" operation is available, and if I try "http://
> > localhost/gdServices.php/auth/index?wsdl" I can see the wsdl generated
> > file that takes properly the type of parameter and return type of my
> > operation method (it reads well the method's php-doc comments).
>
> > Now the problem is that no any client gets anything from the service,
> > I mean no any response or even any exception or soap fault. Here's a
> > very simple php client I'm trying:
>
> > <?php
>
> > error_reporting(E_ALL | E_STRICT);
>
> > try
> > {
> >    $oClient = new SoapClient ("http://localhost/gdServices.php/auth/
> > index?wsdl", array("trace" => true));
>
> >    $sHi = $oClient->sayHi("test");
>
> >    // the following returns null!
> >    // die(var_dump( $oClient->__getLastResponse() ));
>
> >    // the following also returns null!
> >    var_dump($sHi);
>
> > }
>
> > catch (SoapFault $oFault)
> > {
> >    // and SoapFault is never triggered... I never really get into this
> > 'catch' section
> >    trigger_error("SOAP Fault!! : " . $oFault->faultstring),
> > E_USER_ERROR);
>
> > }
>
> > Did anybody succesfully integrate this in symfony? Any clues?
> > Thanks a lot in advance!
> > Regards,
>
> > Javi Ruiz
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to