Has anyone run into any issues with using Castle w/ MS ServiceLocator and then later invoking the workflowInvoker or WorkflowApplication (workflow foundation)?
Here's the steps that cause problems... 1. Register services through Castle Windsor (as singleton) 2. Retrieve a service through the ServiceLocator API ( http://commonservicelocator.codeplex.com/ ) 3. Execute the service I retrieved. 4. This service then executes an activity/workflow using the WorkflowInvoker. 5. If I try and retrieve the service through the ServiceLocator again then it fails saying it's unable to find the component. The only workaround I've found for this is to run the workflow in a separate app domain and call it via a MarshalByRef proxy. When I try and debug this after the WorkflowInvoker runs I can see the services in ServiceLocator are gone. Does WF interact with ServiceLocator during cleanup? Is this a Workflow Issue, ServiceLocator issue, or Castle Windsor issue? Is there a direction you could point me in on this issue? -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/castle-project-users/-/Ja6umBVddy8J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
