BizTalk Server General - Deployment exception on @namespace parameter

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server General > May 2005 > Deployment exception on @namespace parameter





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 Deployment exception on @namespace parameter
shawnk

2005-05-24, 8:19 am

I have an assembly that builds just fine. When I try to deploy I get the
following error;

[Microsoft.BizTalk.Deployment.DeploymentException]
[System.Data.SqlClient.SqlException]
Procedure 'dpl_SaveSchemaProperty'
expects parameter '@NameSpace', which was not supplied.

[System.Data.SqlClient.SqlException]
Procedure 'dpl_SaveSchemaProperty'
expects parameter '@NameSpace', which was not supplied.

The assembly is a simple message library. The XML and .NET namespaces have
everything specified as far as know.

I try to look this up in the documentation but have not yet found it.

Thanks ahead of time to any responses.

shawnk

PS. I am working on some naming conventions for the message library. So my
namespaces are being changed but should be correct.
shawnk

2005-05-24, 6:01 pm

Found the 'bug' in Biztalk.

I think that if an assembly builds it should be deployable.
Any 'bugs' in the code that prevent deployment should be caught at compile
time (in Biztalk).

You can find this 'bug' in Biztalk by inserting the following 'bug' in the
message XML schema code.
Insert a 'bug' in the XSD message schema by switching the capitalization of
the first letter of the property namespace prefix
This is a 'code synchronization' bug (for the prefix)

In the example

If the Prefix (in XSD message schema) is changed by one character we get the
following.

The correct XML code should be (capitalization matches)

xmlns:Ppr_pfx="http://Dev_sch_svr/bof_nsp"
<b:namespace prefix="Ppr_pfx" uri="http://Dev_sch_svr/bof_nsp"
location=".\BTB_Activity_bzt_msg_typ.xsd" />

The 'bug' in the XML code is the mis-match of the first letter in the
prefix (capital vs non-capital form)

xmlns:Ppr_pfx="http://Dev_sch_svr/bof_nsp"
<b:namespace prefix="ppr_pfx" uri="http://Dev_sch_svr/bof_nsp"
location=".\BTB_Activity_bzt_msg_typ.xsd" />

We get the deployment error;

[Microsoft.BizTalk.Deployment.DeploymentException]
[System.Data.SqlClient.SqlException]
Procedure 'dpl_SaveSchemaProperty'
expects parameter '@NameSpace', which was not supplied.

[System.Data.SqlClient.SqlException]
Procedure 'dpl_SaveSchemaProperty'
expects parameter '@NameSpace', which was not supplied.

This 'bug' in the message schema got by the compile but failed in the
deployment
When the 'bug' is switched around

xmlns:ppr_pfx="http://Dev_sch_svr/bof_nsp"
<b:namespace prefix="Ppr_pfx" uri="http://Dev_sch_svr/bof_nsp"
location=".\BTB_Activity_bzt_msg_typ.xsd" />

We get the compile time error;


H:\Book\BZT_book_01\Chap_00_Message_libr
ary\BTB_Message_Library_bzts\BTB_First_m
sg_lib\BTB_Activity_bzt_msg.xsd
Node "<Schema>" -
The following promoted property 'Ppr_pfx:Activity_msg_typ' does not
exist in property schema.

The fault is really in my XML code but it would be nice if Biztalk flags it
It's a very minor bug (in Biztalk) but I thought I would post it.



"shawnk" wrote:

> I have an assembly that builds just fine. When I try to deploy I get the
> following error;
>
> [Microsoft.BizTalk.Deployment.DeploymentException]
> [System.Data.SqlClient.SqlException]
> Procedure 'dpl_SaveSchemaProperty'
> expects parameter '@NameSpace', which was not supplied.
>
> [System.Data.SqlClient.SqlException]
> Procedure 'dpl_SaveSchemaProperty'
> expects parameter '@NameSpace', which was not supplied.
>
> The assembly is a simple message library. The XML and .NET namespaces have
> everything specified as far as know.
>
> I try to look this up in the documentation but have not yet found it.
>
> Thanks ahead of time to any responses.
>
> shawnk
>
> PS. I am working on some naming conventions for the message library. So my
> namespaces are being changed but should be correct.

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com