Ok here's the scenerio.

I have a message which contains multiple child nodes which I have to call a
webservice for each corresponding node.  After I call the webservice I need
to call the rule engine as well.  I am using System.Xml.NodeList to access
the values within the XmlDocument and to loop on using the looping construct
.


The webservice call requires a Long Running Transaction
The rules requires an atomic transaction
The XmlNodeList requires the entire orchestration be atomic just to define
the structure.

So basically, if I want to call the webservice I need the orchestration to
be long running.  If I want to use XmlNodeList I have to make the
orchestration transaction Atomic.  So basically I cannot use NodeList becaus
e
the stupid thing is not serializable.  That is just plain stupid!  Thank you
for the venting...

[ Post a follow-up to this message ]

For the structure of your orchestration, is it possible to declare your
XmlNodeList local to an atomic scope?  (Rather than at the orchestration
level?)
(Remember that you can have scope-level variable declarations)

Scott Colestock
www.traceofthought.net



"JGaska [http://www.IoniaSolutions.com]"
< JGaskahttpwwwIoniaSolutionscom@discussio
ns.microsoft.com> wrote in message
news:DF4F10EF-C50D-4595-86C3-652E9B755F82@microsoft.com...
>
> Ok here's the scenerio.
>
> I have a message which contains multiple child nodes which I have to call
> a
> webservice for each corresponding node.  After I call the webservice I
> need
> to call the rule engine as well.  I am using System.Xml.NodeList to access
> the values within the XmlDocument and to loop on using the looping
> construct.
>
>
> The webservice call requires a Long Running Transaction
> The rules requires an atomic transaction
> The XmlNodeList requires the entire orchestration be atomic just to define
> the structure.
>
> So basically, if I want to call the webservice I need the orchestration to
> be long running.  If I want to use XmlNodeList I have to make the
> orchestration transaction Atomic.  So basically I cannot use NodeList
> because
> the stupid thing is not serializable.  That is just plain stupid!  Thank
> you
> for the venting...
>
>
>
>
>

[ Post a follow-up to this message ]

Unfortunately no.  I need to call the webservice from within the looping
structure and I was going to use the XmlNodeList for the looping structure
and use that to call the webservice.  If I wrap the looping structure within
an atomic scope I will not be able to call the webservice using a long
running transaction because I cannot embed transactions within the atomic
scope.

Round and round I go........  I guess back to the xpath implementation huh,
instead of using the NodeList. etc..



"Scott Colestock" wrote:

> For the structure of your orchestration, is it possible to declare your
> XmlNodeList local to an atomic scope?  (Rather than at the orchestration
> level?)
> (Remember that you can have scope-level variable declarations)
>
> Scott Colestock
> www.traceofthought.net
>
>
>
> "JGaska [http://www.IoniaSolutions.com]"
> < JGaskahttpwwwIoniaSolutionscom@discussio
ns.microsoft.com> wrote in messag
e
> news:DF4F10EF-C50D-4595-86C3-652E9B755F82@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Hi,

One option may be to create a schema (ChildSchema) that represents the child
node, then include that in the main schema, setting the data structure type
for the child node to ChildSchema.

You can then use the message assignment, and some XPath to create a message
instance of ChildSchema. You can use a count and total as integers to contro
l
the loop.

I think I used this technique in a splitter pattern, you can download the
code here:

http://www.gotdotnet.com/Workspaces...br />
93ed7149

Regards,

Alan


--
The Bloggers Guide to BizTalk
http://geekswithblogs.com/asmith



"JGaska [http://www.IoniaSolutions.com]" wrote:
[vbcol=seagreen]
>
> Unfortunately no.  I need to call the webservice from within the looping
> structure and I was going to use the XmlNodeList for the looping structure
> and use that to call the webservice.  If I wrap the looping structure with
in
> an atomic scope I will not be able to call the webservice using a long
> running transaction because I cannot embed transactions within the atomic
> scope.
>
> Round and round I go........  I guess back to the xpath implementation huh
,
> instead of using the NodeList. etc..
>
>
>
> "Scott Colestock" wrote:
> 

[ Post a follow-up to this message ]

Alan;

Yes that is exactly what I am forced to do, but the only caveat is I have to
update the original message.  So I will use th xpath to update the message.
Thenks for the insight though.

-Joe

"Alan Smith" wrote:
[vbcol=seagreen]
> Hi,
>
> One option may be to create a schema (ChildSchema) that represents the chi
ld
> node, then include that in the main schema, setting the data structure typ
e
> for the child node to ChildSchema.
>
> You can then use the message assignment, and some XPath to create a messag
e
> instance of ChildSchema. You can use a count and total as integers to cont
rol
> the loop.
>
> I think I used this technique in a splitter pattern, you can download the
> code here:
>
> http://www.gotdotnet.com/Workspaces... />
8093ed7149
>
> Regards,
>
> Alan
>
>
> --
> The Bloggers Guide to BizTalk
> http://geekswithblogs.com/asmith
>
>
>
> "JGaska [http://www.IoniaSolutions.com]" wrote:
> 

[ Post a follow-up to this message ]