Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support of WSDL document literal warpped TYPE #77

Open
lucile-fievet opened this issue Aug 26, 2013 · 2 comments
Open

Support of WSDL document literal warpped TYPE #77

lucile-fievet opened this issue Aug 26, 2013 · 2 comments

Comments

@lucile-fievet
Copy link

Hy,
My application works fine with rpc-literal wsdl type, but I would like to have the document-literal-wrapped.
When I change my config for document-wrapped, I have this message :

The service "besimple.soap.context.demoapi" has a dependency on a non-existent service "besimple.soap.definition.dumper.wsdl.documentwrapped"

Do I have to configure the service somewhere ?
Thanks a lot for the bundle anyway

@lucile-fievet
Copy link
Author

In the SoapBundle/Ressources/config/webservice.xml

I added one parameter (besimple.soap.definition.dumper.wsdl.documentwrapped.class) and one service (besimple.soap.definition.dumper.wsdl.documentwrapped)

<parameters>
...
<parameter key="besimple.soap.definition.dumper.wsdl.documentwrapped.class">BeSimple\SoapBundle\ServiceDefinition\Dumper\WsdlDumper</parameter>

<services>
...
<service id="besimple.soap.definition.dumper.wsdl.documentwrapped" class="%besimple.soap.definition.dumper.wsdl.documentwrapped.class%">
<argument type="service" id="besimple.soap.definition.loader.annot_complextype" />
<argument type="service" id="besimple.soap.type.repository" />
<argument type="collection">
<argument key="stylesheet">%besimple.soap.definition.dumper.options.stylesheet%</argument>
</argument>
</service>``

But I need also the corresponding class so I created :
class DocumentLiteralWrappedRequestMessageBinder extends RpcLiteralRequestMessageBinder implements MessageBinderInterface

It is the same of RpcLiteralRequestMessageBinde, and then my soap service generate a wsdl, but it still looking like the RPC Literal Type and my service doesn't work anymore :) that is quite normal.

I guess the document_literal_wrapped is not yet supported, and started but not finished ... is it on the way ? may I help ? have you some hints to get it rights ?

I suppose we have to extends the header to add the types and adapte the message

<types><schema><element name="myMethode"><complexeType>...<complexeType></element>.... </schema></types> <message>...</message>

and also adapte the binding type ...

Thanks for any help
Best regards

@lucile-fievet
Copy link
Author

The Ressources/ServiceDefinition/Dumper/WsdlDumper.php got the "rpc" hard coded, and if I set another WsdlDumper in Ressources/config/webservice.xml

<parameter key="besimple.soap.definition.dumper.wsdl.documentwrapped.class">BeSimple\SoapBundle\ServiceDefinition\Dumper\DocumentLiteralWsdlDumper</parameter>

It is not taken in account..
Then if I set document instead of rpc, it does'nt work either, the WsdlTypeStrategy goes wrong.

The questions I have are :
How can I set properly the prefix binding used in WsdlDumper.php ?
What am I missing for the WsdlTypeStartegy ?

Thanks for any help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant