RE: [Springframework-developer] new bean factory and application context features

[Kopylenko, D. <dko...@ac...>]

I guess it's -1 against the source level metadata use case. Well, since =
this
is a brand new concept (for java at least) what are everyone's
thoughts/feelings about it?

Regards,
Dmitriy.


-----Original Message-----
From: Colin Sampaleanu [mailto:col...@ex...]=20
Sent: Tuesday, October 14, 2003 6:09 PM
To: Kopylenko, Dmitry
Cc: "'\"j=FCrgen h=F6ller [werk3AT]\" '";
'spr...@li... '
Subject: Re: [Springframework-developer] new bean factory and =
application
context features


I suppose, although to tell you the truth I prefer to declare my=20
trnasactions separately from the source. Putting them in the source=20
couples things too closely for my taste, and makes management harder,=20
given that I want to change things around for unit tests and the like.


Kopylenko, Dmitry wrote:

>Colin,
>
>that will be possible when the metadata support and "magic"=20
>TransactionAutoProxy creator will be in place ;-)
>
>Regards,
>Dmitriy.
>
>-----Original Message-----
>From: Colin Sampaleanu
>To: "j=FCrgen h=F6ller [werk3AT]"
>Cc: spr...@li...
>Sent: 10/14/2003 5:49 PM
>Subject: Re: [Springframework-developer] new bean factory and=20
>application context features
>
>j=FCrgen h=F6ller [werk3AT] wrote:
>
> =20
>
>>...
>>
>>This is a BeanPostProcessor bean that can be set up as follows to=20
>>proxy
>>   =20
>>
>the beans with the given names with the given interceptors. Note that=20
>this is only one bean with proxy settings to define, although there=20
>might be dozens of target beans with the same proxy behavior.
> =20
>
>><bean id=3D"autoProxyCreator"
>>   =20
>>
>class=3D"org.springframework.aop.framework.support.AutoProxyCreator">
> =20
>
>> <property
>>   =20
>>
>name=3D"beanNames"><value>myBean1,myBean2,myBean3</value></property>
> =20
>
>> <property name=3D"interceptors>
>>   <list>
>>     <ref bean=3D"myInterceptor1"/>
>>     <ref bean=3D"myInterceptor2"/>
>>   </list>
>> </property>
>></bean>
>>
>>So setting up 10 transactional beans would just involve 1
>>   =20
>>
>AutoProxyCreator and 1 transaction interceptor plus the 10 target =
beans=20
>(12 beans in total), instead of 10 TransactionProxyFactoryBeans plus=20
>the 10 target beans (20 beans in total). The transaction attributes=20
>would be centralized though, in contrast to =
TransactionProxyFactoryBean=20
>that keeps them local per individual proxy definition.
> =20
>
>>=20
>>
>>   =20
>>
>Hi Juergen,
>
>How do you see this being used (if at all) with the current
>TransactionInterceptor, since its TransactionAttributeSource property=20
>gets satisfied via a MethodMapTransactionAttributeSource instance =
(which
>
>needs definitions in the format 'FQN.methodName'). While this works=20
>fine
>
>when doing individual interceptors for use with ProxyFactoryBean, =
short
>of adding new code I'm at a loss as to how I could use=20
>TransactionInterceptor with BeanNameAutoProxy to do transactions on =
all=20
>methods in all the beans I feed to the auto proxy.
>
>Just wondering if I missed something?
>
>Regards,
>Colin
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: SF.net Giveback Program.=20
>SourceForge.net hosts over 70,000 Open Source Projects. See the people =

>who have HELPED US provide better services: Click here:=20
>http://sourceforge.net/supporters.php
>_______________________________________________
>Springframework-developer mailing list=20
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
> =20
>