Hello,

I am unable to move forward with even a simple orchestration becuase
of the XSD schemas I am using.

I have 2 XSD schemas which (one included the other) make up a single
schema (source).  One file is 2k, the included file with the
definitions is 457k.

Whenever I try to compile, validate or basically anything which
invlolves accessing this larger xsd file I get a the process 'devenv'
running at 98% until I finally decide to quit.  I have waited as long
as 40 minutes to see an end to a compilation or validation but I get
nothing!

I am out of options here.  What can I do to get this thing to compile?

Thanks

Isaac Ferreira
Application Architect
BizTalk Developer

[ Post a follow-up to this message ]

Can you attach your schemas for us to take a look at?

Thank you,
--
Dave

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------[vbcol=seagreen] 
09:43:36 GMT)[vbcol=seagreen] 
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!news.glorb.com!postnews2.google.com!not-for-mail[vbcol=seagreen] 

[ Post a follow-up to this message ]

Hello Dave,

I emailed the schemas to you, they are too large to post here, I think.

Regards,
Isaac Ferreira
Application Architect
BizTalk Developer



ddowning@online.microsoft.com ("David Downing [MSFT]") wrote in message news:<oGRMGmTiEH
A.3064@cpmsftngxa10.phx.gbl>...[vbcol=seagreen]
> Can you attach your schemas for us to take a look at?
>
> Thank you,
> --
> Dave
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> -------------------- 
>  09:43:36 GMT) 
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00
.s
> ul.t-online.de!t-online.de!news.glorb.com!postnews2.google.com!not-for-mai
l 

[ Post a follow-up to this message ]

On 23 Aug 2004 02:43:36 -0700, Isaac Ferreira wrote:

> Hello,
>
> I am unable to move forward with even a simple orchestration becuase
> of the XSD schemas I am using.
>
> I have 2 XSD schemas which (one included the other) make up a single
> schema (source).  One file is 2k, the included file with the
> definitions is 457k.
>
> Whenever I try to compile, validate or basically anything which
> invlolves accessing this larger xsd file I get a the process 'devenv'
> running at 98% until I finally decide to quit.  I have waited as long
> as 40 minutes to see an end to a compilation or validation but I get
> nothing!
>
> I am out of options here.  What can I do to get this thing to compile?
>
> Thanks
>
> Isaac Ferreira
> Application Architect
> BizTalk Developer

Hi Isaac,

Can you send me your project? I'll have a look at it.

kind regards,

Martijn

[ Post a follow-up to this message ]

Dave,

I will post both schemas in seperate posts.....

Here is the MAIN schema, the one which INCLUDES the definitions
schema....


<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" attributeFormDefault="unqualified"
version="200401">
<xs:include schemaLocation="papiNetCommonDefsV2R20.xsd"/>
<!--Copyright 2000-2004  papiNet G.I.E (papiNet), International
Digital Enterprise Alliance, Inc. (IDEAlliance), and American Forest
and Paper Association, Inc. (AFPA), collectively Copyright Owner. All
rights reserved by the Copyright Owner under the laws of the United
States, Belgium, the European Economic Community, and all states,
domestic and foreign.  For support, more information, or to report
implementation bugs, please contact papiNet at www.papiNet.org.-->
<xs:element name="DeliveryMessage">
<xs:complexType>
<xs:sequence>
<xs:element ref="DeliveryMessageHeader"/>
<xs:element ref="DeliveryMessageLineItem" maxOccurs="unbounded"/>
<xs:element ref="DeliveryMessageSummary"/>
</xs:sequence>
<xs:attribute name="DeliveryMessageType" type="deliveryMessageType"
use="required"/>
<xs:attribute name="DeliveryMessageStatusType"
type="deliveryMessageStatusType" use="required"/>
<xs:attribute name="Reissued" type="yesNo" default="No"/>
<xs:attribute name="Language" type="languageType" default="eng"/>
</xs:complexType>
</xs:element>
<xs:element name="DeliveryMessageHeader"
type="deliveryMessageHeader"/>
<xs:element name="DeliveryMessageLineItem"
type="deliveryMessageLineItem"/>
<xs:element name="DeliveryMessageSummary"
type="deliveryMessageSummary"/>
</xs:schema>

[ Post a follow-up to this message ]

Sorry for the late response... it took awhile to research.  What's
happening is that your schemas don't have the "Root Reference" specified.
During the compilation, a new class is created for each root node if the
"Root Reference" is not specified.  Try setting this for both schemas, and
you should see significant improvement.

Dave
--------------------[vbcol=seagreen] 
<oGRMGmTiEHA.3064@cpmsftngxa10.phx.gbl>[vbcol=seagreen] 
09:41:15 GMT)[vbcol=seagreen] 
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!fr.ip.ndsoftware.net!proxad.net!postnews2.google.
com!not-for-mail[vbcol=seagreen] 

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

[ Post a follow-up to this message ]

On Tue, 24 Aug 2004 10:54:40 +0200, Martijn Hoogendoorn wrote:

> On 23 Aug 2004 02:43:36 -0700, Isaac Ferreira wrote:
> 
>
> Hi Isaac,
>
> Can you send me your project? I'll have a look at it.
>
> kind regards,
>
> Martijn

Sorry for the delayed response, I had a wonderful lengthy e-mail written to
you when there was a power network blackout. The short answer: I'm having
the same difficulties. I even tried splitting up the schema in separate
smaller schemas, but that didn't compile as well. To allow you to test it,
I've e-mailed it. I'm sorry I cannot help you here, I think there's some
kind of hickup with Visual Studio handling those pesky large schemas,
although the HL7 standard defines larger schemas, which work... This might
be worth looking into..

HTH,

Martijn Hoogendoorn

[ Post a follow-up to this message ]

On Thu, 26 Aug 2004 10:42:18 +0200, Martijn Hoogendoorn wrote:

> On Tue, 24 Aug 2004 10:54:40 +0200, Martijn Hoogendoorn wrote:
> 
>
> Sorry for the delayed response, I had a wonderful lengthy e-mail written t
o
> you when there was a power network blackout. The short answer: I'm having
> the same difficulties. I even tried splitting up the schema in separate
> smaller schemas, but that didn't compile as well. To allow you to test it,
> I've e-mailed it. I'm sorry I cannot help you here, I think there's some
> kind of hickup with Visual Studio handling those pesky large schemas,
> although the HL7 standard defines larger schemas, which work... This might
> be worth looking into..
>
> HTH,
>
> Martijn Hoogendoorn

My Bad!

After posting this, I David Downing's reply to your request. He's right, I
tried his solution and it works peachy...

HTH,

Martijn Hoogendoorn

[ Post a follow-up to this message ]

Hello,

The problem has finally been solved thanks to help from Martijn
Hoogendoorn and also Microsoft.

For a schema which has includes you must set a "root reference"

To do this:

Go to the properties of the ROOT file and navigate to the "reference"
block, enter here the message type

Go to the properties of the INCLUDED file and navigate to the
"reference" block, enter here the message type (ususally with a
reference attached)

This should include only the relevant definitions inside the
compilation and enable the compiler to complete.

It would be more useful to force this property inside the "Imports"
collection, that way it would not be missed.

Thanks to everyone which contributed to this solution....

Isaac Ferreira
Application Architect
BizTalk Developer

[ Post a follow-up to this message ]