Nandika, That did it, thank you! I have a couple of questions:
1. Why is it that some of my operations have a mep attribute (both in and in-out) and others do not? Should I manually add the in-out to all those that don't have a mep attribute? 2. Some customers have reported that the Silverlight client is throwing a communication exception when calling the getSlideImage operation. Does it make sense that the wrong mep namespace would result in this type of thing? The operation always works for me on my development machine, so I have been a bit mystified at why some customers have issues, others don't. Sam On Mon, May 31, 2010 at 1:12 AM, Nandika Jayawardana <[email protected]>wrote: > There are two namespaces for the MEP patterns. > > 1. http://www.w3.org/2004/08/wsdl/in-out [ older one] > 2. http://www.w3.org/ns/wsdl/in-out. [new one ] > > In axis2/c 2004/08 mep uri are used for matching message exchange patterns. > However, in the current svn, both uri's are available. When code generated > with the latest codegen tool, the newer versions of uri's will be used and > hence the operation dispatching would fail. You can either change the > generated services.xml or get the latest svn to fix the issue. > > Regards > Nandika > > > On Mon, May 31, 2010 at 4:23 AM, Sam Carleton > <[email protected]>wrote: > >> One one particular operation , I get this in my Axis2/C logs: >> >> [error] ..\..\src\core\description\op.c(833) Could not map the MEP URI >> http://www.w3.org/ns/wsdl/in-out to an Axis2/C MEP constant value in >> retrieving MEP for operation getSlideImage >> >> What does this mean? How do I fix it? >> >> Sam >> > > > > -- > http://nandikajayawardana.blogspot.com/ > WSO2 Inc: http://www.wso2.com >
