|
Home > Archive > BizTalk Server General > March 2005 > my schema is not in the list when configuring the XmlDisassembler
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 |
my schema is not in the list when configuring the XmlDisassembler
|
|
| Yossi Dahan 2005-02-22, 5:50 pm |
|
We have two schemas that are exactly the same, but have different property
promotion settings.
We have two different pipelines, each one should use a different schema for
the promotion, in those we wish to use the standard XmlDisassembler to
perform the promotion, because both schemas have the same root node and
namespace we know we have to specify explicitly which schema should be used
in which pipeline, so we created two pipelines, dropped the XmlDisassembler
component in the disassemble stage of both, and tried to select the schema
from the list, however, our schemas were not on the list.
The documentation on this is vague and (as confirmed by MS) incorrect when
initially it says that the list shows only schemas with unique target
namespace but later suggests that if there are two schemas with the same
target namespace the correct one should be manually selected.
Did someone manage to have two identical schemas deployed and used with the
XmlDisassembler?
What is the correct way to do so?
Thank you
Yossi Dahan
| |
| Jon Flanders[DevelopMentor] 2005-02-22, 5:50 pm |
| Yossi - you need to add a reference to the schemas in the project that is
creating the pipelines.
--
Jon Flanders [DevelopMentor]
http://staff.develop.com/jfland/
http://www.develop.com/courses/biztalk
"Yossi Dahan" <yossidahan@hotmail.com> wrote in message
news:%23FoOvvOGFHA.3908@TK2MSFTNGP12.phx.gbl...
>
> We have two schemas that are exactly the same, but have different property
> promotion settings.
>
> We have two different pipelines, each one should use a different schema
> for
> the promotion, in those we wish to use the standard XmlDisassembler to
> perform the promotion, because both schemas have the same root node and
> namespace we know we have to specify explicitly which schema should be
> used
> in which pipeline, so we created two pipelines, dropped the
> XmlDisassembler
> component in the disassemble stage of both, and tried to select the schema
> from the list, however, our schemas were not on the list.
>
> The documentation on this is vague and (as confirmed by MS) incorrect when
> initially it says that the list shows only schemas with unique target
> namespace but later suggests that if there are two schemas with the same
> target namespace the correct one should be manually selected.
>
> Did someone manage to have two identical schemas deployed and used with
> the
> XmlDisassembler?
> What is the correct way to do so?
>
> Thank you
>
> Yossi Dahan
>
>
>
| |
| Yossi Dahan 2005-02-28, 5:53 pm |
| Jon hi,
Thanks for the reply, I just tried adding a reference to the assembly
with the schema and it did not help.
the list, I believe, works off the deployed schemas and not an
assembly.
Am i wrong?
any other ideas?
Yossi
| |
| Matt Milner 2005-03-02, 2:46 am |
| I believe you are correct. Interestingly, I believe the flat file schema
picker for the disassembler works differently from the XML disassembler.
Very strange.
matt
"Yossi Dahan" <yossi@dnd.co.il> wrote in message
news:1109606476.916551.44380@o13g2000cwo.googlegroups.com...
> Jon hi,
>
> Thanks for the reply, I just tried adding a reference to the assembly
> with the schema and it did not help.
> the list, I believe, works off the deployed schemas and not an
> assembly.
>
> Am i wrong?
>
> any other ideas?
>
> Yossi
>
|
|
|
|
|