BizTalk Server Applications Integration - OAG XSD Import - BizTalk2004

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Applications Integration > November 2004 > OAG XSD Import - BizTalk2004





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 OAG XSD Import - BizTalk2004
Nick

2004-11-02, 8:46 pm

Hello,

I am trying to import an OAG XSD schema into BTS2004 project and I am
getting all sorts of error.

There are several INCLUDES in the primary XSD. Do I need to add all
of those in my reference list? If I do that then how do I change the
primary XSD to refer to these references?

Thanks in advance.
- Nick.
Greg Forsythe

2004-11-03, 7:47 am

You must add the primary XSD and all imported <xs:import> and included
<xs:include> schemas that the primary XSD uses into your project.
This can create a rather large and unwieldy project.

Another way of approaching this is to create a separate schema-only project
that just contains the OAG schemas. Build this project and add the resulting
..dll as a reference into your other project/s
When you need to reference a schema in your other project/s you can use the
<from referenced assembly> option.
You will need to deploy the OAG Assembly into Biztalk before deploying your
other project/s.
I have successfully done this with the OASIS UBL 1.0 schemas: ref
http://www.gotdotnet.com/Community/...23-fe72f317891a

If you use this method you will be able to reference any OAG schema from any
project.

Greg

"Nick" <nickchhabra@yahoo.com> wrote in message
news:f22e7f03.0411021743.90bb060@posting.google.com...
> Hello,
>
> I am trying to import an OAG XSD schema into BTS2004 project and I am
> getting all sorts of error.
>
> There are several INCLUDES in the primary XSD. Do I need to add all
> of those in my reference list? If I do that then how do I change the
> primary XSD to refer to these references?
>
> Thanks in advance.
> - Nick.



Nick

2004-11-04, 8:46 pm

Hello Greg,

I tried the first option and added all the imported and included
schemas that the primary XSD uses into my project.

When I try opening the primary schema I get a prompt "Invalid schema"
with details:

1) Cannot resolve schemaLocation attribute. An error occurred at
file:///C:/../Primary.xsd (15, 10) [this the line 3 where the include
is]
2) Undefined complexType
'http://www.openapplications.org/oagis:BusinessObjectDocument' is used
as a base for complex type extension". An error occurred at
file:///C:/../Primary.xsd, (26, 26)

And, when I try to validate the schema I get additional errors like

1) file:///C:/../Primary.xsd : error BEC2009: Node "<Schema>" - Schema
reference "../Resources/Verbs/Show.xsd" is not a valid reference or
does not exist in the current project.

What am I doing wrong? Any suggestion to get past this?

Appreciate your help.
- Nick.

"Greg Forsythe" <greg.forsythe@unisys.com> wrote in message news:<#FZvvqZwEHA.2728@TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
> You must add the primary XSD and all imported <xs:import> and included
> <xs:include> schemas that the primary XSD uses into your project.
> This can create a rather large and unwieldy project.
>
> Another way of approaching this is to create a separate schema-only project
> that just contains the OAG schemas. Build this project and add the resulting
> .dll as a reference into your other project/s
> When you need to reference a schema in your other project/s you can use the
> <from referenced assembly> option.
> You will need to deploy the OAG Assembly into Biztalk before deploying your
> other project/s.
> I have successfully done this with the OASIS UBL 1.0 schemas: ref
> http://www.gotdotnet.com/Community/...23-fe72f317891a
>
> If you use this method you will be able to reference any OAG schema from any
> project.
>
> Greg
>
> "Nick" <nickchhabra@yahoo.com> wrote in message
> news:f22e7f03.0411021743.90bb060@posting.google.com...
Greg Forsythe

2004-11-07, 2:46 am

Nick,
I downloaded OAG version 8.0 sp3 and tried to create a Biztalk project from
it.
I get a similar error.
The Biztalk schema editor is complaining about an invalid schema i.e. an
element and a complex type having the same name.
However, this is a valid Xml Schema ref:
http://www.w3.org/TR/xmlschema-1/#c...ameSymbolSpaces
which states:
"For example, the same name can appear in both a type definition and an
element declaration, without conflict or necessary relation between the
two."

Looks like a bug, you should raise this with Microsoft.

Greg





"Nick" <nickchhabra@yahoo.com> wrote in message
news:f22e7f03.0411041712.645bca6@posting.google.com...
> Hello Greg,
>
> I tried the first option and added all the imported and included
> schemas that the primary XSD uses into my project.
>
> When I try opening the primary schema I get a prompt "Invalid schema"
> with details:
>
> 1) Cannot resolve schemaLocation attribute. An error occurred at
> file:///C:/../Primary.xsd (15, 10) [this the line 3 where the include
> is]
> 2) Undefined complexType
> 'http://www.openapplications.org/oagis:BusinessObjectDocument' is used
> as a base for complex type extension". An error occurred at
> file:///C:/../Primary.xsd, (26, 26)
>
> And, when I try to validate the schema I get additional errors like
>
> 1) file:///C:/../Primary.xsd : error BEC2009: Node "<Schema>" - Schema
> reference "../Resources/Verbs/Show.xsd" is not a valid reference or
> does not exist in the current project.
>
> What am I doing wrong? Any suggestion to get past this?
>
> Appreciate your help.
> - Nick.
>
> "Greg Forsythe" <greg.forsythe@unisys.com> wrote in message

news:<#FZvvqZwEHA.2728@TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
project[vbcol=seagreen]
resulting[vbcol=seagreen]
the[vbcol=seagreen]
your[vbcol=seagreen]
http://www.gotdotnet.com/Community/...23-fe72f317891a[vbcol=seagreen]
any[vbcol=seagreen]


Nick

2004-11-07, 5:48 pm

I finally figured this out. It seems simple now but I must admit it
was a challenge to get this going The key is to:

1) Add the references into you project via Add Reference option and
the system automatically bring the schemas into your project.
2) Copy only the relevant schemas. No need to bring in all the
reference schemas.
3) Include path needs to be edited for couple of primary schema
.../Resources/Verbs/Show.xsd depending on the location of the
includes.

Thanks.
- Nick.

nickchhabra@yahoo.com (Nick) wrote in message news:<f22e7f03.0411041712.645bca6@posting.google.com>...[vbcol=seagreen]
> Hello Greg,
>
> I tried the first option and added all the imported and included
> schemas that the primary XSD uses into my project.
>
> When I try opening the primary schema I get a prompt "Invalid schema"
> with details:
>
> 1) Cannot resolve schemaLocation attribute. An error occurred at
> file:///C:/../Primary.xsd (15, 10) [this the line 3 where the include
> is]
> 2) Undefined complexType
> 'http://www.openapplications.org/oagis:BusinessObjectDocument' is used
> as a base for complex type extension". An error occurred at
> file:///C:/../Primary.xsd, (26, 26)
>
> And, when I try to validate the schema I get additional errors like
>
> 1) file:///C:/../Primary.xsd : error BEC2009: Node "<Schema>" - Schema
> reference "../Resources/Verbs/Show.xsd" is not a valid reference or
> does not exist in the current project.
>
> What am I doing wrong? Any suggestion to get past this?
>
> Appreciate your help.
> - Nick.
>
> "Greg Forsythe" <greg.forsythe@unisys.com> wrote in message news:<#FZvvqZwEHA.2728@TK2MSFTNGP12.phx.gbl>...
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com