xsd - BizTalk: Deploying large XML schema (OAGIS) split into multiple documents -


currently, deploying oagis xml schema set biztalk 2010 visual studio 2010. has taken 3 hours far no finish in sight. in visual studio output log, there 18,000 lines now. keep getting messages such as:

warning deploy: schema "oagischemata.oagi_bpi_platform.org_openapplications_platform._1_2_1.common.oagi.components.fields,  oagischemata, version=1.0.0.0, culture=neutral, publickeytoken=afe0ae2252ec000f" , deployed schema ""  have same target namespace "http://www.openapplications.org/oagis/9". target namespaces should unique. 

indeed, there several schema documents same namespace should no issue. xml schema specification allows schema designer split schema multiple files. in altova xmlspy, same schema set works out neither errors nor warnings.

can biztalk handle large schema split multiple files? if can, there way speed deployment? insane.

the deployment finished total duration of 6 hours. in log, there 25,000 warnings in total, of them similar 1 in question.

can biztalk handle large schema split multiple files?

despite warnings, xml schema set seems work without problems.

is there way speed deployment?

an obvious way remove parts not required current usage. actually, current deployment includes purchaseorder noun (there dozens of nouns in total). actual problem seems number of reusable components in oagis. located in few files, many. removing unused components require editing original schema files, not practical.


Comments

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

keyboard - Smiles and long press feature in Android -

node.js - Bad Request - node js ajax post -