Is there a simple way to get messages that don't contain namespaces through
an orchestration?  When I drop a message in a receive port I get a "No
Subscribers Found" suspension.  If I append the message to contain a
namespace it flows through.

The messages coming in do not have a namespace and the messages being sent
cannot have a namespace (they are being processing by a very old system that
I can't touch).  If I were to use inbound/outbound maps containing identical
schemas except for the namespace would that work?  Or is there a "prettier"
solution?  Thanks.

[ Post a follow-up to this message ]

I ended up using maps on the receive and send ports that mapped identical
schemas and only added/removed the namespace and that seemed to work.

Todd

"Todd Bagley" <tbagley@heymileskimball.com> wrote in message
news:uParGcAgGHA.356@TK2MSFTNGP02.phx.gbl...
> Is there a simple way to get messages that don't contain namespaces
> through an orchestration?  When I drop a message in a receive port I get a
> "No Subscribers Found" suspension.  If I append the message to contain a
> namespace it flows through.
>
> The messages coming in do not have a namespace and the messages being sent
> cannot have a namespace (they are being processing by a very old system
> that I can't touch).  If I were to use inbound/outbound maps containing
> identical schemas except for the namespace would that work?  Or is there a
> "prettier" solution?  Thanks.
>

[ Post a follow-up to this message ]

The other option is to setup custom pipelines and have the XMLDissasembler
point to the exact schema it needs to match up with.

--
Todd Sussman
todd.sussman@neudesic.com
Member of the Microsoft BPI Virtual TS Team

"Todd Bagley" <tbagley@heymileskimball.com> wrote in message
news:etv92eCgGHA.4464@TK2MSFTNGP04.phx.gbl...
> I ended up using maps on the receive and send ports that mapped identical
> schemas and only added/removed the namespace and that seemed to work.
>
> Todd
>
> "Todd Bagley" <tbagley@heymileskimball.com> wrote in message
> news:uParGcAgGHA.356@TK2MSFTNGP02.phx.gbl... 
a[vbcol=seagreen] 
sent[vbcol=seagreen] 
a[vbcol=seagreen] 
>
>

[ Post a follow-up to this message ]

Take the namespace off the schema root and it should work.  The only
reason BT is expecting a namespace is because its set on the root
(automatically when you create the schema.

[ Post a follow-up to this message ]