circular-dependency

I'm running into a issue with CDI Injection into a Weld container in JBoss 7.1.1 I've got the following object model : @Stateless class ServiceEjb { @Inject A a; } class A { @Inject B b; } class B { @Inject A a; } When trying to inject A or B in my stateless class, injection loop and crash with a javax.enterprise.inject.CreationException. I try many thing (scoping, @Singleton on A or B but without success). I don't want to break the code, and those injections makes senses. Any clues will be greatly appreciated. Nick Circular dependency injection is not required by the CDI standard , unless at

Reading the requireJs documentation, in order to fix the Circular Dependencies, is suggested to use exports to create an empty object for the module that is available immediately for reference by other modules. I try this code but it seems to do not work. What is wrong? P.S.: read the comments for seeing the output, especially the B module inside setTimeout call. // A module define([ 'b' ], function (b) { console.log('B:', b); // B, Object var A = { boo: 1 }; return A; }); // B module define([ 'a', 'exports' ], function (a, exports) { console.log('A:', a); // A, undefined (as I was expecting)

I'm working with a project that contains about 30 unique modules. It wasn't designed too well, so it's common that I create circular imports when adding some new functionality to the project. Of course, when I add the circular import, I'm unaware of it. Sometimes it's pretty obvious I've made a circular import when I get an error like AttributeError: 'module' object has no attribute 'attribute' where I clearly defined 'attribute' . But other times, the code doesn't throw exceptions because of the way it's used. So, to my question: Is it possible to programmatically detect when and where a

is this code a example of circular dependency? package expr; import sheet.Sheet public class AdressExpr implements Expr { private Address address; private Sheet sheet; public double value(Sheet sheet) { return sheet.value(address); } } public interface Expr { public double value(Sheet sheet); } public class Adress { // omissions } package sheet; import expr.Address; import expr.Expr; public class Sheet implements SuperSheet { private Map <Address, Expr> map; public double value(Address address) { return map.get(Address).value(this); } } public interface SuperSheet { public double value(Address

Our current project has ran into a circular dependency issue. Our business logic assembly is using classes and static methods from our SharedLibrary assembly. The SharedLibrary contains a whole bunch of helper functions, such as a SQL Reader class, Enumerators, Global Variables, Error Handling, Logging and Validation. The SharedLibrary needs access to the Business objects, but the Business objects need access to SharedLibrary. The old developers solved this obvious code smell by replicating the functionality of the business objects in the shared library (very anti-DRY). I've spent a day now