springframework-developer

RE: [Springframework-developer] SimpleNamingContext should be usable with other providers around

[<jue...@we...>]

TGV0J3MgZmFjdG9yIG91dCB0aGUgYW5vbnltb3VzIGlubmVyIGNsYXNzIGZyb20gU2ltcGxlTmFt
aW5nQ29udGV4dEJ1aWxkZXIuY3JlYXRlSW5pdGlhbENvbnRleHRGYWN0b3J5IHRvIGEgc2VwYXJh
dGUgU2ltcGxlTmFtaW5nQ29udGV4dEZhY3RvcnkgY2xhc3MuIFRoaXMgc2hvdWxkIGFsbG93IGZv
ciB1c2luZyBpdCBpbiB0aGUgd2F5IHlvdSBpbnRlbmRlZC4NCiANClVzaW5nIGEgc2luZ2xldG9u
IGJlYW4gZmFjdG9yeSBzaG91bGQgd29yayB0b28uIFlvdSBjb3VsZCBhbHNvIGltcGxlbWVudCB5
b3VyIG93biBjdXN0b20gc2luZ2xldG9uIHRoYXQgbG9hZHMgd2hhdGV2ZXIgQmVhbkZhY3Rvcnkg
dHlwZSB5b3UgbmVlZC4NCiANCkp1ZXJnZW4NCiANCg0KCS0tLS0tT3JpZ2luYWwgTWVzc2FnZS0t
LS0tIA0KCUZyb206IENvbGluIFNhbXBhbGVhbnUgW21haWx0bzpjb2xpbm1sMUBleGlzLmNvbV0g
DQoJU2VudDogVHVlIDkvMTYvMjAwMyAxMjoxNiBBTSANCglUbzogc3ByaW5nZnJhbWV3b3JrLWRl
dmVsb3BlckBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQgDQoJQ2M6IA0KCVN1YmplY3Q6IFtTcHJpbmdm
cmFtZXdvcmstZGV2ZWxvcGVyXSBTaW1wbGVOYW1pbmdDb250ZXh0IHNob3VsZCBiZSB1c2FibGUg
d2l0aCBvdGhlciBwcm92aWRlcnMgYXJvdW5kDQoJDQoJDQoJIA0KDQo=

Re: [Springframework-developer] SimpleNamingContext should be usable with other providers around

[Colin S. <col...@ex...>]

jürgen höller [werk3AT] wrote:

>Let's factor out the anonymous inner class from SimpleNamingContextBuilder.createInitialContextFactory to a separate SimpleNamingContextFactory class. This should allow for using it in the way you intended.
> 
>Using a singleton bean factory should work too. You could also implement your own custom singleton that loads whatever BeanFactory type you need.
>  
>
I was being lazy. Easiest thing for me to do is just create a singleton 
that returns an instance of StaticSingletonBeanFactory. But I think a 
class like this (similar to BeanFactoryBootstrap except it would return 
StaticSingletonBeanFactory) would be handy to have built-in.

And for the record, I am not trying to subvert IOC here :-).  What I 
actually want to do (which I will get to in another message) is link up 
several ApplicationContext instances which are loaded in different 
layers, and I need a place to store them temporarilly as they get created...

Re: [Springframework-developer] SimpleNamingContext should be usable with other providers around

[Rod J. <rod...@in...>]

Colin,

If you want to implement such an approach, please do and submit it for
discussion, along with how you're using it.

Regards,
Rod

----- Original Message ----- 
From: "Colin Sampaleanu" <col...@ex...>
To: "jürgen höller [werk3AT]" <jue...@we...>
Cc: <spr...@li...>
Sent: Tuesday, September 16, 2003 2:45 PM
Subject: Re: [Springframework-developer] SimpleNamingContext should be
usable with other providers around


> jürgen höller [werk3AT] wrote:
>
> >Let's factor out the anonymous inner class from
SimpleNamingContextBuilder.createInitialContextFactory to a separate
SimpleNamingContextFactory class. This should allow for using it in the way
you intended.
> >
> >Using a singleton bean factory should work too. You could also implement
your own custom singleton that loads whatever BeanFactory type you need.
> >
> >
> I was being lazy. Easiest thing for me to do is just create a singleton
> that returns an instance of StaticSingletonBeanFactory. But I think a
> class like this (similar to BeanFactoryBootstrap except it would return
> StaticSingletonBeanFactory) would be handy to have built-in.
>
> And for the record, I am not trying to subvert IOC here :-).  What I
> actually want to do (which I will get to in another message) is link up
> several ApplicationContext instances which are loaded in different
> layers, and I need a place to store them temporarilly as they get
created...
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] SimpleNamingContext should be usable with other providers around

[Colin S. <col...@ex...>]

How about I modify StaticListableBeanFactory, so it can optionally be 
constructed with the HashMap access being synchronized, and create an 
accessor class which returns a singleton instance of 
StaticListableBeanFactory?


Rod Johnson wrote:

>Colin,
>
>If you want to implement such an approach, please do and submit it for
>discussion, along with how you're using it.
>
>Regards,
>Rod
>
>----- Original Message ----- 
>From: "Colin Sampaleanu" <col...@ex...>
>To: "jürgen höller [werk3AT]" <jue...@we...>
>Cc: <spr...@li...>
>Sent: Tuesday, September 16, 2003 2:45 PM
>Subject: Re: [Springframework-developer] SimpleNamingContext should be
>usable with other providers around
>
>
>  
>
>>jürgen höller [werk3AT] wrote:
>>
>>    
>>
>>>Let's factor out the anonymous inner class from
>>>      
>>>
>SimpleNamingContextBuilder.createInitialContextFactory to a separate
>SimpleNamingContextFactory class. This should allow for using it in the way
>you intended.
>  
>
>>>Using a singleton bean factory should work too. You could also implement
>>>      
>>>
>your own custom singleton that loads whatever BeanFactory type you need.
>  
>
>>>      
>>>
>>I was being lazy. Easiest thing for me to do is just create a singleton
>>that returns an instance of StaticSingletonBeanFactory. But I think a
>>class like this (similar to BeanFactoryBootstrap except it would return
>>StaticSingletonBeanFactory) would be handy to have built-in.
>>
>>And for the record, I am not trying to subvert IOC here :-).  What I
>>actually want to do (which I will get to in another message) is link up
>>several ApplicationContext instances which are loaded in different
>>layers, and I need a place to store them temporarilly as they get
>>    
>>
>created...
>  
>

Re: [Springframework-developer] SimpleNamingContext should be usable with other providers around

[Colin S. <col...@ex...>]

Colin Sampaleanu wrote:

> jürgen höller [werk3AT] wrote:
>
>> Let's factor out the anonymous inner class from 
>> SimpleNamingContextBuilder.createInitialContextFactory to a separate 
>> SimpleNamingContextFactory class. This should allow for using it in 
>> the way you intended.
>>
>> Using a singleton bean factory should work too. You could also 
>> implement your own custom singleton that loads whatever BeanFactory 
>> type you need. 
>
> I was being lazy. Easiest thing for me to do is just create a 
> singleton that returns an instance of StaticSingletonBeanFactory. But 
> I think a class like this (similar to BeanFactoryBootstrap except it 
> would return StaticSingletonBeanFactory) would be handy to have built-in.

Of course, I meant StaticListableBeanFactory here, not 
StaticSingletonBeanFactory...

>
> And for the record, I am not trying to subvert IOC here :-).  What I 
> actually want to do (which I will get to in another message) is link 
> up several ApplicationContext instances which are loaded in different 
> layers, and I need a place to store them temporarilly as they get 
> created...