On Fri, Aug 22, 2008 at 7:25 AM, srm13 <[EMAIL PROTECTED]> wrote:

>
> Thanks, sticking to WS-Interop seems sensible. However, then the question
> arises how such a service can be consumed? Is there a standard way of
> wrapping them so that they provide data in the right format?
>

Normally any rpc/enc service can be converted to doc/lit by tweaking its
WSDL. You basically need to change the invocation style and provide the
right element types for the operation.

Matthieu


>
> It is not an issue with this Calendar service, as I can rewrite that, but
> this was only a trial to see how I can use the technology to access
> existing
> services which might be RPC encoded.
>
> thanks,
> Stephan
>
>
> Matthieu Riou-5 wrote:
> >
> > On Fri, Aug 22, 2008 at 6:13 AM, srm13 <[EMAIL PROTECTED]> wrote:
> >
> >>
> >> > But, trying to make a very simple service invocation this error is
> >> raised
> >> by Apache ODE :
> >>
> >> > "ERROR - GeronimoLog.error(108) | Unable to process response: SOAP
> body
> >> > does not contain expected
> >> > part wrapper: service {http://services}prefixer port
> prefixerOperations
> >> > wrapper prefixResponse
> >> > org.apache.ode.axis2.OdeFault: SOAP body does not contain expected
> part
> >> > wrapper: service
> >> > {http://services}prefixer port prefixerOperations wrapper
> >> prefixResponse
> >>
> >> I am encountering the same issue with a Calculator service (the service
> >> is
> >> a
> >> .jws file). The service can be invoked directly and returns the expected
> >> value, but when invoked through the process I get the error. Comparing
> >> the
> >> code submitted and mine, I think both services use RPC encoding for
> >> communication.
> >>
> >
> > ODE doesn't support encoding, only doc/lit and rpc/lit are supported. We
> > actually try to stick to WS-BasicProfile (aka WS-Interoperability) that
> > doesn't support encoding either.
> >
> > Matthieu
> >
> >
> >>
> >> I am really stuck here, so a quick answer would be good.
> >>
> >> best Stephan
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Strange-error-%3A-SOAP-body-does-not-contain-expected-part-wrapper%3A-service-tp19024188p19107016.html
> >> Sent from the Apache Ode User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Strange-error-%3A-SOAP-body-does-not-contain-expected-part-wrapper%3A-service-tp19024188p19108330.html
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
>

Reply via email to