|
Home > Archive > BizTalk Server Orchestration > October 2004 > Second SQL Adapter in same solution/orchestration
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 |
Second SQL Adapter in same solution/orchestration
|
|
| Neal Walters 2004-10-02, 8:59 pm |
| I run the SQL Adapter, and it builds a schema called SQLService.xsd.
It also builds an orchestration called Biztalk_Orchestration with two
multi-part messages type that is "internal" so that other schemas can use it.
They are called procedureRequest and procedureResponse. It also builds a
PortType caleld SQLServiceExec.
Okay, all is fine with that.
Now I want to use another SQL Adapter in the same solution. It now builds a
second orchestration called Biztalk-Orchestration_1 and uses identical
PortType names and Multi-part Message Type names. It also builds a second
schema called SQLService_1.xsd which has the same typename as SQLService.
Is this not horrible? What do I do now? Start renaming everything to be
unique - or just don't use the SQL Adapter to build all this stuff in the
first place? Or maybe I should open a separate solution to let the SQL
Adapter build the schema only, then copy that schema over into my real
project. Then i could build the PortTypes and Multi-Part Message Types
myself?
Neal Walters
http://Biztalk-Training.com
| |
| Matt Milner 2004-10-02, 8:59 pm |
| I think you have hit on the possible solutions in your remarks. Rename to
be unique, which is a good idea anyway, or do this in another project and
then copy the schema and port information over manually.
Matt
"Neal Walters" <NealWalters@discussions.microsoft.com> wrote in message
news:652C4AC5-5C4B-47FB-B34A-B94D48AC8DAB@microsoft.com...
>I run the SQL Adapter, and it builds a schema called SQLService.xsd.
> It also builds an orchestration called Biztalk_Orchestration with two
> multi-part messages type that is "internal" so that other schemas can use
> it.
> They are called procedureRequest and procedureResponse. It also builds a
> PortType caleld SQLServiceExec.
>
> Okay, all is fine with that.
>
> Now I want to use another SQL Adapter in the same solution. It now builds
> a
> second orchestration called Biztalk-Orchestration_1 and uses identical
> PortType names and Multi-part Message Type names. It also builds a second
> schema called SQLService_1.xsd which has the same typename as SQLService.
>
> Is this not horrible? What do I do now? Start renaming everything to be
> unique - or just don't use the SQL Adapter to build all this stuff in the
> first place? Or maybe I should open a separate solution to let the SQL
> Adapter build the schema only, then copy that schema over into my real
> project. Then i could build the PortTypes and Multi-Part Message Types
> myself?
>
> Neal Walters
> http://Biztalk-Training.com
|
|
|
|
|