I have a schema generated from an SQL adapter. This schema will provide the
basis for a message which supplies information to a stored procedure so it
can return me some configuration information I regquire for the rest of my
orchestration.

I have tried to create this message by using and Assignemnt shape inside a
construct shape. I have ticked the box saying to construct a message of this
type.

However, when I try to assigne values to the promoted properties of the
schema, I get the error that I have not constructed the message.

Elsewhere in my orchestration I do the say construction for a message that
will supply information to a web request.

Is there something special I need to do for a SQL adapter generated stored
procedure call?

So far, I have had to build this message using a "dummy" map. This does not
seem right t me.

All suggestions appreciated.

Steve

[ Post a follow-up to this message ]

Steve, I am having a similar problem and it is not specific to SQLAdapter. I
am using ports that write to a flat file only, and I am receiving this error
on one of out three of these configured ports. I am anxious to see what
response you/we may receive about this...

"SteveM" wrote:

> I have a schema generated from an SQL adapter. This schema will provide th
e
> basis for a message which supplies information to a stored procedure so it
> can return me some configuration information I regquire for the rest of my
> orchestration.
>
> I have tried to create this message by using and Assignemnt shape inside a
> construct shape. I have ticked the box saying to construct a message of th
is
> type.
>
> However, when I try to assigne values to the promoted properties of the
> schema, I get the error that I have not constructed the message.
>
> Elsewhere in my orchestration I do the say construction for a message that
> will supply information to a web request.
>
> Is there something special I need to do for a SQL adapter generated stored
> procedure call?
>
> So far, I have had to build this message using a "dummy" map. This does no
t
> seem right t me.
>
> All suggestions appreciated.
>
> Steve

[ Post a follow-up to this message ]

Actually, using the map is one way to do it.  Web Services with simple type
parameters are a special case where the message construction process only
requires that you specify the message to be constructed.  For all other
messages, you need to actually create the messages that you indicate are to
be created using either a map, code and XMLDocument, or assigning one
message to another.

Matt


"SteveM" <SteveM@discussions.microsoft.com> wrote in message
news:C1ADECB4-17CC-4381-967C-795D01FE47C3@microsoft.com...
>I have a schema generated from an SQL adapter. This schema will provide the
> basis for a message which supplies information to a stored procedure so it
> can return me some configuration information I regquire for the rest of my
> orchestration.
>
> I have tried to create this message by using and Assignemnt shape inside a
> construct shape. I have ticked the box saying to construct a message of
> this
> type.
>
> However, when I try to assigne values to the promoted properties of the
> schema, I get the error that I have not constructed the message.
>
> Elsewhere in my orchestration I do the say construction for a message that
> will supply information to a web request.
>
> Is there something special I need to do for a SQL adapter generated stored
> procedure call?
>
> So far, I have had to build this message using a "dummy" map. This does
> not
> seem right t me.
>
> All suggestions appreciated.
>
> Steve

[ Post a follow-up to this message ]

Thanks Matt,

I guess that is where my confusion lies. If I create it in code, is that in
an expression statement prior to a construct or in an assignemnt shape withi
n
a construct.

Perhaps if you can throw a little of the syntax for this create statement in
my direction things may be a little clearer.

I have tried to say
Msg_GetConfig = new ...

But this doesn't seem to allow me to reference the schema I need.

Should I even be using a predefined message?

I thought that the construct shape would construct the message object
because I had told it to.

TIA

Steve

"Matt Milner" wrote:

> Actually, using the map is one way to do it.  Web Services with simple typ
e
> parameters are a special case where the message construction process only
> requires that you specify the message to be constructed.  For all other
> messages, you need to actually create the messages that you indicate are t
o
> be created using either a map, code and XMLDocument, or assigning one
> message to another.
>
> Matt
>
>
> "SteveM" <SteveM@discussions.microsoft.com> wrote in message
> news:C1ADECB4-17CC-4381-967C-795D01FE47C3@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Nope, the construct shape doesn't know how to construct your message.  There
can be so much variability in a message that matches a schema that it would
be hard to guess what you wanted.

You'd first declare an orchestration variable of type XmlDocument.

Then in a message assignment shape, you'd do something like this:
myxmlDoc = new XmlDocument();
myxmlDoc.LoadXML("<somexmlhere></somexmlhere>")
myMsgBeingConstructed = myxmlDoc;


Matt



"SteveM" <SteveM@discussions.microsoft.com> wrote in message
news:38D01D94-D9B0-446C-97FA-59E2129725FE@microsoft.com...[vbcol=seagreen]
> Thanks Matt,
>
> I guess that is where my confusion lies. If I create it in code, is that
> in
> an expression statement prior to a construct or in an assignemnt shape
> within
> a construct.
>
> Perhaps if you can throw a little of the syntax for this create statement
> in
> my direction things may be a little clearer.
>
> I have tried to say
> Msg_GetConfig = new ...
>
> But this doesn't seem to allow me to reference the schema I need.
>
> Should I even be using a predefined message?
>
> I thought that the construct shape would construct the message object
> because I had told it to.
>
> TIA
>
> Steve
>
> "Matt Milner" wrote:
> 

[ Post a follow-up to this message ]