AbeSeb

I have a custom service that I would like to add to the sharepoint hosted workflow runtime.

I don't see a corresponding configuration section in the web.config file of the sharepoint website. Does anyone know how I could do this

Thanks!


Re: Windows Workflow Foundation Adding a custom service to sharepoint hosted workflow runtime

Tom Lake - MSFT

Since your question is specific to SharePoint¡¯s implementation of Windows Workflow Foundation you should post your question to the SharePoint - Workflow forum.






Re: Windows Workflow Foundation Adding a custom service to sharepoint hosted workflow runtime

Vignesh Kannappan - MSFT

Hi Abe - The workflow functionality in Microsoft Windows SharePoint Services 3.0 is built on the Microsoft Windows Workflow Foundation (3.0), and so the standard way of adding services to the web.config in WF should apply.

Example (adding ManualWorkflowSchedulerService):

<configSections>

<section name="WorkflowRuntime" type="System.Workflow.Runtime.Configuration.WorkflowRuntimeSection, System.Workflow.Runtime, Version=3.0.00000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

</configSections>

<WorkflowRuntime>

<Services>

<add type="System.Workflow.Runtime.Hosting.ManualWorkflowSchedulerService, System.Workflow.Runtime, Version=3.0.00000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

</Services>

</WorkflowRuntime>

This may be helpful as well: http://msdn2.microsoft.com/en-us/library/ms195750.aspx

HTH,

Vignesh






Re: Windows Workflow Foundation Adding a custom service to sharepoint hosted workflow runtime

Serge Luca

Vignesh,

If you want the workflowRuntime to read the "WorkflowRuntime" Configsection of your Web.config, you have to pass "WorkflowRuntime" as a parameter, it's not automatic

...new System.Workflow.Runtime.WorkflowRuntime("WorkflowRuntime") ;

So it seems that (saddly) we (the users) cannot load WF services in sharepoint...despite the great architecture of WF.

Serge






Re: Windows Workflow Foundation Adding a custom service to sharepoint hosted workflow runtime

Cory@luckyfunk

Re: "So it seems that (saddly) we (the users) cannot load WF services in sharepoint...despite the great architecture of WF"

Can someone please validate this - ahem, product group... - this question (the root of it, anyway) is posted a bunch on the "directed to" Sharepoint developer forums with no response. When this question is posed in this group, the answer is always the same: "Yeah, just add the ExternalDataExchangeService to the Runtime, register your service, and run off happily and merrily."

Except, you can't do this the consistently mentioned way - you can't grab the runtime in Sharepoint (instantiation and initialization starts waaaay too early to get included in the party) and it doesn't seem to work when grabbing the ExternalDataExchangeService from the ActivityContext and jamming your service onto it. This lets CallExternalMethod activities work fine - just not HandleExternalEvent... Unfortunately, in a world of state workflows, you really need events.

So, please - can the MSFT/Prod group validate the quote above Can we not sucessfully (i.e. working) register custom services against the ExternalDataExchangeService when MOSS is the WF host If we can, care to share how If not, can you please explain the underlying fudamental architectural design of ITaskService, etc

Much appreciated,

Cory






Re: Windows Workflow Foundation Adding a custom service to sharepoint hosted workflow runtime

Tom Lake - MSFT

The restriction of not being able to add a custom service to the workflow runtime when you have you workflow hosted in SharePoint 2007 is because SharePoint has made this restriction. They are just an implementation of Windows Workflow Foundation and have chosen not to allow this.






Re: Windows Workflow Foundation Adding a custom service to sharepoint hosted workflow runtime

Cory@luckyfunk

Tom,

Thank you very much for your quick reply. It would be extraordinarily helpful if this restriction is added to the WSS/MOSS SDK documentation. I have seen many posts asking this question, albeit in round-about manner, with no answers.

While I can appreciate the necessity to restrict certain aspects of functionality, whether it's due to time constraints, scope, functional behavior issues, persistence compatability, etc, I do think that participation in the host eventing model is a necessity in the future.

I don't believe that, although wf in moss is doc centric, that all events should be forced to derive from task/doc based events.

Having assumed this was the answer, I'm headed down the path of using workflow modification entries to deal with eventing in state workflows.

Again, thanks for your quick reply.

Cory