You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by Simon Sekat <se...@gmail.com> on 2007/07/23 23:01:25 UTC
how to generate the deploy.xml and WSDL files in my BPEL service unit
In my BPEL service unit, there is the main BPEL, deploy.xml and several WSDL
files. I want to find out how to produce deploy.xml and my WSDL files
efficiently (generate them?). Thank you.
If you don't understand what I meant by my WSDL files, read the rest of this
email. My WSDL files differ from the original WSDL files that I download
from the web server (e.g. http://localhost:8192/PersonService/main.wsdl) in
the following aspects:
1. my WSDL files do not have <binding> and <service> tag. The original WSDL
files do, as shown below.
- <#> <wsdl:binding name="*soapBinding*" type="*tns:Person*">
<wsdlsoap:binding style="*document*" transport="*
http://schemas.xmlsoap.org/soap/http*" />
- <#> <wsdl:operation name="*GetPerson*">
<wsdlsoap:operation soapAction="" />
- <#> <wsdl:input>
<wsdlsoap:body use="*literal*" />
</wsdl:input>
- <#> <wsdl:output>
<wsdlsoap:body use="*literal*" />
</wsdl:output>
- <#> <wsdl:fault name="*UnknownPerson*">
<wsdlsoap:fault name="*UnknownPerson*" use="*literal*" />
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
- <#> <wsdl:service name="*PersonService*">
- <#> <wsdl:port binding="*tns:soapBinding*" name="*soap*">
<wsdlsoap:address location="*http://0.0.0.0:8192/PersonService/*" />
</wsdl:port>
</wsdl:service>
2. My WSDL files have <partnerLinkType> additionally, as shown below.
<plnk:partnerLinkType name="Person1LinkType">
<plnk:role name="Provider" portType="tns:Person"/>
</plnk:partnerLinkType>
--
Simon S.
Re: how to generate the deploy.xml and WSDL files in my BPEL service unit
Posted by Alex Boisvert <bo...@intalio.com>.
At this time, I know of only the Intalio|BPMS Designer that generates
deploy.xml together with BPEL.
I would need to take a look at the Eclipse BPEL Designer to see how to
extend it to generate deploy.xml ...
alex
On 7/30/07, Simon Sekat <se...@gmail.com> wrote:
>
> Alex,
>
> You just gave me a clue on dealing with the WSDL. Now I understand there
> might not be a way to generate them. Thank you.
>
> But how would you create the deploy.xml in your applications? Are they
> hand
> written, developed by using some editors?
>
> On 7/30/07, Alex Boisvert <bo...@intalio.com> wrote:
> >
> > Hi Simon,
> >
> > I'm not sure I understand the problem you're trying to solve... however,
> I
> > can suggest:
> >
> > 1) Using XSLT during packaging to easily remove your <binding> and
> > <service>
> > sections
> > 2) Placing your partnerLinks in a separate WSDL document and import your
> > original (or modified from #1) WSDL
> >
> > But I'm still not sure if that's what you're after.
> >
> > alex
> >
> >
> > On 7/23/07, Simon Sekat <se...@gmail.com> wrote:
> > >
> > > In my BPEL service unit, there is the main BPEL, deploy.xml and
> several
> > > WSDL
> > > files. I want to find out how to produce deploy.xml and my WSDL files
> > > efficiently (generate them?). Thank you.
> > >
> > > If you don't understand what I meant by my WSDL files, read the rest
> of
> > > this
> > > email. My WSDL files differ from the original WSDL files that I
> download
> > > from the web server (e.g.
> http://localhost:8192/PersonService/main.wsdl)
> > > in
> > > the following aspects:
> > >
> > > 1. my WSDL files do not have <binding> and <service> tag. The
> original
> > > WSDL
> > > files do, as shown below.
> > >
> > > - <#> <wsdl:binding name="*soapBinding*" type="*tns:Person*">
> > > <wsdlsoap:binding style="*document*" transport="*
> > > http://schemas.xmlsoap.org/soap/http*" />
> > > - <#> <wsdl:operation name="*GetPerson*">
> > > <wsdlsoap:operation soapAction="" />
> > > - <#> <wsdl:input>
> > > <wsdlsoap:body use="*literal*" />
> > > </wsdl:input>
> > > - <#> <wsdl:output>
> > > <wsdlsoap:body use="*literal*" />
> > > </wsdl:output>
> > > - <#> <wsdl:fault name="*UnknownPerson*">
> > > <wsdlsoap:fault name="*UnknownPerson*" use="*literal*" />
> > > </wsdl:fault>
> > > </wsdl:operation>
> > > </wsdl:binding>
> > > - <#> <wsdl:service name="*PersonService*">
> > > - <#> <wsdl:port binding="*tns:soapBinding*" name="*soap*">
> > > <wsdlsoap:address location="*http://0.0.0.0:8192/PersonService/*"
> />
> > > </wsdl:port>
> > > </wsdl:service>
> > >
> > > 2. My WSDL files have <partnerLinkType> additionally, as shown below.
> > >
> > > <plnk:partnerLinkType name="Person1LinkType">
> > > <plnk:role name="Provider" portType="tns:Person"/>
> > > </plnk:partnerLinkType>
> > >
> > >
> > > --
> > >
> > > Simon S.
> > >
> >
>
>
>
> --
>
> Simon S.
>
Re: how to generate the deploy.xml and WSDL files in my BPEL service unit
Posted by Simon Sekat <se...@gmail.com>.
Alex,
You just gave me a clue on dealing with the WSDL. Now I understand there
might not be a way to generate them. Thank you.
But how would you create the deploy.xml in your applications? Are they hand
written, developed by using some editors?
On 7/30/07, Alex Boisvert <bo...@intalio.com> wrote:
>
> Hi Simon,
>
> I'm not sure I understand the problem you're trying to solve... however, I
> can suggest:
>
> 1) Using XSLT during packaging to easily remove your <binding> and
> <service>
> sections
> 2) Placing your partnerLinks in a separate WSDL document and import your
> original (or modified from #1) WSDL
>
> But I'm still not sure if that's what you're after.
>
> alex
>
>
> On 7/23/07, Simon Sekat <se...@gmail.com> wrote:
> >
> > In my BPEL service unit, there is the main BPEL, deploy.xml and several
> > WSDL
> > files. I want to find out how to produce deploy.xml and my WSDL files
> > efficiently (generate them?). Thank you.
> >
> > If you don't understand what I meant by my WSDL files, read the rest of
> > this
> > email. My WSDL files differ from the original WSDL files that I download
> > from the web server (e.g. http://localhost:8192/PersonService/main.wsdl)
> > in
> > the following aspects:
> >
> > 1. my WSDL files do not have <binding> and <service> tag. The original
> > WSDL
> > files do, as shown below.
> >
> > - <#> <wsdl:binding name="*soapBinding*" type="*tns:Person*">
> > <wsdlsoap:binding style="*document*" transport="*
> > http://schemas.xmlsoap.org/soap/http*" />
> > - <#> <wsdl:operation name="*GetPerson*">
> > <wsdlsoap:operation soapAction="" />
> > - <#> <wsdl:input>
> > <wsdlsoap:body use="*literal*" />
> > </wsdl:input>
> > - <#> <wsdl:output>
> > <wsdlsoap:body use="*literal*" />
> > </wsdl:output>
> > - <#> <wsdl:fault name="*UnknownPerson*">
> > <wsdlsoap:fault name="*UnknownPerson*" use="*literal*" />
> > </wsdl:fault>
> > </wsdl:operation>
> > </wsdl:binding>
> > - <#> <wsdl:service name="*PersonService*">
> > - <#> <wsdl:port binding="*tns:soapBinding*" name="*soap*">
> > <wsdlsoap:address location="*http://0.0.0.0:8192/PersonService/*" />
> > </wsdl:port>
> > </wsdl:service>
> >
> > 2. My WSDL files have <partnerLinkType> additionally, as shown below.
> >
> > <plnk:partnerLinkType name="Person1LinkType">
> > <plnk:role name="Provider" portType="tns:Person"/>
> > </plnk:partnerLinkType>
> >
> >
> > --
> >
> > Simon S.
> >
>
--
Simon S.
Re: how to generate the deploy.xml and WSDL files in my BPEL service unit
Posted by Alex Boisvert <bo...@intalio.com>.
Hi Simon,
I'm not sure I understand the problem you're trying to solve... however, I
can suggest:
1) Using XSLT during packaging to easily remove your <binding> and <service>
sections
2) Placing your partnerLinks in a separate WSDL document and import your
original (or modified from #1) WSDL
But I'm still not sure if that's what you're after.
alex
On 7/23/07, Simon Sekat <se...@gmail.com> wrote:
>
> In my BPEL service unit, there is the main BPEL, deploy.xml and several
> WSDL
> files. I want to find out how to produce deploy.xml and my WSDL files
> efficiently (generate them?). Thank you.
>
> If you don't understand what I meant by my WSDL files, read the rest of
> this
> email. My WSDL files differ from the original WSDL files that I download
> from the web server (e.g. http://localhost:8192/PersonService/main.wsdl)
> in
> the following aspects:
>
> 1. my WSDL files do not have <binding> and <service> tag. The original
> WSDL
> files do, as shown below.
>
> - <#> <wsdl:binding name="*soapBinding*" type="*tns:Person*">
> <wsdlsoap:binding style="*document*" transport="*
> http://schemas.xmlsoap.org/soap/http*" />
> - <#> <wsdl:operation name="*GetPerson*">
> <wsdlsoap:operation soapAction="" />
> - <#> <wsdl:input>
> <wsdlsoap:body use="*literal*" />
> </wsdl:input>
> - <#> <wsdl:output>
> <wsdlsoap:body use="*literal*" />
> </wsdl:output>
> - <#> <wsdl:fault name="*UnknownPerson*">
> <wsdlsoap:fault name="*UnknownPerson*" use="*literal*" />
> </wsdl:fault>
> </wsdl:operation>
> </wsdl:binding>
> - <#> <wsdl:service name="*PersonService*">
> - <#> <wsdl:port binding="*tns:soapBinding*" name="*soap*">
> <wsdlsoap:address location="*http://0.0.0.0:8192/PersonService/*" />
> </wsdl:port>
> </wsdl:service>
>
> 2. My WSDL files have <partnerLinkType> additionally, as shown below.
>
> <plnk:partnerLinkType name="Person1LinkType">
> <plnk:role name="Provider" portType="tns:Person"/>
> </plnk:partnerLinkType>
>
>
> --
>
> Simon S.
>