Subject:Is there an XSD import limitation to a certain nested level? Author:Jacob Stuart Date:13 Jul 2006 03:39 PM
I am using the evaluation version of the Enterprise edition and have a purchase request in place with my purchasing department for the full license. However, while waiting for the purchase to go through, I'm using the evaluation version to work on the project that I need the software for.
What I'm running into is that it seems there's a limit to the number of nested, imported XSDs I can pull in when mapping an XSLT. My company uses BizTalk to generate the XSDs and so there are a LOT of them being imported from one schema and then from nested schemas.
Stylus Studio is doing a great job of it (using a custom catalog file and such), but it stops pulling in the schemas of nested elements after a certain level. It looks like the primary schema document (ProcessRequest.xsd) imports, among other schemas, an xsd (Action.xsd), then that Action.xsd imports another xsd (UpdateRequest.xsd), but then the imports of UpdateRequest.xsd are not imported. If I choose UpdateRequest.xsd by itself, all of its nested/imported schemas are pulled in correctly. That and through some other verification it seems like the schemas are setup correctly and should work.
So I'm left with wondering if there is a limitation on the trial version or with Stylus Studio itself. If it can't pull all the nested schemas then I'm going to need to revoke my purchase request since it will not work for my needs.