Re: Error deployment BPEL- UndeclaredPartnerLink

[Druid <de...@gmail.com>]

Hi
  There is still another problem，I think I have defined the service but it
is not find
  I find it difficult to solve the problem by myself,and the reference
material is not enough for me,is there any suggestion?

2008/9/23 Matthieu Riou <ma...@offthelip.org>

> On Tue, Sep 23, 2008 at 3:30 AM, Druid <de...@gmail.com> wrote:
>
> >
> > with your help,I have solved the problem,but I met  a new one.
> > I konw there is something wrong with the confirmationData,but I don't
> know
> > what is the reason.
> > http://www.nabble.com/file/p19624961/HelloWorld2-RPC-sa.zip
> > HelloWorld2-RPC-sa.zip
> > http://www.nabble.com/file/p19624961/error.txt error.txt
> >
>
> In HelloWorldAsynchronism.bpel you have the following assignment:
>
>      <assign>
>        <copy>
>          <from>
>            <confirmationData xmlns="urn:/HelloWorldAsynchronism.wsdl">
>                <ha:HelloName>1111</ha:HelloName>
>            </confirmationData>
>          </from>
>          <to variable="HelloResponseAA" part="confirmationData" />
>        </copy>
>      </assign>
>
> In BPEL when you want to assign a literal XML snippet you have to surround
> it with a <literal> element:
>
>      <assign>
>        <copy>
>          <from>
>            <literal>
>              <confirmationData xmlns="urn:/HelloWorldAsynchronism.wsdl">
>                <ha:HelloName>1111</ha:HelloName>
>              </confirmationData>
>            </literal>
>          </from>
>          <to variable="HelloResponseAA" part="confirmationData" />
>        </copy>
>      </assign>
>
> Matthieu
>
>
> >
> >
> > Matthieu Riou-5 wrote:
> > >
> > > On Sun, Sep 21, 2008 at 10:58 PM, Druid <de...@gmail.com> wrote:
> > >
> > >>
> > >> I have met the same problem ,and I changed the namingspace as you
> > >> said,but
> > >> it
> > >> doesn't work.
> > >> what else should I have to change?
> > >
> > >
> > > In BPEL 2.0 the portType reference in a partner link type is an
> > attribute,
> > > not a sub-element. So your partner link type should look like:
> > >
> > > <plnk:partnerLinkType name="HelloLT">
> > >   <plnk:role name="helloService" portType="tns:HelloAvailabilityPT"/>
> > >   <plnk:role name="helloCustomer" portType="tns:HelloCallbackPT"/>
> > > </plnk:partnerLinkType>
> > >
> > > Matthieu
> > >
> > >
> > >> http://www.nabble.com/file/p19602295/HelloWorld2-RPC-sa.zip
> > >> HelloWorld2-RPC-sa.zip
> > >> http://www.nabble.com/file/p19602295/error.txt error.txt
> > >>
> > >>
> > >> atp wrote:
> > >> >
> > >> >
> > >> >
> > >> > atp wrote:
> > >> >>
> > >> >> Hi,
> > >> >>
> > >> >> I've read this thread, but, unfortunately, it does'nt answer to my
> > >> >> problem which is very similar to which of tmf.
> > >> >>
> > >> >> [ ... ]
> > >> >>
> > >> >>
> > >> >
> > >> > I've just now partially solve the problem.
> > >> > It appears that the WSDL editor and the BPEL wizzard don't ude the
> > same
> > >> > namespace for  partner link types.
> > >> >
> > >> > The wsdl editor uses
> > >> http://schemas.xmlsoap.org/ws/2004/03/partner-link/
> > >> ,
> > >> > while the BPEL wizzard use
> > >> http://docs.oasis-open.org/wsbpel/2.0/plnktype
> > >> >
> > >> > So, the ValidationProcess.wsdl file contained a mix of both, and the
> > >> ODE
> > >> > compiler seems have a preference for the first one.
> > >> >
> > >> > For now, the problem is over, and I'll have to deal with a lot of
> new
> > >> ones
> > >> > :-)
> > >> >
> > >> > Regards,
> > >> >
> > >> > Ph.
> > >> >
> > >> > --
> > >> >
> > >>
> > >> --
> > >> View this message in context:
> > >>
> >
> http://www.nabble.com/Error-deployment-BPEL--UndeclaredPartnerLink-tp15884549p19602295.html
> > >> Sent from the Apache Ode User mailing list archive at Nabble.com.
> > >>
> > >>
> > >
> > >
> >
> > --
> > View this message in context:
> >
> http://www.nabble.com/Error-deployment-BPEL--UndeclaredPartnerLink-tp15884549p19624961.html
> > Sent from the Apache Ode User mailing list archive at Nabble.com.
> >
> >
>