You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by "Ciot, Thierry" <th...@compuware.com> on 2007/06/08 22:23:34 UTC
Process end point
Now that I have my first process deployed, I'm trying to figure out the
end point to access it.
It turns out if I log under axis2 management console under ODE
(http://localhost:8180/ode/axis2-admin/listService) I can see my
deployed service listed and its EPR is
http://localhost:8180/ode/services/LoanRequest. However, my wsdl file
is specifying a different end point (modeled after helloworld2) of
http://localhost:8180/ode/processes/LoanRequest. That end point exists
and is active.
So here are my questions:
1) They seem to be both real end point for the process. What's the
difference between each one?
2) Which end point is the real process end point?
3) Do we have any choice in where the end point is or does it have to
be under /ode/processes/?
Thanks, Thierry.
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
Re: Passing SOAP Header Information via ODE
Posted by Dmitry Vasilenko <dv...@spss.com>.
Here is the file ...
Dmitry Vasilenko 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 <dv...@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 <vb...@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 <bo...@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
>
http://www.nabble.com/file/p13649991/HelloWord_FromBPELHelper.zip
HelloWord_FromBPELHelper.zip
--
View this message in context: http://www.nabble.com/Process-end-point-tf3891955.html#a13649991
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: Passing SOAP Header Information via ODE
Posted by Dmitry Vasilenko <dv...@spss.com>.
Thank you very much Alex,
That was exactly the problem! When I added the namespace prefix to the
getVersionRequest
<wsdlsoap:header message="impl:getVersionRequest" part="header2"
use="literal"/>
everything started working as expected.
Best Regards,
Dmitry
Alex Boisvert wrote:
>
> Hmmm. I'm not too sure about this one. Maybe WSDL4J is playing tricks
> on
> us.
>
> Can you try using a qname for the message reference in the header mapping?
> e.g. Changing this,
>
> <wsdlsoap:header message="getVersionRequest" part="header2"
> use="literal"/>
>
> to
>
> <wsdlsoap:header message="intf:getVersionRequest" part="header2"
> use="literal"/>
>
> If that doesn't work, please file a bug.
>
> thanks,
> alex
>
>
> On 11/8/07, Dmitry Vasilenko <dv...@spss.com> wrote:
>>
>>
>> Thanks Alex,
>>
>> I have updated WS-Security namespace prefix/bindings to use "wsse" and
>> "
>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
>> "
>> consistently (see attached) but it still does not work.
>>
>> The SOAP message sent to the endpoint still missing the header... ;-[
>>
>> <?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:hqejbhcnphr2q9cwji6lri</addr:MessageID>
>> </soapenv:Header>
>> <soapenv:Body>
>> <axis2ns4:getVersion
>> xmlns:axis2ns4="http://xml.spss.com/repository/remote">123.0
>> </axis2ns4:getVersion>
>> </soapenv:Body>
>> </soapenv:Envelope>
>>
>> Thanks a lot for your help,
>> Dmitry
>>
>> http://www.nabble.com/file/p13651098/HelloWord_FromBPELHelper.zip
>> HelloWord_FromBPELHelper.zip
>> --
>> View this message in context:
>> http://www.nabble.com/Process-end-point-tf3891955.html#a13651098
>> Sent from the Apache Ode User mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Process-end-point-tf3891955.html#a13655698
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: Passing SOAP Header Information via ODE
Posted by Alex Boisvert <bo...@intalio.com>.
Hmmm. I'm not too sure about this one. Maybe WSDL4J is playing tricks on
us.
Can you try using a qname for the message reference in the header mapping?
e.g. Changing this,
<wsdlsoap:header message="getVersionRequest" part="header2"
use="literal"/>
to
<wsdlsoap:header message="intf:getVersionRequest" part="header2"
use="literal"/>
If that doesn't work, please file a bug.
thanks,
alex
On 11/8/07, Dmitry Vasilenko <dv...@spss.com> wrote:
>
>
> Thanks Alex,
>
> I have updated WS-Security namespace prefix/bindings to use "wsse" and
> "
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> "
> consistently (see attached) but it still does not work.
>
> The SOAP message sent to the endpoint still missing the header... ;-[
>
> <?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:hqejbhcnphr2q9cwji6lri</addr:MessageID>
> </soapenv:Header>
> <soapenv:Body>
> <axis2ns4:getVersion
> xmlns:axis2ns4="http://xml.spss.com/repository/remote">123.0
> </axis2ns4:getVersion>
> </soapenv:Body>
> </soapenv:Envelope>
>
> Thanks a lot for your help,
> Dmitry
>
> http://www.nabble.com/file/p13651098/HelloWord_FromBPELHelper.zip
> HelloWord_FromBPELHelper.zip
> --
> View this message in context:
> http://www.nabble.com/Process-end-point-tf3891955.html#a13651098
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
>
Re: Passing SOAP Header Information via ODE
Posted by Dmitry Vasilenko <dv...@spss.com>.
Thanks Alex,
I have updated WS-Security namespace prefix/bindings to use "wsse" and
"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
consistently (see attached) but it still does not work.
The SOAP message sent to the endpoint still missing the header... ;-[
<?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:hqejbhcnphr2q9cwji6lri</addr:MessageID>
</soapenv:Header>
<soapenv:Body>
<axis2ns4:getVersion
xmlns:axis2ns4="http://xml.spss.com/repository/remote">123.0</axis2ns4:getVersion>
</soapenv:Body>
</soapenv:Envelope>
Thanks a lot for your help,
Dmitry
http://www.nabble.com/file/p13651098/HelloWord_FromBPELHelper.zip
HelloWord_FromBPELHelper.zip
--
View this message in context: http://www.nabble.com/Process-end-point-tf3891955.html#a13651098
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: Passing SOAP Header Information via ODE
Posted by Alex Boisvert <bo...@intalio.com>.
Your "wsse" namespace prefix/bindings are inconsistent between your WSDL and
your BPEL.
alex
On 11/8/07, Dmitry Vasilenko <dv...@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 <dv...@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 <vb...@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 <bo...@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.
>
>
Re: Passing SOAP Header Information via ODE
Posted by Dmitry Vasilenko <dv...@spss.com>.
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 <dv...@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 <vb...@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 <bo...@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.
Re: Passing SOAP Header Information via ODE
Posted by Alex Boisvert <bo...@intalio.com>.
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 <dv...@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 <vb...@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 <bo...@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.
>
>
Re: Passing SOAP Header Information via ODE
Posted by Dmitry Vasilenko <dv...@spss.com>.
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 <vb...@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 <bo...@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.
Re: Passing SOAP Header Information via ODE
Posted by Alex Boisvert <bo...@intalio.com>.
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 <vb...@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 <bo...@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.
Re: Passing SOAP Header Information via ODE
Posted by Vishal Bhasin <vb...@yahoo.com>.
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 <bo...@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.
Re: Passing SOAP Header Information via ODE
Posted by Alex Boisvert <bo...@intalio.com>.
Yep, looks good.
alex
On 6/10/07, Vishal Bhasin <vb...@yahoo.com> 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.<http://us.rd.yahoo.com/evt=48251/*http://smallbusiness.yahoo.com/webhosting/?p=PASSPORTPLUS>
>
>
>
Passing SOAP Header Information via ODE
Posted by Vishal Bhasin <vb...@yahoo.com>.
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.
Re: Process end point
Posted by Matthieu Riou <ma...@gmail.com>.
Hi Thierry,
See my answers in line.
1) They seem to be both real end point for the process. What's the
> difference between each one?
The services one won't work, the processes one will. This is an issue we
have with Axis2 as all the deployed services are listed as being under the
services path. However ours are under processes specifically to distinguish
them.
2) Which end point is the real process end point?
http://localhost:8180/ode/processes/LoanRequest
3) Do we have any choice in where the end point is or does it have to
> be under /ode/processes/?
It has to be something under processes. The webapp name can be anything you
want and you can put anything you want after the processes section. (like
/ode/processes/foo/bar).
Cheers,
Matthieu
Thanks, Thierry.
>
>
> The contents of this e-mail are intended for the named addressee only. It
> contains information that may be confidential. Unless you are the named
> addressee or an authorized designee, you may not copy or use it, or disclose
> it to anyone else. If you received it in error please notify us immediately
> and then destroy it.
>
> The contents of this e-mail are intended for the named addressee only. It
> contains information that may be confidential. Unless you are the named
> addressee or an authorized designee, you may not copy or use it, or disclose
> it to anyone else. If you received it in error please notify us immediately
> and then destroy it.
>