Workflow Foundation Architecture - how to write wrapper for workflow?


i want use workflow foundation. looking implementing following requirements:

 

* workflow foundation implementation hidden/encapsulated client asp.net user interface layer code

* dont want write own code hosting workflow runtime

* expose workflow interactions with asp.net user interface layer as webservice methods - reason being asp.net user interface layer bunch of independent applications want make use of common workflow

 

in have figured out, in order avoid writing own code hosting workflow runtime, have 2 options - either publish workflow wcf service or asp.net webservice in iis - iis acts workflow runtime host - far cool.

 

now, want hide workflow implementation asp.net client user interface layer, have add wrapper methods workflow webservice methods - such dont want asp.net ui layer code pass , receive workflow instance ids. when publish workflow wcf or asp.net webservice, have no control on code being generated! how can wrap workflow asp.net user interface layer?

 

i write webservice application consumes published workflow foundation component's webservice. design feels wierd - asp.net calling webservice - webservice calling workflow webservice...

usually use workflow/bpm products remembers state of workflow/process, etc.,

 

by way of not using hosting service, launching new workflow instance every time when service called web application (it doesnt matter if hosted wcf or asp.net webservice).

 

i recommend create hosting service, primary responsibility need.  can let me know reason why wouldnt want use hosting application?

 

{ gaja; }

http://gajakannan.com/netarch.aspx



Architecture  >  Architecture General



Comments

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

BizTalk Server 2013 Azure VM Log Shipping and HA for hosts

How to Share webservice object to all user