I have a soap-msg coming in thru document literal service. now when i run the called wrapper service thru a wM web service connector it all runs fine. Also if I do a savePipeline/restorePipeline (when called from the external application)and receive the data and run it from there all the results look good. The problem comes when the external app call this directly it gets an internal application error which I am throwing thru my serivice.
The problem really becomes worse when i try to debug it thru the savePipeline.
This is how my service looks (i/p is soapRequestData - String)
map(maps the soapRequestData to a tempsoapdata variable)
savePipeline(just to see if the data is mapped to this tempsoapdata var)
Do take into consideration that when the service is called directly i have the savePipeline on and while tracing it I have the restorePipeline on.
Now when I come to the last restorePipeline I would expect to see my soapRequestData coming in as request being mapped to the tempsoapdata var. But this does not happen (I do not see the tempsoapdata though I can see the input as a string variable of soapRequestData)and hence the external application is seeing the error.
The map in the 3rd step is just a simple map from the input soapRequestData var to the tempsoapdata var. Does anyone have any idea as to why webM is doing this (not mapping this value to this temp var)? I am assuming this is the problen and hence my next steps in the flow dont map anythign from the input request soadRequestData. Now mind you when I trace this service with the first resorePipeline it works right till the end. Hows that possible? Also tried something different. If I have a savePipeline and restorePipeline both on the external app receives a success. All is fine. but then do I really need to do a savePipeline and restorePipeline. Isnt that a big overhead on performance?
Thanks in advance