I've found the solution... The problem was that I didn't initialize my destination variable before the assign. I tried a tutorial about the design of BPEL process with the eclipse plug-in, that make a HelloWorld process. It's work, but if i delete the initialization assign, I find the same error.
Maybe adding a notice to say that initialization is required would be a good idea because this error message is not easily understandable... I found the solution with lucky :) Thank you for your time. Cheers, Sandrine. Matthieu Riou-5 wrote: > > On Wed, Dec 10, 2008 at 9:26 AM, Sandrine Beauche < > [EMAIL PROTECTED]> wrote: > >> >> No deployment too... >> > > Any compilation error reported by ODE? Have you tried setting a namespace > prefix for BPEL so you can have an empty namespace when required as I > mentioned? > > Thanks, > Matthieu > > > >> >> Sandrine. >> >> >> Matthieu Riou-5 wrote: >> > >> > On Wed, Dec 10, 2008 at 7:16 AM, Sandrine Beauche < >> > [EMAIL PROTECTED]> wrote: >> > >> >> >> >> If I modify like this, I can't deploy the service. >> >> >> > >> > Mmh yeah, Alex probably typed his example too quick as the xmlns would >> > change the namespace of the BPEL from element. Try this: >> > >> > <copy> >> > <from >> > xmlns:emptyns="">$myVar.TestPart/emptyns:hello1</from> >> > <to variable="tmpVar1"/> >> > </copy> >> > >> > Generally speaking, I would advise using a prefix for the BPEL >> namespace. >> > Otherwise no prefix in your XML literals end up being in the BPEL >> > namespace >> > which is usually not what you want and gets confusing. >> > >> > Cheers, >> > Matthieu >> > >> > >> >> Sandrine. >> >> >> >> >> >> Alex Boisvert-3 wrote: >> >> > >> >> > It appears to be a namespacing issue. The "hello1" element in your >> >> SOAP >> >> > message and in your WSDL definition is not namespace-qualified, >> whereas >> >> in >> >> > your assignment you use the "nsxsd" prefix binding. >> >> > >> >> > Try the following: >> >> > >> >> > <copy> >> >> > <from xmlns="">$myVar.TestPart/hello1</from> >> >> > <to variable="tmpVar1"/> >> >> > </copy> >> >> > >> >> > alex >> >> > >> >> > On Tue, Dec 9, 2008 at 9:43 AM, Sandrine Beauche < >> >> > [EMAIL PROTECTED]> wrote: >> >> > >> >> >> >> >> >> Hi Alex, >> >> >> >> >> >> ok, I've resent the exemple with a zip archive >> >> >> >> >> >> Sandrine. >> >> >> >> >> >> >> >> >> http://www.nabble.com/file/p20919709/HelloWorld2.zip >> HelloWorld2.zip >> >> >> >> >> >> >> >> >> Hi Sandrine, >> >> >> >> >> >> I don't see a problem with your assignments. >> >> >> >> >> >> Your attachments were truncated. Could you zip them and resend? >> >> >> >> >> >> alex >> >> >> >> >> >> >> >> >> On Tue, Dec 9, 2008 at 8:22 AM, Sandrine Beauche < >> >> >> [EMAIL PROTECTED]> wrote: >> >> >> >> >> >> > >> >> >> > I've tried to do an assign from a complex type to another >> variable, >> >> and >> >> >> > this >> >> >> > works when the complex type has one subtype. >> >> >> > >> >> >> > But my problem is to do this with a complex type that have >> several >> >> >> > subtype. >> >> >> > I >> >> >> > have in my wsdl this complex type: >> >> >> > >> >> >> > <xsd:complexType name="helloType"> >> >> >> > <xsd:sequence> >> >> >> > <xsd:element name="hello1" type="xsd:string"/> >> >> >> > <xsd:element name="hello2" type="xsd:string"/> >> >> >> > </xsd:sequence> >> >> >> > </xsd:complexType> >> >> >> > >> >> >> > and the message: >> >> >> > >> >> >> > <wsdl:message name="HelloMessage"> >> >> >> > <wsdl:part name="TestPart" type="nsxsd:helloType"/> >> >> >> > </wsdl:message> >> >> >> > >> >> >> > In my BPEL, I have these variable >> >> >> > >> >> >> > <variable name="myVar" messageType="test:HelloMessage"/> >> >> >> > <variable name="tmpVar1" type="xsd:string"/> >> >> >> > <variable name="tmpVar2" type="xsd:string"/> >> >> >> > >> >> >> > and I want to do these assign: >> >> >> > >> >> >> > <copy> >> >> >> > <from>$myVar.TestPart/nsxsd:hello1</from> >> >> >> > <to variable="tmpVar1"/> >> >> >> > </copy> >> >> >> > <copy> >> >> >> > <from>$myVar.TestPart/nsxsd:hello2</from> >> >> >> > <to variable="tmpVar2"/> >> >> >> > </copy> >> >> >> > >> >> >> > But this does'nt work. I obtain a message fault: >> >> >> > >> >> >> > <soapenv:Body> >> >> >> > <soapenv:Fault> >> >> >> > <faultcode>soapenv:Server</faultcode> >> >> >> > <faultstring xmlns:axis2ns1="http://docs.oasis >> >> >> > open.org/wsbpel/2.0/proces /executable"> >> axis2ns1:selectionFailure >> >> >> > </faultstring> >> >> >> > <detail /> >> >> >> > </soapenv:Fault> >> >> >> > </soapenv:Body> >> >> >> > >> >> >> > What's wrong in my bpel or wsdl? The complete bpel and wsdl are >> >> >> attached. >> >> >> > I >> >> >> > have also attached a soap message that i send to the process to >> >> test >> >> >> it. >> >> >> > >> >> >> > -- >> >> >> > Thanks. >> >> >> > >> >> >> > >> >> >> >> >> >> >> >> >> -- >> >> >> View this message in context: >> >> >> >> >> >> http://www.nabble.com/assign-with-complex-types-tp20919141p20919709.html >> >> >> Sent from the Apache Ode User mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/assign-with-complex-types-tp20919141p20937253.html >> >> Sent from the Apache Ode User mailing list archive at Nabble.com. >> >> >> >> >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/assign-with-complex-types-tp20919141p20939929.html >> Sent from the Apache Ode User mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/assign-with-complex-types-tp20919141p20959672.html Sent from the Apache Ode User mailing list archive at Nabble.com.
