We have a bunch of BTS orchestrations exposed as web services that have
their input/output messages described in a couple of referenced BTS schema
projects. These schema projects are now fairly large (one of them about
5Mb - we have a lot of schemas!).
The projects contain namespaced versioning schemas (each in their own
versioned folder hierarchy) and they are compiled into a .Net assembly
that
is always version 1.0.0.0 as we are loathe to introduce multiple versions
of
these large files.
I appreciate this is likely not the best way of doing things so I wondered
if anyone could give any guidance on how to best to organise these schema
projects?
This question has just come to me after I've left work so I have no way of
checking what I'm about to ask until Wednesday am but can we call a halt
to
version 1.0.0.0 and when schemas need to be maintained (i.e. create new
versions of some of our schemas) can we reference the 1.0.0.0 assembly and
add new xsd files comiling these few new schemas into version 1.0.0.1 for
example which will reduce the size of the second assembly.
Secondly, we do mapping based on the schemas and BizTalk creates xslt to
do
this. When we come to deploy these orchs what does BTS do in terms of
looking for these referenced schemas? i.e. must the schemas used to build
the mappings/interfaces be present and upto date?
Thanks for any help
AP
--
My Inbox is a temple - please remove SHOES before entering
