Rana,
When you set up the file polling port, there is an option to set the content type there. If you set the content type to text/xml, then it will invoke the xml content handler. In this case, the receiving flow will need a node object to receive the data.
If you decide to use the default, it requires a java input stream named ffdata.
You can do a real simple test to see if this works by creating a flow with the input of ffdata as an object.
Then use pub.io:streamToBytes to convert it to bytes. Then, use pub.string:bytesToString to convert to string.
Map this string to the message input to pub.flow:debugLog and it should write the entire message to the server log as a test.
I used this procedure to determine initially how the file polling mechanism worked. It is mainly used for flat files. The reason the content type input box is available is in case you decide to create, register and use your own custom content handler.
Hope this helps.
Ray
#Integration-Server-and-ESB#webMethods#Flow-and-Java-services