|
Home > Archive > BizTalk Server Orchestration > June 2005 > shared WSE schemas
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
shared WSE schemas
|
|
| PCTC_IT 2005-06-20, 8:49 pm |
| I put my WSE schemas in a separate assembly so that i can reuse them with
multipe orchestrations without namespace conflicts. My issue is that i am
using the same Web Service schema in 3 orchestrations, but now one of the web
methods changed (so i have to update the schema).
So i try to undeploy my schema assembly but it won't let me with out
undeploying all my other assemblies that reference those schemas. Is there
any way around this or maybe a better way to set it up?
Thanks,
PCTC_IT
| |
| Scott Colestock 2005-06-22, 5:51 pm |
| That is a typical BizTalk issue - "most dependent" assemblies must be
undeployed prior to "least dependent" being undeployed, if you follow me.
Note if the sum total of your schema changes are element/attribute related
(not changing root records, type names, distinguished fields, etc.) then you
can simply re-gac the schema assembly and restart the host. Depending on
your situation, this may or may not save you pain.
Scott Colestock
www.traceofthought.net
"PCTC_IT" <PCTCIT@discussions.microsoft.com> wrote in message
news:B017D746-A32C-4325-900A-40D37623DAF1@microsoft.com...
>I put my WSE schemas in a separate assembly so that i can reuse them with
> multipe orchestrations without namespace conflicts. My issue is that i am
> using the same Web Service schema in 3 orchestrations, but now one of the
> web
> methods changed (so i have to update the schema).
>
> So i try to undeploy my schema assembly but it won't let me with out
> undeploying all my other assemblies that reference those schemas. Is
> there
> any way around this or maybe a better way to set it up?
>
> Thanks,
>
> PCTC_IT
|
|
|
|
|