Hi,
I am having problems working with the contentStream within the pipe after using ftp to put an edi (x124010) file to the reverse invoke server. I changed my mime.types (on the reverse invoke server) to assocaite the file extension along with the content type (application/EDIstream).
application/EDIstream x12 edi
I am migrating from 6.01 to 6.5. The same code worked fine in 6.01.
When I do a trace pipe I see the following:
0 contentStream {wm.server.net.FTPInputStream} = ‘wm.server.net.FTPInputStream@19eb5f6’
It appears something is getting in there. BTW this is the same logged information if trace is execute on 6.01 (working version)
My flow serivce(residing on the reverse invoke)
performs a stream to byte then a byte to string.
For some reason the contentStream oject node, when mapped to the stream to byte value throw an exception.
Any help would be greatly appreciated.
Thanks.