ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert" <boisv...@intalio.com>
Subject Re: Passing SOAP Header Information via ODE
Date Thu, 08 Nov 2007 16:17:35 GMT
Your "wsse" namespace prefix/bindings are inconsistent between your WSDL and
your BPEL.

alex


On 11/8/07, Dmitry Vasilenko <dvasilen@spss.com> wrote:
>
>
> Yes, please see attached HelloWord_FromBPELHelper.zip (the CR.wsdl file)
>
> Here is the SOAP send to the CR:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
> ">
>        <soapenv:Header>
>              <addr:To
> xmlns:addr="http://www.w3.org/2005/08/addressing">
> http://localhost:8080/cr-ws/services/ContentRepository</addr:To>
>              <addr:Action
> xmlns:addr="http://www.w3.org/2005/08/addressing"/>
>              <addr:ReplyTo
> xmlns:addr="http://www.w3.org/2005/08/addressing">
>
> <addr:Address>http://www.w3.org/2005/08/addressing/anonymous
> </addr:Address>
>              </addr:ReplyTo>
>              <addr:MessageID
> xmlns:addr="http://www.w3.org/2005/08/addressing
> ">uuid:hqejbhcnphr2q8nqhv3ift</addr:MessageID>
>        </soapenv:Header>
>        <soapenv:Body>
>              <axis2ns1:getVersion
> xmlns:axis2ns1="http://xml.spss.com/repository/remote">123.0
> </axis2ns1:getVersion>
>        </soapenv:Body>
> </soapenv:Envelope>
>
> The "header2" specified as the part of the WSDL message is missing ... ;-[
>
>
>
>
>
>
>
> Alex Boisvert wrote:
> >
> > Did you add soap:header bindings in your WSDL?
> >
> > e.g.
> >     <binding name="SessionCreateSoapBinding"
> > type="tns:SessionCreatePortType">
> >         <soap:binding style="document" transport="
> > http://schemas.xmlsoap.org/soap/http"/>
> >         <operation name="SessionCreateRQ">
> >             <soap:operation soapAction="OTA"/>
> >             <input>
> >                 <soap:header message="tns:GetSessionCreateInput"
> > part="header" use="literal"/>
> >                 <soap:header message="tns:GetSessionCreateInput"
> > part="header2" use="literal"/>
> >                 <soap:body parts="body" use="literal"/>
> >             </input>
> >             <output>
> >                 <soap:header message="tns:GetSessionCreateOutput"
> > part="header" use="literal"/>
> >                 <soap:header message="tns:GetSessionCreateOutput"
> > part="header2" use="literal"/>
> >                 <soap:body parts="body" use="literal"/>
> >             </output>
> >         </operation>
> >     </binding>
> >
> > alex
> >
> > On 11/8/07, Dmitry Vasilenko <dvasilen@spss.com> wrote:
> >>
> >>
> >> Could anyone provide some (any) samples of using
> >> "urn:ode.apache.org/axis2-il/headers/"
> >> extension in BPEL assign/invoke to pass SOAP headers to the endpoint?
> >>
> >> We are trying to use the approach similar to the one described by
> Vishal
> >> Bhasin
> >> (see zip file attached to the his message "Passing SOAP Header
> >> Information
> >> via
> >> ODE  - Vishal Bhasin Jun 10, 2007; 07:23pm ") but it does not work.
> >>
> >> The headers are ignored. Only the body part is sent.
> >>
> >> We are currently looking at that "urn:ode.apache.org/axis2-il/headers/"
> >> extension
> >> but not sure how to use it and cannot find any samples.
> >>
> >>
> >> Alex Boisvert wrote:
> >> >
> >> > Oh, I forgot you were using JBI...  I am not sure anymore about the
> >> SOAP
> >> > header mappings.  I haven't looked at this in a while...  The
> question
> >> is
> >> > really about how/where ServiceMix places the SOAP headers in the
> >> > normalized
> >> > message.  At the Ode level, we can use the MessageMappers to do the
> >> right
> >> > thing.
> >> >
> >> > BTW, we have introduced an extension to assign:
> >> >
> >> > <to variable="BPELVariableName" extension="QName" />
> >> >
> >> > so it's no longer necessary to declare them in the WSDL.  See
> >> > http://incubator.apache.org/ode/assign.html for details.
> >> >
> >> > alex
> >> >
> >> >
> >> > On 6/11/07, Vishal Bhasin <vbhasin@yahoo.com> wrote:
> >> >>
> >> >> Alex,
> >> >>
> >> >> Thanks for reviewing these!
> >> >>
> >> >> While routing the message from JMS - SU (in ServiceMix) to ODE-SU,
I
> >> see
> >> >> that SOAP header information is stripped, how can I pass along the
> >> header
> >> >> information as well?
> >> >>
> >> >> Thanks,
> >> >>
> >> >> Vishal
> >> >>
> >> >> Alex Boisvert <boisvert@intalio.com> wrote: Yep, looks good.
> >> >>
> >> >> alex
> >> >>
> >> >>
> >> >> On 6/10/07, Vishal Bhasin  wrote:
> >> >> >
> >> >> > I'm attaching one of our WSDLs with all XSDs referenced. I'd
> >> appreciate
> >> >> if
> >> >> > you could please review and let me know if I can use these to
pass
> >> the
> >> >> SOAP
> >> >> > header information to my external web service.
> >> >> >
> >> >> > Thanks,
> >> >> >
> >> >> > Vishal
> >> >> >
> >> >> >
> >> >> > Regards,
> >> >> >
> >> >> > Vishal
> >> >> >
> >> >> > "I want to improve the system, not fight it"
> >> >> >
> >> >> > ------------------------------
> >> >> > Building a website is a piece of cake.
> >> >> > Yahoo! Small Business gives you all the tools to get online.
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >> Regards,
> >> >>
> >> >> Vishal
> >> >>
> >> >> "I want to improve the system, not fight it"
> >> >>
> >> >>
> >> >>
> >> >> ---------------------------------
> >> >> Park yourself in front of a world of choices in alternative
> vehicles.
> >> >> Visit the Yahoo! Auto Green Center.
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Process-end-point-tf3891955.html#a13647571
> >> Sent from the Apache Ode User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> http://www.nabble.com/file/p13649882/HelloWord_FromBPELHelper.zip
> HelloWord_FromBPELHelper.zip
> http://www.nabble.com/file/p13649882/HelloWord_FromBPELHelper.zip
> HelloWord_FromBPELHelper.zip
> --
> View this message in context:
> http://www.nabble.com/Process-end-point-tf3891955.html#a13649882
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message