On Sun, Sep 21, 2008 at 10:58 PM, Druid <[EMAIL PROTECTED]> 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. > >
