We have a scenario in which we need to create an reference of class B in a class A and Class A in class B. We need to know whether there is any solution to this as we are getting "service unsatisfied" and a sling exception is thrown by the service.
This is a conflict which the system cannot handle itself. But in many cases it is also a sign of a bad application design.
I see 2 options:
1) Make a reference optional and deal with this optionality in the application code. Just make sure that the optional reference is greedy, so it's getting satisfied as soon as the reference target is available.
2) Redesign your services so you don't have this circular dependency anymore. Most likely the creation of a third service C makes sense, which both A and B can depend on.