I have a flat file that is converted into  message1, works fine.
Then I have a class library which brakes out each row in the message1 into a
 single message2.

Then Message2, the single row, is passed through the rules engine. A flag is
 set in the rules engine whether message2 is a acceptable item.

This is where I have the problem.

I try to build Message3 which is a list of accepted items and Message4 which
 is a list of invalid items in a class library.

Everything works in debug I can see all the items in Message 3 and 4,  BUT t
hey do NOT persist to a port, file, or WebService.

What could I be doing wrong?

Thanks
Dan

[ Post a follow-up to this message ]

When the message fail to persist, what shows up in HAT?  Do we have any
message instance there?

Sincerely,


Everett Yang
DSI - Microsoft BizTalk Server

This posting is provided “AS IS” with no warranties, and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn

[ Post a follow-up to this message ]

There are no errors or suspends

The whole orchestration goes through with no problems.

In the final send which is attached to a file port, the xml is populated in 
the message, but the file adapter does not see it.

so I get
<ns0:Root xmlns:ns0="http://ADEE.PassedThroughDiamonds"><Approved>true
</Approved></ns0:Root>

not
<ns0:Root xmlns:ns0="http://ADEE.PassedThroughDiamonds"><Approved>true</Approved><Row><Vend
orID>10013</VendorID><Shape>AS</Shape><Size>3.81</Size><Color>J</Color><Clarity>VS2</Clarit
y><Price>4270</Price><Certification>EGL</Certification><Depth>68.1</Depth
><Table>71</Table><Girdle>MED</Girdle><Culet>N</Culet><Polish>VG</Polish><Symmetry>G
V</Symmetry><Flourescence>N</Flourescence><Measurements>8.85X8.72X5.94</Measurements
><CertNumber></CertNumber><StockNumber>B4559</StockNumber><Cut></Cut><Status>true</S
tat
us><Reason></Reason><Override>false</Override></Row><Row><VendorID>10013</Ve
ndorID><Shape>RA</Shape><Size>2.04</Size><Color>F</Color><Clarity>IF</Clarit
y><Price>8445</Price><Certification>EGL</Certification><Depth>65.3</Depth><T
able>75</Table><Girdle>THIN
</Girdle><Culet>N</Culet><Polish>VG</Polish><Symmetry>VG</Symmetry><Flouresc
ence>N</Flourescence><Measurements>7.20X6.98X4.56</Measurements><CertNumber>
</CertNumber><StockNumber>B4561</StockNumber><Cut>Good</Cut><Status>true</St
atus><Reason></Reason><Over
ride>false</Override></Row></ns0:Root>

which is what I see in the send orbject of the orchestration before the port
 call.

Any help here?

Thanks

[ Post a follow-up to this message ]

We can try stopping the send port and have document show up in HAT.  Then
look at the message instance to see what it looks like as it leaves
Orchestration.

What type of pipeline are we using in the send port?


Sincerely,


Everett Yang
DSI - Microsoft BizTalk Server

This posting is provided “AS IS” with no warranties, and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn

[ Post a follow-up to this message ]

Ok finally got a message in Hat and here is what I found.

This Assembler cannot retrieve document specification by using this type: "h
ttp://Diamond_Import.RejectedDiamonds#Root".

I dont get it, the message is assembled correctly.

NameSpace?

Dan

[ Post a follow-up to this message ]

Yes, double check the target namespace.

Sincerely,


Everett Yang
DSI - Microsoft BizTalk Server

This posting is provided “AS IS” with no warranties, and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn

[ Post a follow-up to this message ]

Dan,

can you check if you have not deployed two schema's with the same target
namespace and roottag name. That may cause troubles similar like this one...

Regards,
Christof

"Dan" <anonymous@discussions.microsoft.com> wrote in message
news:1ABC1746-2794-4C6F-899A-ECA81866B18E@microsoft.com...
>
> Ok finally got a message in Hat and here is what I found.
>
> This Assembler cannot retrieve document specification by using this type:
"http://Diamond_Import.RejectedDiamonds#Root".
>
> I dont get it, the message is assembled correctly.
>
> NameSpace?
>
> Dan

[ Post a follow-up to this message ]

I got it.

I had to create tempary messages to populate the list. Then map those temps 
to a well defined message of the same type.

Then it persisted.  Different, but it works.

Thanks to everyone.
Dan

[ Post a follow-up to this message ]