Hi all,
In moving over my workflows from beta1 to beta2, I did the publish as a webservice and all worked fine.
If I have a very simple 'sample' wf as a webservice (i.e. 2 shapes, WS receive + WS Response) it works fine (without persistence)
However when I start to build my more complex ones - the WebService complains that there's no persistence service added.....
Question: What determines whether I need a persistence service or not added to a WS
Is it based on datatype e.g. XmlDocument
I ideally dont want any persistence here (it's being looked after by BizTalk2006)
Many thanks for any light shed
-- further to add --
When I go an add the SqlPersistence (or Custom File Persistence) Service, on the very first call to the WebService, it seems like it's trying to re-load a previously saved Workflow..... Maybe turn off Session Cookies then there's always a new ASPNETSessionID cookie to try and correlate on
Workflow published as a WebService + persistence required in Beta2
AndrewBadera
Solved it!
From what I can tell, it's nothing to do with my Workflows (at this stage), when I'm testing from the browser, the first time is fine - obviously first time we get our SessionID cookie - works.
Second/Third times from the same browser window - fails, talking about needing persistence. (trying to do a lookup in the WFRuntime for the WF Instance)
The interesting thing is -
During development in VS2005 and the DEV webserver (the little guy that pops up in the system tray), it appears to ignore my WebConfig Settings of 'no session state'.
Running under IIS - all cool.
One to note.