Thanks for responding. I was just curious for comparison sake with ColdSpring. I guess I haven't figured out when to use CS over LW, or vice-versa. Of course, for AOP I'd have no choice but CS. But for the things they do have in common... ? Thanks.
----- Original Message ---- From: Paul Marcotte <pmarco...@gmail.com> To: lightwireFramework@googlegroups.com Sent: Thursday, February 7, 2008 3:43:58 PM Subject: {LightwireFramework} Re: Handling circular dependencies.
Hey LT,
You can use "mixin" injection in Lightwire rather than "setter" injection. In ColdSpring the way around a circular dependency is to use a property tag instead of a constructor-arg. Lightwire has both constructor and setter injection and the aforementioned mixin injection.
I caught your post on the ColdSpring list as well, so I'm curious about you object dependencies. Do you mind sharing some information about the dependent objects?
Paul
On Feb 7, 2008 3:31 PM, LT <lagos.t...@gmail.com> wrote:
Hi,
I was wondering if Lightwire handles circular dependencies in a different way from ColdSpring. Thanks.
My pleasure. To give you a bit more information, you can use a superset of ColdSpring xml definitions with Lightwire. The difference is that since Lightwire supports mixin injection, there is a <mixin/> tag. What mixin give you is the ability to reference the dependency as variables.MyMixinwithout having to add a specific setter for "MyMixin".
But that's where it stops. You won't find AOP, Autowiring, or remote proxies with LightWire.
Regarding the circular dependency, I just wanted to mention that many of the community leaders like Sean Corfield and Brian Kotek suggest that having a 1:1 ration of Services to business objects can cause issues like circular dependencies. Quick example. Say you have a ProductService and and CategoryService for your online catalog. If you have a circular dependency between the two, you might consider rolling them up into a CatalogService that provides API methods Products and Categories. This is a application design paradigm that I'm currently working toward.
So, uh, that's my 2 cents...
Cheers,
Paul
On Feb 9, 2008 12:33 PM, lagos.tout <lagos.t...@gmail.com> wrote:
> Thanks for responding. > I was just curious for comparison sake with ColdSpring. > I guess I haven't figured out when to use CS over LW, or vice-versa. > Of course, for AOP I'd have no choice but CS. But for the things they do > have in common... ? > Thanks.
> LT
> ----- Original Message ---- > From: Paul Marcotte <pmarco...@gmail.com> > To: lightwireFramework@googlegroups.com > Sent: Thursday, February 7, 2008 3:43:58 PM > Subject: {LightwireFramework} Re: Handling circular dependencies.
> Hey LT,
> You can use "mixin" injection in Lightwire rather than "setter" > injection. In ColdSpring the way around a circular dependency is to use a > property tag instead of a constructor-arg. Lightwire has both constructor > and setter injection and the aforementioned mixin injection.
> I caught your post on the ColdSpring list as well, so I'm curious about > you object dependencies. Do you mind sharing some information about the > dependent objects?
> Paul
> On Feb 7, 2008 3:31 PM, LT <lagos.t...@gmail.com> wrote:
> > Hi,
> > I was wondering if Lightwire handles circular dependencies in a > > different way from ColdSpring. > > Thanks.
Also, LW was designed for DI into transients as well as singletons. You *can* do that with CS, but it is not recommended. The recommended solution in CS is to create a factory thatıs bean aware for the transient DI (say you have a user that requires a UserDAO).
Oh, and if you want to write a programmatic config file (instead of XML), that can be done in LW but in CS youıd have to write a script to gen your xml and then pass that in.
I just find LW more elegant for my use cases and as I really need AOP or other such features, I believe I can add them to LW while still keeping it really tight.
Best Wishes, Peter
On 2/9/08 9:47 PM, "Paul Marcotte" <pmarco...@gmail.com> wrote:
> My pleasure. To give you a bit more information, you can use a superset of > ColdSpring xml definitions with Lightwire. The difference is that since > Lightwire supports mixin injection, there is a <mixin/> tag. What mixin give > you is the ability to reference the dependency as variables.MyMixin without > having to add a specific setter for "MyMixin".
> But that's where it stops. You won't find AOP, Autowiring, or remote proxies > with LightWire.
> Regarding the circular dependency, I just wanted to mention that many of the > community leaders like Sean Corfield and Brian Kotek suggest that having a 1:1 > ration of Services to business objects can cause issues like circular > dependencies. Quick example. Say you have a ProductService and and > CategoryService for your online catalog. If you have a circular dependency > between the two, you might consider rolling them up into a CatalogService that > provides API methods Products and Categories. This is a application design > paradigm that I'm currently working toward.
> So, uh, that's my 2 cents...
> Cheers,
> Paul
> On Feb 9, 2008 12:33 PM, lagos.tout <lagos.t...@gmail.com> wrote: >> Hi, Paul.
>> Thanks for responding. >> I was just curious for comparison sake with ColdSpring. >> I guess I haven't figured out when to use CS over LW, or vice-versa. >> Of course, for AOP I'd have no choice but CS. But for the things they do >> have in common... ? >> Thanks.
>> LT
>> ----- Original Message ---- >> From: Paul Marcotte <pmarco...@gmail.com> >> To: lightwireFramework@googlegroups.com >> Sent: Thursday, February 7, 2008 3:43:58 PM >> Subject: {LightwireFramework} Re: Handling circular dependencies.
>> Hey LT,
>> You can use "mixin" injection in Lightwire rather than "setter" injection. >> In ColdSpring the way around a circular dependency is to use a property tag >> instead of a constructor-arg. Lightwire has both constructor and setter >> injection and the aforementioned mixin injection.
>> I caught your post on the ColdSpring list as well, so I'm curious about you >> object dependencies. Do you mind sharing some information about the >> dependent objects?
>> Paul
>> On Feb 7, 2008 3:31 PM, LT <lagos.t...@gmail.com> wrote:
>>> Hi,
>>> I was wondering if Lightwire handles circular dependencies in a >>> different way from ColdSpring. >>> Thanks.
Thanks, Peter. Would you mind explaining a bit more what you mean by "The recommended solution in CS is to create a factory thats bean aware for the transient DI (say you have a user that requires a UserDAO)" Also, why is injection into transients not recommended with CS? LT
----- Original Message ---- From: Peter Bell <systemsfo...@gmail.com> To: lightwireFramework@googlegroups.com Sent: Sunday, February 10, 2008 9:31:17 AM Subject: {LightwireFramework} Re: Handling circular dependencies.
Also, LW was designed for DI into transients as well as singletons. You *can* do that with CS, but it is not recommended. The recommended solution in CS is to create a factory thats bean aware for the transient DI (say you have a user that requires a UserDAO).
Oh, and if you want to write a programmatic config file (instead of XML), that can be done in LW but in CS youd have to write a script to gen your xml and then pass that in.
I just find LW more elegant for my use cases and as I really need AOP or other such features, I believe I can add them to LW while still keeping it really tight.
Best Wishes, Peter
On 2/9/08 9:47 PM, "Paul Marcotte" <pmarco...@gmail.com> wrote:
Hi LT,
My pleasure. To give you a bit more information, you can use a superset of ColdSpring xml definitions with Lightwire. The difference is that since Lightwire supports mixin injection, there is a <mixin/> tag. What mixin give you is the ability to reference the dependency as variables.MyMixin without having to add a specific setter for "MyMixin".
But that's where it stops. You won't find AOP, Autowiring, or remote proxies with LightWire.
Regarding the circular dependency, I just wanted to mention that many of the community leaders like Sean Corfield and Brian Kotek suggest that having a 1:1 ration of Services to business objects can cause issues like circular dependencies. Quick example. Say you have a ProductService and and CategoryService for your online catalog. If you have a circular dependency between the two, you might consider rolling them up into a CatalogService that provides API methods Products and Categories. This is a application design paradigm that I'm currently working toward.
So, uh, that's my 2 cents...
Cheers,
Paul
On Feb 9, 2008 12:33 PM, lagos.tout <lagos.t...@gmail.com> wrote:
Hi, Paul.
Thanks for responding. I was just curious for comparison sake with ColdSpring. I guess I haven't figured out when to use CS over LW, or vice-versa. Of course, for AOP I'd have no choice but CS. But for the things they do have in common... ? Thanks.
LT
----- Original Message ---- From: Paul Marcotte <pmarco...@gmail.com> To: lightwireFramework@googlegroups.com Sent: Thursday, February 7, 2008 3:43:58 PM Subject: {LightwireFramework} Re: Handling circular dependencies.
Hey LT,
You can use "mixin" injection in Lightwire rather than "setter" injection. In ColdSpring the way around a circular dependency is to use a property tag instead of a constructor-arg. Lightwire has both constructor and setter injection and the aforementioned mixin injection.
I caught your post on the ColdSpring list as well, so I'm curious about you object dependencies. Do you mind sharing some information about the dependent objects?
Paul
On Feb 7, 2008 3:31 PM, LT <lagos.t...@gmail.com> wrote:
Hi,
I was wondering if Lightwire handles circular dependencies in a different way from ColdSpring. Thanks.
If you want to DI into transients using CS, just email to the ColdSpring list, explain what you want to do and ask whether you should use CS to inject into the transients using ³singleton=²false²² and if not, what approach theyıd recommend. Please donıt mention me or LightWire seems to piss them off over there :->
Best Wishes, Peter
On 2/10/08 1:38 PM, "lagos.tout" <lagos.t...@gmail.com> wrote:
> Thanks, Peter. > Would you mind explaining a bit more what you mean by "The recommended > solution in CS is to create a factory thatıs bean aware for the transient DI > (say you have a user that requires a UserDAO)" Also, why is injection into > transients not recommended with CS? > LT
> ----- Original Message ---- > From: Peter Bell <systemsfo...@gmail.com> > To: lightwireFramework@googlegroups.com > Sent: Sunday, February 10, 2008 9:31:17 AM > Subject: {LightwireFramework} Re: Handling circular dependencies.
> Also, LW was designed for DI into transients as well as singletons. You *can* > do that with CS, but it is not recommended. The recommended solution in CS is > to create a factory thatıs bean aware for the transient DI (say you have a > user that requires a UserDAO).
> Oh, and if you want to write a programmatic config file (instead of XML), that > can be done in LW but in CS youıd have to write a script to gen your xml and > then pass that in.
> I just find LW more elegant for my use cases and as I really need AOP or other > such features, I believe I can add them to LW while still keeping it really > tight.
> Best Wishes, > Peter
> On 2/9/08 9:47 PM, "Paul Marcotte" <pmarco...@gmail.com> wrote:
>> Hi LT,
>> My pleasure. To give you a bit more information, you can use a superset of >> ColdSpring xml definitions with Lightwire. The difference is that since >> Lightwire supports mixin injection, there is a <mixin/> tag. What mixin give >> you is the ability to reference the dependency as variables.MyMixin without >> having to add a specific setter for "MyMixin".
>> But that's where it stops. You won't find AOP, Autowiring, or remote >> proxies with LightWire.
>> Regarding the circular dependency, I just wanted to mention that many of the >> community leaders like Sean Corfield and Brian Kotek suggest that having a >> 1:1 ration of Services to business objects can cause issues like circular >> dependencies. Quick example. Say you have a ProductService and and >> CategoryService for your online catalog. If you have a circular dependency >> between the two, you might consider rolling them up into a CatalogService >> that provides API methods Products and Categories. This is a application >> design paradigm that I'm currently working toward.
>> So, uh, that's my 2 cents...
>> Cheers,
>> Paul
>> On Feb 9, 2008 12:33 PM, lagos.tout <lagos.t...@gmail.com> wrote: >>> Hi, Paul.
>>> Thanks for responding. >>> I was just curious for comparison sake with ColdSpring. >>> I guess I haven't figured out when to use CS over LW, or vice-versa. >>> Of course, for AOP I'd have no choice but CS. But for the things they do >>> have in common... ? >>> Thanks.
>>> LT
>>> ----- Original Message ---- >>> From: Paul Marcotte <pmarco...@gmail.com> >>> To: lightwireFramework@googlegroups.com >>> Sent: Thursday, February 7, 2008 3:43:58 PM >>> Subject: {LightwireFramework} Re: Handling circular dependencies.
>>> Hey LT,
>>> You can use "mixin" injection in Lightwire rather than "setter" injection. >>> In ColdSpring the way around a circular dependency is to use a property tag >>> instead of a constructor-arg. Lightwire has both constructor and setter >>> injection and the aforementioned mixin injection.
>>> I caught your post on the ColdSpring list as well, so I'm curious about you >>> object dependencies. Do you mind sharing some information about the >>> dependent objects?
>>> Paul
>>> On Feb 7, 2008 3:31 PM, LT <lagos.t...@gmail.com> wrote:
>>>> Hi,
>>>> I was wondering if Lightwire handles circular dependencies in a >>>> different way from ColdSpring. >>>> Thanks.
----- Original Message ---- From: Peter Bell <systemsfo...@gmail.com> To: lightwireFramework@googlegroups.com Sent: Sunday, February 10, 2008 10:54:28 AM Subject: {LightwireFramework} Re: Handling circular dependencies.
If you want to DI into transients using CS, just email to the ColdSpring list, explain what you want to do and ask whether you should use CS to inject into the transients using singleton=false and if not, what approach theyd recommend. Please dont mention me or LightWire seems to piss them off over there :->
Best Wishes, Peter
On 2/10/08 1:38 PM, "lagos.tout" <lagos.t...@gmail.com> wrote:
Thanks, Peter. Would you mind explaining a bit more what you mean by "The recommended solution in CS is to create a factory thats bean aware for the transient DI (say you have a user that requires a UserDAO)" Also, why is injection into transients not recommended with CS? LT
----- Original Message ---- From: Peter Bell <systemsfo...@gmail.com> To: lightwireFramework@googlegroups.com Sent: Sunday, February 10, 2008 9:31:17 AM Subject: {LightwireFramework} Re: Handling circular dependencies.
Also, LW was designed for DI into transients as well as singletons. You *can* do that with CS, but it is not recommended. The recommended solution in CS is to create a factory thats bean aware for the transient DI (say you have a user that requires a UserDAO).
Oh, and if you want to write a programmatic config file (instead of XML), that can be done in LW but in CS youd have to write a script to gen your xml and then pass that in.
I just find LW more elegant for my use cases and as I really need AOP or other such features, I believe I can add them to LW while still keeping it really tight.
Best Wishes, Peter
On 2/9/08 9:47 PM, "Paul Marcotte" <pmarco...@gmail.com> wrote:
Hi LT,
My pleasure. To give you a bit more information, you can use a superset of ColdSpring xml definitions with Lightwire. The difference is that since Lightwire supports mixin injection, there is a <mixin/> tag. What mixin give you is the ability to reference the dependency as variables.MyMixin without having to add a specific setter for "MyMixin".
But that's where it stops. You won't find AOP, Autowiring, or remote proxies with LightWire.
Regarding the circular dependency, I just wanted to mention that many of the community leaders like Sean Corfield and Brian Kotek suggest that having a 1:1 ration of Services to business objects can cause issues like circular dependencies. Quick example. Say you have a ProductService and and CategoryService for your online catalog. If you have a circular dependency between the two, you might consider rolling them up into a CatalogService that provides API methods Products and Categories. This is a application design paradigm that I'm currently working toward.
So, uh, that's my 2 cents...
Cheers,
Paul
On Feb 9, 2008 12:33 PM, lagos.tout <lagos.t...@gmail.com> wrote:
Hi, Paul.
Thanks for responding. I was just curious for comparison sake with ColdSpring. I guess I haven't figured out when to use CS over LW, or vice-versa. Of course, for AOP I'd have no choice but CS. But for the things they do have in common... ? Thanks.
LT
----- Original Message ---- From: Paul Marcotte <pmarco...@gmail.com> To: lightwireFramework@googlegroups.com Sent: Thursday, February 7, 2008 3:43:58 PM Subject: {LightwireFramework} Re: Handling circular dependencies.
Hey LT,
You can use "mixin" injection in Lightwire rather than "setter" injection. In ColdSpring the way around a circular dependency is to use a property tag instead of a constructor-arg. Lightwire has both constructor and setter injection and the aforementioned mixin injection.
I caught your post on the ColdSpring list as well, so I'm curious about you object dependencies. Do you mind sharing some information about the dependent objects?
Paul
On Feb 7, 2008 3:31 PM, LT <lagos.t...@gmail.com> wrote:
Hi,
I was wondering if Lightwire handles circular dependencies in a different way from ColdSpring. Thanks.
You can absolutely use LW with factories. However, because LW can act as a simple factory, your ³factory² methods can be simpler. I have a UserService.new() thatıll return a new user object, but the entire code for it is:
cfreturn BeanFactory.getBean(³User²);
That returns my User with (say) a UserDAO or whatever else it needs injected already and ready for use.
So, if I want a UserService.getByID(UserID) method, itıll just be:
var User = new(); User.loadQuery(DAO.getbyID(UserID)); cfreturn User
Obviously if I needed an abstract factory, itıd be a little more code.
Best Wishes, Peter
On 2/10/08 4:57 PM, "lagos.tout" <lagos.t...@gmail.com> wrote:
> :) > ok. i will. > so do you not use factories? > is it not ok (read 'not best practice') to use LW with factories? > thanks. > LT
> ----- Original Message ---- > From: Peter Bell <systemsfo...@gmail.com> > To: lightwireFramework@googlegroups.com > Sent: Sunday, February 10, 2008 10:54:28 AM > Subject: {LightwireFramework} Re: Handling circular dependencies.
> If you want to DI into transients using CS, just email to the ColdSpring list, > explain what you want to do and ask whether you should use CS to inject into > the transients using ³singleton=²false²² and if not, what approach theyıd > recommend. Please donıt mention me or LightWire seems to piss them off over > there :->
> Best Wishes, > Peter
> On 2/10/08 1:38 PM, "lagos.tout" <lagos.t...@gmail.com> wrote:
>> Thanks, Peter. >> Would you mind explaining a bit more what you mean by "The recommended >> solution in CS is to create a factory thatıs bean aware for the transient DI >> (say you have a user that requires a UserDAO)" Also, why is injection into >> transients not recommended with CS? >> LT
>> ----- Original Message ---- >> From: Peter Bell <systemsfo...@gmail.com> >> To: lightwireFramework@googlegroups.com >> Sent: Sunday, February 10, 2008 9:31:17 AM >> Subject: {LightwireFramework} Re: Handling circular dependencies.
>> Also, LW was designed for DI into transients as well as singletons. You *can* >> do that with CS, but it is not recommended. The recommended solution in CS is >> to create a factory thatıs bean aware for the transient DI (say you have a >> user that requires a UserDAO).
>> Oh, and if you want to write a programmatic config file (instead of XML), >> that can be done in LW but in CS youıd have to write a script to gen your xml >> and then pass that in.
>> I just find LW more elegant for my use cases and as I really need AOP or >> other such features, I believe I can add them to LW while still keeping it >> really tight.
>> Best Wishes, >> Peter
>> On 2/9/08 9:47 PM, "Paul Marcotte" <pmarco...@gmail.com> wrote:
>>> Hi LT,
>>> My pleasure. To give you a bit more information, you can use a superset of >>> ColdSpring xml definitions with Lightwire. The difference is that since >>> Lightwire supports mixin injection, there is a <mixin/> tag. What mixin >>> give you is the ability to reference the dependency as variables.MyMixin >>> without having to add a specific setter for "MyMixin".
>>> But that's where it stops. You won't find AOP, Autowiring, or remote >>> proxies with LightWire.
>>> Regarding the circular dependency, I just wanted to mention that many of the >>> community leaders like Sean Corfield and Brian Kotek suggest that having a >>> 1:1 ration of Services to business objects can cause issues like circular >>> dependencies. Quick example. Say you have a ProductService and and >>> CategoryService for your online catalog. If you have a circular dependency >>> between the two, you might consider rolling them up into a CatalogService >>> that provides API methods Products and Categories. This is a application >>> design paradigm that I'm currently working toward.
>>> So, uh, that's my 2 cents...
>>> Cheers,
>>> Paul
>>> On Feb 9, 2008 12:33 PM, lagos.tout <lagos.t...@gmail.com> wrote: >>>> Hi, Paul.
>>>> Thanks for responding. >>>> I was just curious for comparison sake with ColdSpring. >>>> I guess I haven't figured out when to use CS over LW, or vice-versa. >>>> Of course, for AOP I'd have no choice but CS. But for the things they do >>>> have in common... ? >>>> Thanks.
>>>> LT
>>>> ----- Original Message ---- >>>> From: Paul Marcotte <pmarco...@gmail.com> >>>> To: lightwireFramework@googlegroups.com >>>> Sent: Thursday, February 7, 2008 3:43:58 PM >>>> Subject: {LightwireFramework} Re: Handling circular dependencies.
>>>> Hey LT,
>>>> You can use "mixin" injection in Lightwire rather than "setter" injection. >>>> In ColdSpring the way around a circular dependency is to use a property >>>> tag instead of a constructor-arg. Lightwire has both constructor and >>>> setter injection and the aforementioned mixin injection.
>>>> I caught your post on the ColdSpring list as well, so I'm curious about you >>>> object dependencies. Do you mind sharing some information about the >>>> dependent objects?
>>>> Paul
>>>> On Feb 7, 2008 3:31 PM, LT <lagos.t...@gmail.com> wrote:
>>>>> Hi,
>>>>> I was wondering if Lightwire handles circular dependencies in a >>>>> different way from ColdSpring. >>>>> Thanks.
Before diving in and asking about transients on the CS list, do a search. Brian Kotek recently announced a BeanInjector that is designed for singleton injection into transients without the performance hit you get when doing this natively in CS.
Cheers,
Paul
On Feb 10, 2008 1:57 PM, lagos.tout <lagos.t...@gmail.com> wrote:
> :) > ok. i will. > so do you not use factories? > is it not ok (read 'not best practice') to use LW with factories? > thanks. > LT
> ----- Original Message ---- > From: Peter Bell <systemsfo...@gmail.com> > To: lightwireFramework@googlegroups.com > Sent: Sunday, February 10, 2008 10:54:28 AM > Subject: {LightwireFramework} Re: Handling circular dependencies.
> If you want to DI into transients using CS, just email to the ColdSpring > list, explain what you want to do and ask whether you should use CS to > inject into the transients using "singleton="false"" and if not, what > approach they'd recommend. Please don't mention me or LightWire seems to > piss them off over there :->
> Best Wishes, > Peter
> On 2/10/08 1:38 PM, "lagos.tout" <lagos.t...@gmail.com> wrote:
> Thanks, Peter. > Would you mind explaining a bit more what you mean by "The recommended > solution in CS is to create a factory that's bean aware for the transient DI > (say you have a user that requires a UserDAO)" Also, why is injection into > transients not recommended with CS? > LT
> ----- Original Message ---- > From: Peter Bell <systemsfo...@gmail.com> > To: lightwireFramework@googlegroups.com > Sent: Sunday, February 10, 2008 9:31:17 AM > Subject: {LightwireFramework} Re: Handling circular dependencies.
> Also, LW was designed for DI into transients as well as singletons. You > *can* do that with CS, but it is not recommended. The recommended solution > in CS is to create a factory that's bean aware for the transient DI (say you > have a user that requires a UserDAO).
> Oh, and if you want to write a programmatic config file (instead of XML), > that can be done in LW but in CS you'd have to write a script to gen your > xml and then pass that in.
> I just find LW more elegant for my use cases and as I really need AOP or > other such features, I believe I can add them to LW while still keeping it > really tight.
> Best Wishes, > Peter
> On 2/9/08 9:47 PM, "Paul Marcotte" <pmarco...@gmail.com> wrote:
> Hi LT,
> My pleasure. To give you a bit more information, you can use a superset > of ColdSpring xml definitions with Lightwire. The difference is that since > Lightwire supports mixin injection, there is a <mixin/> tag. What mixin > give you is the ability to reference the dependency as variables.MyMixinwithout having to add a specific setter for "MyMixin".
> But that's where it stops. You won't find AOP, Autowiring, or remote > proxies with LightWire.
> Regarding the circular dependency, I just wanted to mention that many of > the community leaders like Sean Corfield and Brian Kotek suggest that having > a 1:1 ration of Services to business objects can cause issues like circular > dependencies. Quick example. Say you have a ProductService and and > CategoryService for your online catalog. If you have a circular dependency > between the two, you might consider rolling them up into a CatalogService > that provides API methods Products and Categories. This is a application > design paradigm that I'm currently working toward.
> So, uh, that's my 2 cents...
> Cheers,
> Paul
> On Feb 9, 2008 12:33 PM, lagos.tout <lagos.t...@gmail.com> wrote:
> Hi, Paul.
> Thanks for responding. > I was just curious for comparison sake with ColdSpring. > I guess I haven't figured out when to use CS over LW, or vice-versa. > Of course, for AOP I'd have no choice but CS. But for the things they do > have in common... ? > Thanks.
> LT
> ----- Original Message ---- > From: Paul Marcotte <pmarco...@gmail.com> > To: lightwireFramework@googlegroups.com > Sent: Thursday, February 7, 2008 3:43:58 PM > Subject: {LightwireFramework} Re: Handling circular dependencies.
> Hey LT,
> You can use "mixin" injection in Lightwire rather than "setter" injection. > In ColdSpring the way around a circular dependency is to use a property > tag instead of a constructor-arg. Lightwire has both constructor and > setter injection and the aforementioned mixin injection.
> I caught your post on the ColdSpring list as well, so I'm curious about > you object dependencies. Do you mind sharing some information about the > dependent objects?
> Paul
> On Feb 7, 2008 3:31 PM, LT <lagos.t...@gmail.com> wrote:
> Hi,
> I was wondering if Lightwire handles circular dependencies in a > different way from ColdSpring. > Thanks.
