ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jbi joe <...@daggerpoint.net>
Subject WSDL Woes and no mapper
Date Wed, 18 Jul 2007 10:57:24 GMT

I edited/compiled the ode-jbi jar to track down my error:
"Could not find a mapper for request message for JBI MEX...."
Inside of the ServiceMixMapper.isRecognized I found that the ode-jbi
validates my Normalized Message and the WSDL.    My wsdl, snippet below,
verified and I can see the method finds the "operation" =myOperation, then
sees the
"partname" =myPart and that seems to be all it can find.   IT dies shortly
trying to find another part, pdata I think...  I see the code
returns a null, so it does not go any further, subsequently generating the
WHY, how do I fix it?   Netbeans  5.5 says my WSDL is valid.   SHould there
something else in the WSDL the contains somethig for the part.getElement()
find?    Any help greatly appreciated..

WSDL snippet
<wsdl:message name="myMessage">
    <wsdl:part name="myPart" type="xs:myBundle" />

<wsdl:portType name="myPortType">
    <wsdl:operation name="myOperation">
        <wsdl:input message="tns:myMessage" />
View this message in context: http://www.nabble.com/WSDL-Woes-and-no-mapper-tf4102552.html#a11666530
Sent from the Apache Ode User mailing list archive at Nabble.com.

View raw message