Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

BizTalk 2010 Recipes : Creating Schema Namespaces

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
3/25/2011 10:09:13 PM

1. Problem

You need to create two schemas that have the same name for the root node.

2. Solution

BizTalk Server uses a combination of namespaces and root nodes to resolve schema references. Therefore, it is possible to have two schemas with the same root node as long as their namespace designation is different. By default, the BizTalk Editor will set the namespace of a schema to http://[solution].[schema], where solution refers to the name of the solution file and schema refers to the name of the schema file. This default namespace designation may be modified as follows:

  1. Open the project that contains the schema.

  2. Double-click the schema to open it.

  3. Select the <Schema> node.

  4. Right-click and select Properties.

  5. Modify the Target Namespace property as desired.

When you modify the Target Namespace property, BizTalk Server will automatically modify the Default Namespace (element name xmlns) of the schema to match the Target Namespace. Once the two schemas with the same root node have different namespace designations, they may be used without any conflicts.

3. How It Works

Namespaces are used to allow elements and attributes from different schemas to share names. For example, two schemas may have an element named FirstName. If the schemas did not have different namespaces, BizTalk Server would not know which FirstName you were referencing. In addition to adopting naming standards and conventions for all BizTalk artifacts, you should adopt a standard for namespaces in schemas. An example of a standard is as follows:

http://[Company Name].[Project].BizTalk.Schemas.[Schema].[Version]

where Company Name is your company name, Project is the name of the project, Schema is the name of the schema, and Version is the version number of the schema.

NOTE

"EDI" should not be used in the namespace of any project that uses the BizTalk EDI engine. During runtime, you may run into conflicts with this that will not allow your components to function as expected.

Other -----------------
- BizTalk 2010 Recipes : Creating a Schema Based on an Existing XML Document
- BizTalk 2010 Recipes : Creating Simple Document Schemas
- Restoring Windows Server 2008 (part 2) - Restoring Individual Components
- Restoring Windows Server 2008 (part 1) - Full Server Recovery
- Installing and Configuring Office Web Apps for SharePoint 2010 (part 2)
- Installing and Configuring Office Web Apps for SharePoint 2010 (part 1)
- Office Web Apps Integration with SharePoint 2010 : Planning for Office Web Apps Use
- Windows Server 2008 R2 : Planning Domain Group Policy Objects (part 2)
- Windows Server 2008 R2 : Planning Domain Group Policy Objects (part 1) - Policies and Preferences
- Windows Server 2008 R2 : Planning Workgroup and Standalone Local Group Policy Configuration
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server