ba

Asborn,

All excellent points.

I'm going to try some of those revisions and see where it goes.

I'll post the class back to the thread.

Cheers,

I Ferreira

ba

Asborn,

All excellent points.

I'm going to try some of those revisions and see where it goes.

I'll post the class back to the thread.

Cheers,

I Ferreira

ba

I made a copy of the message and then measured the copies length, that
sorted out the end of stream problem.

The simplification also worked well.


The issue that I cant figure out is how to let it grow to accomodate much
bigger file sizes, without setting a ridicilous buffer. I guess I answered
my own question writing that, I guess it might need to be a context property
in the pipeline, that way its not in the adapter at all, its just a
paramater that gets attached to the message.

That would require a pipeline component that measures the message before
giving it over to the adapter.

Do you, or anyone know another place in BizTalk that the message size in
byte[] can be retrieved within BizTalk with less work?