Possible Duplicate:
StructureMap singleton usage (A class implementing two interface)
I’m currently designing a small system and i’m currently using structureMap as IoC. I just recently got the point of interface segregation…and I’m wondering now.
If I have a certain business object, that will implement say, three interfaces… how should I handle this in the configuration and instatiation of code?
Assuming I have two interfaces in a simple scenario, for a service layer class called EmployeeServiceObject. IGenericEntity and IEmployeeServiceObject.
GenericEntity will provide the CRUD capabilities for the class, and IEmployeeServiceObject will provide resultsets for business queries/operations.
If on a Facade/Service Layer method, I have to use the EmployeeServiceObject class and actually use functionality from both interfaces…how should this be handled?
Initially I thought that the correct thing was to setup the configuration of the IoC to map IEmployeeServiceObject to EmployeeServiceObject, ask the factory for the object, and just cast it to IGenericEntity when i needed to use the CRUD functionality, but i’m not quite sure. It also does not seem right because I’d never be formally stating that the concrete class is actually implementing the interface that was not setup in the ioc container configuration.
and I definitely know that creating two instances of the same concrete class but asking for a different interface…sounds even worse.
How should this be handled?
I didnt find how to close my question as duplicate…but I found exactly how to do what I needed in another stackoverflow question.
What Mark mentioned as the Forward method in Windsor, it also exists in StructureMap…and it appears it would be the right way to do things.
StructureMap singleton usage (A class implementing two interface)