Look at the attached project, logically there is no error in the orchestrati
on, the map is initializing the Msg1 and then its used by the last shape, bu
t it can't compile :-(



How many times I should initialize Msg1?



Thanks



G. Tarazi

http://www.LiveTechnologies.ca

[ Post a follow-up to this message ]

Move the message assignment shape into the same construct block with the tra
nsform shape.  You are trying to construct the message twice, but what you w
ant is to construct it once but in a two step process.  

Matt
"G. Tarazi" <Tarazi@LiveTechnologies.ca> wrote in message news:e2$pJUvMEHA.2
468@TK2MSFTNGP11.phx.gbl...
Look at the attached project, logically there is no error in the orchestrati
on, the map is initializing the Msg1 and then its used by the last shape, bu
t it can't compile :-(



How many times I should initialize Msg1?



Thanks



G. Tarazi

http://www.LiveTechnologies.ca

[ Post a follow-up to this message ]

Thank you, it worked after the changes, but how can I change the value of a 
message in 2 different places in the orchestration?

"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message ne
ws:%23yA6GUxMEHA.2488@TK2MSFTNGP10.phx.gbl...
Move the message assignment shape into the same construct block with the tra
nsform shape.  You are trying to construct the message twice, but what you w
ant is to construct it once but in a two step process.  

Matt
"G. Tarazi" <Tarazi@LiveTechnologies.ca> wrote in message news:e2$pJUvMEHA.2
468@TK2MSFTNGP11.phx.gbl...
Look at the attached project, logically there is no error in the orchestrati
on, the map is initializing the Msg1 and then its used by the last shape, bu
t it can't compile :-(



How many times I should initialize Msg1?



Thanks



G. Tarazi

http://www.LiveTechnologies.ca

[ Post a follow-up to this message ]

Messages are immutable, so you create a message once and then use it. If you
 need to change the message, you create a new message of the same type.  You
 can easily use an assignment shape to assign msg1 to msg2, then modify msg2
 in that same construct shape (using a message assignment shape).  

Matt


"G. Tarazi" <Tarazi@LiveTechnologies.ca> wrote in message news:OFVGhd4MEHA.3
052@TK2MSFTNGP12.phx.gbl...
Thank you, it worked after the changes, but how can I change the value of a 
message in 2 different places in the orchestration?

"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message ne
ws:%23yA6GUxMEHA.2488@TK2MSFTNGP10.phx.gbl...
Move the message assignment shape into the same construct block with the tra
nsform shape.  You are trying to construct the message twice, but what you w
ant is to construct it once but in a two step process.  

Matt
"G. Tarazi" <Tarazi@LiveTechnologies.ca> wrote in message news:e2$pJUvMEHA.2
468@TK2MSFTNGP11.phx.gbl...
Look at the attached project, logically there is no error in the orchestrati
on, the map is initializing the Msg1 and then its used by the last shape, bu
t it can't compile :-(



How many times I should initialize Msg1?



Thanks



G. Tarazi

http://www.LiveTechnologies.ca

[ Post a follow-up to this message ]

Actually I have no problem with that, my only concern is if I have message1 
that is 10 to 20 MB, and I would like to modify one of it's parameters, I wi
ll assign it to message2 and modify message2, now is the assignment of messa
ge1 to message2 is referencing, or entire copy of the 10 MB from msg1 to msg
2?



Thank you



"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message ne
ws:%23IMMT3CNEHA.2676@TK2MSFTNGP12.phx.gbl...
Messages are immutable, so you create a message once and then use it. If you
 need to change the message, you create a new message of the same type.  You
 can easily use an assignment shape to assign msg1 to msg2, then modify msg2
 in that same construct shape (using a message assignment shape).  

Matt


"G. Tarazi" <Tarazi@LiveTechnologies.ca> wrote in message news:OFVGhd4MEHA.3
052@TK2MSFTNGP12.phx.gbl...
Thank you, it worked after the changes, but how can I change the value of a 
message in 2 different places in the orchestration?

"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message ne
ws:%23yA6GUxMEHA.2488@TK2MSFTNGP10.phx.gbl...
Move the message assignment shape into the same construct block with the tra
nsform shape.  You are trying to construct the message twice, but what you w
ant is to construct it once but in a two step process.  

Matt
"G. Tarazi" <Tarazi@LiveTechnologies.ca> wrote in message news:e2$pJUvMEHA.2
468@TK2MSFTNGP11.phx.gbl...
Look at the attached project, logically there is no error in the orchestrati
on, the map is initializing the Msg1 and then its used by the last shape, bu
t it can't compile :-(



How many times I should initialize Msg1?



Thanks



G. Tarazi

http://www.LiveTechnologies.ca

[ Post a follow-up to this message ]

I believe it is a copy, but don't know that 100%.  

Your best bet might be to look at doing this in a pipeline component if it m
akes sense so you can take advantage of the streaming capabilities there.  

If you are doing it in orchestration, then you might also want to try and wo
rk your orchestration so that you have the values you need to construct the 
message once instead of twice.  I realize this might not be feasible since y
ou might need to change msg1, send it out to get more data, then create the 
msg2 with that new data and the original.  

Matt

"G. Tarazi" <Tarazi@LiveTechnologies.ca> wrote in message news:OVPn6yDNEHA.3
452@TK2MSFTNGP10.phx.gbl...
Actually I have no problem with that, my only concern is if I have message1 
that is 10 to 20 MB, and I would like to modify one of it's parameters, I wi
ll assign it to message2 and modify message2, now is the assignment of messa
ge1 to message2 is referencing, or entire copy of the 10 MB from msg1 to msg
2?



Thank you



"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message ne
ws:%23IMMT3CNEHA.2676@TK2MSFTNGP12.phx.gbl...
Messages are immutable, so you create a message once and then use it. If you
 need to change the message, you create a new message of the same type.  You
 can easily use an assignment shape to assign msg1 to msg2, then modify msg2
 in that same construct shape (using a message assignment shape).  

Matt


"G. Tarazi" <Tarazi@LiveTechnologies.ca> wrote in message news:OFVGhd4MEHA.3
052@TK2MSFTNGP12.phx.gbl...
Thank you, it worked after the changes, but how can I change the value of a 
message in 2 different places in the orchestration?

"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message ne
ws:%23yA6GUxMEHA.2488@TK2MSFTNGP10.phx.gbl...
Move the message assignment shape into the same construct block with the tra
nsform shape.  You are trying to construct the message twice, but what you w
ant is to construct it once but in a two step process.  

Matt
"G. Tarazi" <Tarazi@LiveTechnologies.ca> wrote in message news:e2$pJUvMEHA.2
468@TK2MSFTNGP11.phx.gbl...
Look at the attached project, logically there is no error in the orchestrati
on, the map is initializing the Msg1 and then its used by the last shape, bu
t it can't compile :-(



How many times I should initialize Msg1?



Thanks



G. Tarazi

http://www.LiveTechnologies.ca

[ Post a follow-up to this message ]

quote:
Originally posted by G. Tarazi 
Look at the attached project, logically there is no error in the orchestrati
on, the map is initializing the Msg1 and then its used by the last shape, bu
t it can't compile :-(



How many times I should initialize Msg1?



Thanks



G. Tarazi

http://www.LiveTechnologies.ca 

[ Post a follow-up to this message ]