Thanks Gert, that fixed it. I am not a contributor yet, can someone
make the change?
File affected:
<ServiceMix>\samples\wsdl-first\wsdl-first-http-su\src\main\resources\xbean.xml
See Attached diff file.
Regards,
Gordon Dickens
Gert Vanthienen wrote:
Gordon,
Can you try to rebuilding the service after adding
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
to your HTTP consumer endpoint configuration?
Gert
Adrian Co wrote:
I haven't tried the example, but AFAIK, this is cause by an
unspecified MEP in one of the configs. (i.e. one of the binding
components probably didn't specified the defaultMep to use). But I'm
just taking a guess. :)
Gordon Dickens wrote:
Hello,
This has probably been discussed before but, when I try to test the
WSDL-First example using the provided client.html file. The soap
response is "Do not understand pattern: null".
I tried rebuilding the service and redeploying and no change.
What do I need to do to correct this?
Thanks,
Gordon Dickens
Index: xbean.xml
===================================================================
--- xbean.xml (revision 561891)
+++ xbean.xml (working copy)
@@ -23,8 +23,9 @@
<http:endpoint service="person:PersonService"
endpoint="soap"
targetService="person:PersonService"
- role="consumer"
+ role="consumer"
locationURI="http://0.0.0.0:8192/PersonService/";
+ defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
soap="true" />
</beans>
