Nancy,
why do you need to initialize the response field with a literal before mapping it?
this is required by BPEL. I don't know all the reasons why BPEL requires that, but the part that makes sense is that initializing with a literal creates the strucuture (you don't really need to set values, excepts things you know will not change, or don't need to be copied from somewhere else). That is, unless you assign the top level element, BPEL requires that you have something to receive the data you copying to. Said an other way, if you look at your XML data as a tree, you need the branches to be there before you can attach your leaves.

When the mapper functionality is fully there, it will make this requirement a lot more transparent than it is today.
Thanks,
Pascal.

Hi,

Thanks for your answer, but I am not sure I understood it properly. You wrote that it is possible to do a "field to field" direct mapping; if this is the case, why dit you create a local variable "a" in your process? why not do a direct mapping (after having initialized the response with a literal)?

Thanks,

Nancy

Hi!

Nancy

It is just an example there is no hard and fast rule to use variables. You can do direct mapping. To avoid your confusion I am attaching new Example.n3x file using only schemas. Hope this clears your doubt

Thanks
Chandra
:)

Hi Chandra,

Thanks very much; unfortunately I still have problems with fields mapping..! I am sending you the project I am working on.
My problem is the following : I can't assign one of the fields of my response to the client (ClientId field) to a value contained in my string variable "a", that I previously assigned to another field, contained in the Response of a WebService that I call (UpdateClient).
The WSDLs of my webServices are included in the project, maybe you can generate a web service from them and try to deploy and run the process; if you face the same pb as me you'll get a "MessageExchange failure".
I tried to do direct mapping between fields instead of using a variable; but I got exactly the same error.
Furthemore I can't find anything in the PXE logs (and the Web Service UpdateClient that I use has no logs either, but it has been previously tested and is supposed to work all right...)
Any idea???
Thanks very much!
Nancy

Hi!

Nancy

I am working on your process and found two issues in Data Editor

Go to Data Editor and expand the nodes Call eligibilte and Call Synchro Client

Under both these nodes you have not define any thing under :
1.incoming for $etudierEligibilteResponse(intf:etudierEligibilteResponse)
2.incoming for $consulterClientParNDResponse(intf:consulterClientParNDResponse)
So I’ll just workout on your process and reply you back again with the result

Thanks
Chandra
;)

Hi!

Nancy

I've just defined the values under these two incoming messages

The Message Exchange failure is occuring because you are not defining anything under incoming messages.
Due to which your message is'nt going furthur

So i hope we'll be getting the result

Thanks
Chandra

Post edited by: cshekhar, at: 2006/05/05 03:55