Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a COM+ object which is not stateless (it takes a while to initialize, and maintains large objects in RAM). I want to expose its functionality to other applications / hosts via web service or TCP/IP.
I saw that COM+ Component Services have a built-in capability to create SOAP wrappers and attach them to IIS. However, it looks like it doesn’t use the meta-data from the COM+ objects, and I am not sure whether I have control over the creation and destruction of the objects.
You should totally forget the idea of using the built-in integration capability. It’s simply a bad idea.
Instead, create yourself a WCF service to expose the object. The WCF service can be stateful if necessary, such that multiple calls to the service from the same client will all go to the same instance of your COM+ object (assuming it supports multiple instances).
Is your object transactional? You can expose this through WCF, but not through the built-in “integration” capability.