springframework-developer — Spring Framework developers list

Re: [Springframework-developer] AutoProxyCreator problem

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

It's meant to be an SPI interface. However I think with the PostProcessor
API there may be a call for exposing the BeanDefinition to _That_. Not via
the BeanFactoyr interface though.

R
----- Original Message ----- 
From: "Kopylenko, Dmitry" <dko...@su...>
To: <spr...@li...>
Sent: Thursday, November 20, 2003 8:00 PM
Subject: RE: [Springframework-developer] AutoProxyCreator problem


> Rajeev,
>
> You're right. There is no public API for getBeanDefinition(). There is a
> protected abstract getBeanDefinition(String) in AbstractBeanFactory
designed
> for subclasses to implement "Template Method" design pattern.
>
> Regards,
> Dmitriy.
>
> -----Original Message-----
> From: Rajeev Kaul [mailto:Ra...@cu...]
> Sent: Thursday, November 20, 2003 2:39 PM
> To: spr...@li...
> Subject: Re: [Springframework-developer] AutoProxyCreator problem
>
>
> Dmitry,
>
> How do you get the bean definition from a bean factory?  There does not
seem
> to be any public method for it.
>
> regards,
>
> Rajeev
> ----- Original Message -----
> From: "Kopylenko, Dmitry" <dko...@su...>
> To: "'Rajeev Kaul '" <Ra...@cu...>;
> <spr...@li...>
> Sent: Wednesday, November 19, 2003 5:16 PM
> Subject: RE: [Springframework-developer] AutoProxyCreator problem
>
>
> > As to your first problem, you would need to create a new instance of
> > the BeanFactory Consider the following piece of code (taken from
> > EnterpriseServices.createInvokerInterceptor() ):
> >
> > // Infinite cycle: tries to create the bean if we don't use a
> > different factory ListableBeanFactoryImpl bf2 = new
> > ListableBeanFactoryImpl(); bf2.registerBeanDefinition(beanName,
> > definition); cpii.setBeanFactory(bf2);
> >
> > ...where cpii is the reference of type
> > AbstractPoolingInvokerInterceptor which extends
> > PrototypeInvokerInterceptor
> >
> > I guess this is what you need.
> >
> > Dmitriy.
> >
> > -----Original Message-----
> > From: Rajeev Kaul
> > To: spr...@li...
> > Sent: 11/19/2003 7:33 PM
> > Subject: Re: [Springframework-developer] AutoProxyCreator problem
> >
> > I am thinking of a solution for condensing the verbose configuration
> > (shown below) for prototype business logic beans I am using in my
> > application.  A shared controller instance (singelton) creates the
> > business logic bean.  However the business logic bean must be
> > instantiated per each thread that runs through the shared controller.
> > I have been using the configuration shown below:
> >
> >
> > <bean id="prototypeBean" class="xyz.BusLogicBean" singleton="false">
> >
> > <property name="count"><value>10</value></property>
> >
> > </bean>
> >
> > <bean id="prototypeInvokerInterceptor"
> > class="org.springframework.aop.interceptor.PrototypeInvokerInterceptor
> > ">
> >
> >
> > <property
> > name="targetBeanName"><value>prototypeBean</value></property>
> >
> > </bean>
> >
> > <bean id="prototype"
> > class="org.springframework.aop.framework.ProxyFactoryBean">
> >
> > <property
> > name="interceptorNames"><value>prototypeInvokerInterceptor</value></pr
> > op
> > erty>
> >
> > </bean>
> >
> >
> >
> > As you can see this is very verbose, especially if you have a lot of
> > these business logic beans in your application.  I tried using a
> > derived version of BeanNameAutoProxyCreator to solve this, but ran
> > into problems. I would like to replace this configuration with
> > something shown below:
> >
> >
> >
> > <bean id="prototypeBean" class="xyz.BusLogicBean" singleton="false"
> > proxy="prototype">
> >
> > <property name="count"><value>10</value></property>
> >
> > </bean>
> >
> > This would involve adding a "PROXY" attribute which would specify the
> > type of proxy interceptor desired for the bean.  For example,
> > "prototype" would mean ProxyFactoryBean with
> > PrototypeInvokerInterceptor, "default" would mean ProxyFactoryBean
> > with InvokerInterceptor, etc.  In loadBeanDefinition() method of the
> > XmlBeanFactory class, the supporting proxy classes (ProxyFactoryBean
> > and PrototypeInvokerInterceptor) could be automatically generated and
> > registered.
> >
> > Any suggestions, comments, ...?
> >
> >
> >
> > Rajeev
> >
> > ----- Original Message -----
> > From: Rajeev Kaul <mailto:Ra...@cu...>
> > To: spr...@li...
> > <mailto:spr...@li...>
> > Sent: Tuesday, November 18, 2003 1:29 PM
> > Subject: [Springframework-developer] AutoProxyCreator problem
> >
> >
> > I have been trying to use BeanNameAutoProxyCreator class (I noticed
> > there are no test cases for it) to create proxies for "prototype"
> > business objects. I extended the BeanNameAutoProxyCreator class to use
> > the PrototypeInvokerInterceptor in the "createInvokerInterceptor()"
> > method.  However, this results in an infinite loop, as the
> > PrototypeInvokerInterceptor calls the beanFactory getBean() method
> > which in turn triggers the beanPostProcessor and the cycle repeats
> > endlessly.
> >
> > Any suggestions on getting around this problem?
> >
> > It would have been better, if the BeanNameAutoProxyCreator class was
> > designed to take invokerInterceptor as a property, which could be
> > specified in the configuration, instead of having to subclass it to
> > use other invokerInterceptor(s).
> >
> > Rajeev Kaul
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: SF.net Giveback Program. Does
> > SourceForge.net help you be more productive?  Does it help you create
> > better code?  SHARE THE LOVE, and help us help YOU!  Click Here:
> > http://sourceforge.net/donate/
> > _______________________________________________
> > Springframework-developer mailing list
> > Spr...@li...
> > https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program. Does
> SourceForge.net help you be more productive?  Does it help you create
better
> code?  SHARE THE LOVE, and help us help YOU!  Click Here:
> http://sourceforge.net/donate/
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>

RE: [Springframework-developer] AutoProxyCreator problem

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

Rajeev,

You're right. There is no public API for getBeanDefinition(). There is a
protected abstract getBeanDefinition(String) in AbstractBeanFactory designed
for subclasses to implement "Template Method" design pattern.

Regards,
Dmitriy.

-----Original Message-----
From: Rajeev Kaul [mailto:Ra...@cu...] 
Sent: Thursday, November 20, 2003 2:39 PM
To: spr...@li...
Subject: Re: [Springframework-developer] AutoProxyCreator problem


Dmitry,

How do you get the bean definition from a bean factory?  There does not seem
to be any public method for it.

regards,

Rajeev
----- Original Message -----
From: "Kopylenko, Dmitry" <dko...@su...>
To: "'Rajeev Kaul '" <Ra...@cu...>;
<spr...@li...>
Sent: Wednesday, November 19, 2003 5:16 PM
Subject: RE: [Springframework-developer] AutoProxyCreator problem


> As to your first problem, you would need to create a new instance of 
> the BeanFactory Consider the following piece of code (taken from
> EnterpriseServices.createInvokerInterceptor() ):
>
> // Infinite cycle: tries to create the bean if we don't use a 
> different factory ListableBeanFactoryImpl bf2 = new 
> ListableBeanFactoryImpl(); bf2.registerBeanDefinition(beanName, 
> definition); cpii.setBeanFactory(bf2);
>
> ...where cpii is the reference of type 
> AbstractPoolingInvokerInterceptor which extends 
> PrototypeInvokerInterceptor
>
> I guess this is what you need.
>
> Dmitriy.
>
> -----Original Message-----
> From: Rajeev Kaul
> To: spr...@li...
> Sent: 11/19/2003 7:33 PM
> Subject: Re: [Springframework-developer] AutoProxyCreator problem
>
> I am thinking of a solution for condensing the verbose configuration 
> (shown below) for prototype business logic beans I am using in my 
> application.  A shared controller instance (singelton) creates the 
> business logic bean.  However the business logic bean must be 
> instantiated per each thread that runs through the shared controller.  
> I have been using the configuration shown below:
>
>
> <bean id="prototypeBean" class="xyz.BusLogicBean" singleton="false">
>
> <property name="count"><value>10</value></property>
>
> </bean>
>
> <bean id="prototypeInvokerInterceptor" 
> class="org.springframework.aop.interceptor.PrototypeInvokerInterceptor
> ">
>
>
> <property 
> name="targetBeanName"><value>prototypeBean</value></property>
>
> </bean>
>
> <bean id="prototype" 
> class="org.springframework.aop.framework.ProxyFactoryBean">
>
> <property 
> name="interceptorNames"><value>prototypeInvokerInterceptor</value></pr
> op
> erty>
>
> </bean>
>
>
>
> As you can see this is very verbose, especially if you have a lot of 
> these business logic beans in your application.  I tried using a 
> derived version of BeanNameAutoProxyCreator to solve this, but ran 
> into problems. I would like to replace this configuration with 
> something shown below:
>
>
>
> <bean id="prototypeBean" class="xyz.BusLogicBean" singleton="false" 
> proxy="prototype">
>
> <property name="count"><value>10</value></property>
>
> </bean>
>
> This would involve adding a "PROXY" attribute which would specify the 
> type of proxy interceptor desired for the bean.  For example, 
> "prototype" would mean ProxyFactoryBean with 
> PrototypeInvokerInterceptor, "default" would mean ProxyFactoryBean 
> with InvokerInterceptor, etc.  In loadBeanDefinition() method of the 
> XmlBeanFactory class, the supporting proxy classes (ProxyFactoryBean 
> and PrototypeInvokerInterceptor) could be automatically generated and 
> registered.
>
> Any suggestions, comments, ...?
>
>
>
> Rajeev
>
> ----- Original Message -----
> From: Rajeev Kaul <mailto:Ra...@cu...>
> To: spr...@li...
> <mailto:spr...@li...>
> Sent: Tuesday, November 18, 2003 1:29 PM
> Subject: [Springframework-developer] AutoProxyCreator problem
>
>
> I have been trying to use BeanNameAutoProxyCreator class (I noticed 
> there are no test cases for it) to create proxies for "prototype" 
> business objects. I extended the BeanNameAutoProxyCreator class to use 
> the PrototypeInvokerInterceptor in the "createInvokerInterceptor()" 
> method.  However, this results in an infinite loop, as the 
> PrototypeInvokerInterceptor calls the beanFactory getBean() method 
> which in turn triggers the beanPostProcessor and the cycle repeats 
> endlessly.
>
> Any suggestions on getting around this problem?
>
> It would have been better, if the BeanNameAutoProxyCreator class was 
> designed to take invokerInterceptor as a property, which could be 
> specified in the configuration, instead of having to subclass it to 
> use other invokerInterceptor(s).
>
> Rajeev Kaul
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program. Does 
> SourceForge.net help you be more productive?  Does it help you create 
> better code?  SHARE THE LOVE, and help us help YOU!  Click Here: 
> http://sourceforge.net/donate/ 
> _______________________________________________
> Springframework-developer mailing list 
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program. Does
SourceForge.net help you be more productive?  Does it help you create better
code?  SHARE THE LOVE, and help us help YOU!  Click Here:
http://sourceforge.net/donate/
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

[Springframework-developer] Re: Re: Intercepting a Prototype Bean

[roger h. <apo...@sn...>]

Hi Juergen

As Mark's experience has just demonstrated, the fact that FactoryBean's are
not required to be singleton's does provide a very ready source of confusion
for the uninitiated.  The only reason I was aware of this problem, was
because initially I too was very confused, until I had spent good deal of
time working out what the code was actually doing.

I would definitely favour option 2.

While we're on the subject of FactoryBean's and their curiosities, another
thing that took me a long time to work out was the non-uniform dereferencing
of factory bean names. ie isSingleton() and getBean() do not behave
consistently.

If I have a prototype FactoryBean named "proto", ie:

<bean id="proto"
    class="org.springframework.aop.framework.ProxyFactoryBean">
    <property name="singleton"><value>false</value></property>
</bean>

a call to

    beanFactory.isSingleton("proto");

will return true, but repeated calls to

    beaFactory.getBean("proto")

will indeed return separate prototype instances.

Personally, I find this very counterintuitive and would be happy to see this
changed ;)

Roger



"jürgen höller [werk3AT]" <jue...@we...> wrote in message
news:170...@co......
Roger,

This is indeed true, and I have not been aware of it: If a FactoryBean is
defined as prototype, getBean will currently return the FactoryBean itself.

There are obviously two solutions for this:
1. make getBean return the FactoryBean-created object even for FactoryBean
prototypes
2. require FactoryBeans to be defined as singletons by forbidding
singleton="false"

Option 2 isn't bad in the first place, as it's hard to image why a
FactoryBean itself should be a prototype. Of course, option 1 could be
easily implemented too, and it leaves the choice to the application
developer. Opinions?

We should definitely address this for 1.0 M3, to be released this weekend!

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of roger holbrook
Sent: Thursday, November 20, 2003 7:28 PM
To: spr...@li...
Subject: [Springframework-developer] Re: Intercepting a Prototype Bean


Rod

I think this is a probably bug in AbstractBeanFactory - currently any
getBean() for a FactoryBean that was defined with a bean attribute of
singleton="false", will always return the FactoryBean instance, rather than
a Proxy instance.  This happens because createBean() does not do any factory
dereferencing.

One fix would just be to trap the combination when the beans are being
defined.

Even if createBean() were actually handling the dereferencing correctly,
I think there would still be a problem on a normal sequence of getBean()
calls - since each call would generate a new FactoryBean instance and a new
Proxy instance, but the application code would only ever see a reference to
the latter.  Application code would only be able collect references to the
FactoryBean themselves by explicitly calling getBean("&name"), and then
using these to generate Proxy instances.

A bit confusing really

Roger


"Rod Johnson" <rod...@in...> wrote in message
news:06aa01c3af8b$d4467c90$e900a8c0@chopin...
> Mark,
>
> > Is it possible to apply an interceptor to a prototype bean?
> Yes.
>
> > The prototype is stateful - i.e one per user
> Yes, Spring supports mixins, ie one interceptor per mixin instance.
>
> > I have defined the following in applicationContext.xml
> >
> >
> > <bean id="TestTarget" class="test.MyTarget" singleton="false">
> > </bean>
> >
> >
> > <bean id="TestInterceptor"
> >
>
class="org.springframework.transaction.interceptor.TransactionProxyFactoryBe
> > an" singleton="false">
> > <property name="transactionManager"><ref
> > local="transactionManager"/></property>
> >
> > <property name="target"><ref local="TestTarget"/></property>
> >
> >
> > <property name="transactionAttributes">
> > <props>
> > <prop key="foo">PROPAGATION_REQUIRED</prop>
> > </props>
> > </property>
> > </bean>
> >
> >
> >
> > When I invoke the method foo I get a ClassCastException
>
> Not sure why this is happening but you may need to create the interceptor
> chain manually to use a prototype, as TransactionProxyFactoryBean propably
> assumes it's dealing with a singleton. So you need to create a chain that
> includes:
> - the name of your prototype
> - the interceptor names, which may be singletons or prototypes as you
> require. Use a prototype for mixin support.
>
> The following example comes from the test suite, with minor changes to
make
> it more obvious:
>
>
> <bean id="prototypeTarget"
> class="org.springframework.aop.interceptor.SideEffectBean"
>  singleton="false">
>  <property name="count"><value>10</value></property>
> </bean>
>
> <!-- This can be a singleton or a prototype (for mixin behaviour) -->
> <bean id="debugInterceptor"
> class="org.springframework.aop.interceptor.DebugInterceptor">
> </bean>
>
>
> <bean id="prototype"
>  class="org.springframework.aop.framework.ProxyFactoryBean">
>  <!-- will automatically create invoker interceptor for the prototype -->
>  <property
>
name="interceptorNames"><value>debugInterceptor,prototypeTarget</value></pro
> perty>
>
> <!-- Note this -->
>  <property name="singleton"><value>false</value></property>
> </bean>
>
> There is a bug in M2 to do with prototype AOP handling, which is fixed in
> the forthcoming M3. However I don't think it should affect you in such a
> simple usage.
>
>
> Regards,
> Rod
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/





















-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

Re: [Springframework-developer] AutoProxyCreator problem

[Rajeev K. <Ra...@cu...>]

Dmitry,

How do you get the bean definition from a bean factory?  There does not seem
to be any public method for it.

regards,

Rajeev
----- Original Message -----
From: "Kopylenko, Dmitry" <dko...@su...>
To: "'Rajeev Kaul '" <Ra...@cu...>;
<spr...@li...>
Sent: Wednesday, November 19, 2003 5:16 PM
Subject: RE: [Springframework-developer] AutoProxyCreator problem


> As to your first problem, you would need to create a new instance of the
> BeanFactory
> Consider the following piece of code (taken from
> EnterpriseServices.createInvokerInterceptor() ):
>
> // Infinite cycle: tries to create the bean if we don't use a different
> factory
> ListableBeanFactoryImpl bf2 = new ListableBeanFactoryImpl();
> bf2.registerBeanDefinition(beanName, definition);
> cpii.setBeanFactory(bf2);
>
> ...where cpii is the reference of type AbstractPoolingInvokerInterceptor
> which extends PrototypeInvokerInterceptor
>
> I guess this is what you need.
>
> Dmitriy.
>
> -----Original Message-----
> From: Rajeev Kaul
> To: spr...@li...
> Sent: 11/19/2003 7:33 PM
> Subject: Re: [Springframework-developer] AutoProxyCreator problem
>
> I am thinking of a solution for condensing the verbose configuration
> (shown below) for prototype business logic beans I am using in my
> application.  A shared controller instance (singelton) creates the
> business logic bean.  However the business logic bean must be
> instantiated per each thread that runs through the shared controller.  I
> have been using the configuration shown below:
>
>
> <bean id="prototypeBean" class="xyz.BusLogicBean" singleton="false">
>
> <property name="count"><value>10</value></property>
>
> </bean>
>
> <bean id="prototypeInvokerInterceptor"
> class="org.springframework.aop.interceptor.PrototypeInvokerInterceptor">
>
>
> <property name="targetBeanName"><value>prototypeBean</value></property>
>
> </bean>
>
> <bean id="prototype"
> class="org.springframework.aop.framework.ProxyFactoryBean">
>
> <property
> name="interceptorNames"><value>prototypeInvokerInterceptor</value></prop
> erty>
>
> </bean>
>
>
>
> As you can see this is very verbose, especially if you have a lot of
> these business logic beans in your application.  I tried using a derived
> version of BeanNameAutoProxyCreator to solve this, but ran into
> problems. I would like to replace this configuration with something
> shown below:
>
>
>
> <bean id="prototypeBean" class="xyz.BusLogicBean" singleton="false"
> proxy="prototype">
>
> <property name="count"><value>10</value></property>
>
> </bean>
>
> This would involve adding a "PROXY" attribute which would specify the
> type of proxy interceptor desired for the bean.  For example,
> "prototype" would mean ProxyFactoryBean with
> PrototypeInvokerInterceptor, "default" would mean ProxyFactoryBean with
> InvokerInterceptor, etc.  In loadBeanDefinition() method of the
> XmlBeanFactory class, the supporting proxy classes (ProxyFactoryBean
> and PrototypeInvokerInterceptor) could be automatically generated and
> registered.
>
> Any suggestions, comments, ...?
>
>
>
> Rajeev
>
> ----- Original Message -----
> From: Rajeev Kaul <mailto:Ra...@cu...>
> To: spr...@li...
> <mailto:spr...@li...>
> Sent: Tuesday, November 18, 2003 1:29 PM
> Subject: [Springframework-developer] AutoProxyCreator problem
>
>
> I have been trying to use BeanNameAutoProxyCreator class (I noticed
> there are no test cases for it) to create proxies for "prototype"
> business objects. I extended the BeanNameAutoProxyCreator class to use
> the PrototypeInvokerInterceptor in the "createInvokerInterceptor()"
> method.  However, this results in an infinite loop, as the
> PrototypeInvokerInterceptor calls the beanFactory getBean() method which
> in turn triggers the beanPostProcessor and the cycle repeats endlessly.
>
> Any suggestions on getting around this problem?
>
> It would have been better, if the BeanNameAutoProxyCreator class was
> designed to take invokerInterceptor as a property, which could be
> specified in the configuration, instead of having to subclass it to use
> other invokerInterceptor(s).
>
> Rajeev Kaul
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] Re: Intercepting a Prototype Bean

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

Option 2, as I say in the email which I obviously wrote at the same time as
yours and which hasn't shown up on the list yet.

----- Original Message ----- 
From: "jürgen höller [werk3AT]" <jue...@we...>
To: <spr...@li...>
Sent: Thursday, November 20, 2003 6:56 PM
Subject: RE: [Springframework-developer] Re: Intercepting a Prototype Bean


Roger,

This is indeed true, and I have not been aware of it: If a FactoryBean is
defined as prototype, getBean will currently return the FactoryBean itself.

There are obviously two solutions for this:
1. make getBean return the FactoryBean-created object even for FactoryBean
prototypes
2. require FactoryBeans to be defined as singletons by forbidding
singleton="false"

Option 2 isn't bad in the first place, as it's hard to image why a
FactoryBean itself should be a prototype. Of course, option 1 could be
easily implemented too, and it leaves the choice to the application
developer. Opinions?

We should definitely address this for 1.0 M3, to be released this weekend!

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of roger holbrook
Sent: Thursday, November 20, 2003 7:28 PM
To: spr...@li...
Subject: [Springframework-developer] Re: Intercepting a Prototype Bean


Rod

I think this is a probably bug in AbstractBeanFactory - currently any
getBean() for a FactoryBean that was defined with a bean attribute of
singleton="false", will always return the FactoryBean instance, rather than
a Proxy instance.  This happens because createBean() does not do any factory
dereferencing.

One fix would just be to trap the combination when the beans are being
defined.

Even if createBean() were actually handling the dereferencing correctly,
I think there would still be a problem on a normal sequence of getBean()
calls - since each call would generate a new FactoryBean instance and a new
Proxy instance, but the application code would only ever see a reference to
the latter.  Application code would only be able collect references to the
FactoryBean themselves by explicitly calling getBean("&name"), and then
using these to generate Proxy instances.

A bit confusing really

Roger


"Rod Johnson" <rod...@in...> wrote in message
news:06aa01c3af8b$d4467c90$e900a8c0@chopin...
> Mark,
>
> > Is it possible to apply an interceptor to a prototype bean?
> Yes.
>
> > The prototype is stateful - i.e one per user
> Yes, Spring supports mixins, ie one interceptor per mixin instance.
>
> > I have defined the following in applicationContext.xml
> >
> >
> > <bean id="TestTarget" class="test.MyTarget" singleton="false">
> > </bean>
> >
> >
> > <bean id="TestInterceptor"
> >
>
class="org.springframework.transaction.interceptor.TransactionProxyFactoryBe
> > an" singleton="false">
> > <property name="transactionManager"><ref
> > local="transactionManager"/></property>
> >
> > <property name="target"><ref local="TestTarget"/></property>
> >
> >
> > <property name="transactionAttributes">
> > <props>
> > <prop key="foo">PROPAGATION_REQUIRED</prop>
> > </props>
> > </property>
> > </bean>
> >
> >
> >
> > When I invoke the method foo I get a ClassCastException
>
> Not sure why this is happening but you may need to create the interceptor
> chain manually to use a prototype, as TransactionProxyFactoryBean propably
> assumes it's dealing with a singleton. So you need to create a chain that
> includes:
> - the name of your prototype
> - the interceptor names, which may be singletons or prototypes as you
> require. Use a prototype for mixin support.
>
> The following example comes from the test suite, with minor changes to
make
> it more obvious:
>
>
> <bean id="prototypeTarget"
> class="org.springframework.aop.interceptor.SideEffectBean"
>  singleton="false">
>  <property name="count"><value>10</value></property>
> </bean>
>
> <!-- This can be a singleton or a prototype (for mixin behaviour) -->
> <bean id="debugInterceptor"
> class="org.springframework.aop.interceptor.DebugInterceptor">
> </bean>
>
>
> <bean id="prototype"
>  class="org.springframework.aop.framework.ProxyFactoryBean">
>  <!-- will automatically create invoker interceptor for the prototype -->
>  <property
>
name="interceptorNames"><value>debugInterceptor,prototypeTarget</value></pro
> perty>
>
> <!-- Note this -->
>  <property name="singleton"><value>false</value></property>
> </bean>
>
> There is a bug in M2 to do with prototype AOP handling, which is fixed in
> the forthcoming M3. However I don't think it should affect you in such a
> simple usage.
>
>
> Regards,
> Rod
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/





















-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] Re: Intercepting a Prototype Bean

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

My original intention was that FactoryBeans must be singletons and that
attempts to define them as prototypes should throw a
BeanDefinitionStoreException. One level of indirection should be enough.

Regards,
Rod

----- Original Message ----- 
From: "roger holbrook" <apo...@sn...>
To: <spr...@li...>
Sent: Thursday, November 20, 2003 6:28 PM
Subject: [Springframework-developer] Re: Intercepting a Prototype Bean


> Rod
>
> I think this is a probably bug in AbstractBeanFactory - currently any
> getBean() for a FactoryBean that was defined with a bean attribute of
> singleton="false", will always return the FactoryBean instance, rather
than
> a Proxy instance.  This happens because createBean() does not do any
factory
> dereferencing.
>
> One fix would just be to trap the combination when the beans are being
> defined.
>
> Even if createBean() were actually handling the dereferencing correctly,
> I think there would still be a problem on a normal sequence of getBean()
> calls - since each call would generate a new FactoryBean instance and a
new
> Proxy instance, but the application code would only ever see a reference
to
> the latter.  Application code would only be able collect references to the
> FactoryBean themselves by explicitly calling getBean("&name"), and then
> using these to generate Proxy instances.
>
> A bit confusing really
>
> Roger
>
>
> "Rod Johnson" <rod...@in...> wrote in message
> news:06aa01c3af8b$d4467c90$e900a8c0@chopin...
> > Mark,
> >
> > > Is it possible to apply an interceptor to a prototype bean?
> > Yes.
> >
> > > The prototype is stateful - i.e one per user
> > Yes, Spring supports mixins, ie one interceptor per mixin instance.
> >
> > > I have defined the following in applicationContext.xml
> > >
> > >
> > > <bean id="TestTarget" class="test.MyTarget" singleton="false">
> > > </bean>
> > >
> > >
> > > <bean id="TestInterceptor"
> > >
> >
>
class="org.springframework.transaction.interceptor.TransactionProxyFactoryBe
> > > an" singleton="false">
> > > <property name="transactionManager"><ref
> > > local="transactionManager"/></property>
> > >
> > > <property name="target"><ref local="TestTarget"/></property>
> > >
> > >
> > > <property name="transactionAttributes">
> > > <props>
> > > <prop key="foo">PROPAGATION_REQUIRED</prop>
> > > </props>
> > > </property>
> > > </bean>
> > >
> > >
> > >
> > > When I invoke the method foo I get a ClassCastException
> >
> > Not sure why this is happening but you may need to create the
interceptor
> > chain manually to use a prototype, as TransactionProxyFactoryBean
propably
> > assumes it's dealing with a singleton. So you need to create a chain
that
> > includes:
> > - the name of your prototype
> > - the interceptor names, which may be singletons or prototypes as you
> > require. Use a prototype for mixin support.
> >
> > The following example comes from the test suite, with minor changes to
> make
> > it more obvious:
> >
> >
> > <bean id="prototypeTarget"
> > class="org.springframework.aop.interceptor.SideEffectBean"
> >  singleton="false">
> >  <property name="count"><value>10</value></property>
> > </bean>
> >
> > <!-- This can be a singleton or a prototype (for mixin behaviour) -->
> > <bean id="debugInterceptor"
> > class="org.springframework.aop.interceptor.DebugInterceptor">
> > </bean>
> >
> >
> > <bean id="prototype"
> >  class="org.springframework.aop.framework.ProxyFactoryBean">
> >  <!-- will automatically create invoker interceptor for the
prototype -->
> >  <property
> >
>
name="interceptorNames"><value>debugInterceptor,prototypeTarget</value></pro
> > perty>
> >
> > <!-- Note this -->
> >  <property name="singleton"><value>false</value></property>
> > </bean>
> >
> > There is a bug in M2 to do with prototype AOP handling, which is fixed
in
> > the forthcoming M3. However I don't think it should affect you in such a
> > simple usage.
> >
> >
> > Regards,
> > Rod
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: SF.net Giveback Program.
> > Does SourceForge.net help you be more productive?  Does it
> > help you create better code?  SHARE THE LOVE, and help us help
> > YOU!  Click Here: http://sourceforge.net/donate/
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>

Re: [Springframework-developer] AutoProxyCreator problem

[Rajeev K. <Ra...@cu...>]

I have implemented this in my version of the spring framework.  If there =
is interest, I will be happy to submit the code.

----- Original Message -----=20
  From: Rajeev Kaul=20
  To: spr...@li...=20
  Sent: Wednesday, November 19, 2003 4:33 PM
  Subject: Re: [Springframework-developer] AutoProxyCreator problem


  I am thinking of a solution for condensing the verbose configuration =
(shown below) for prototype business logic beans I am using in my =
application.  A shared controller instance (singelton) creates the =
business logic bean.  However the business logic bean must be =
instantiated per each thread that runs through the shared controller.  I =
have been using the configuration shown below:


  <bean id=3D"prototypeBean" class=3D"xyz.BusLogicBean" =
singleton=3D"false">=20

  <property name=3D"count"><value>10</value></property>

  </bean>



  <bean id=3D"prototypeInvokerInterceptor" =
class=3D"org.springframework.aop.interceptor.PrototypeInvokerInterceptor"=
>=20

  <property =
name=3D"targetBeanName"><value>prototypeBean</value></property>

  </bean>


  <bean id=3D"prototype" =
class=3D"org.springframework.aop.framework.ProxyFactoryBean">=20

  <property =
name=3D"interceptorNames"><value>prototypeInvokerInterceptor</value></pro=
perty>


  </bean>



  As you can see this is very verbose, especially if you have a lot of =
these business logic beans in your application.  I tried using a derived =
version of BeanNameAutoProxyCreator to solve this, but ran into =
problems. I would like to replace this configuration with something =
shown below:



  <bean id=3D"prototypeBean" class=3D"xyz.BusLogicBean" =
singleton=3D"false" proxy=3D"prototype">=20

  <property name=3D"count"><value>10</value></property>

  </bean>

  This would involve adding a "PROXY" attribute which would specify the =
type of proxy interceptor desired for the bean.  For example, =
"prototype" would mean ProxyFactoryBean with =
PrototypeInvokerInterceptor, "default" would mean ProxyFactoryBean with =
InvokerInterceptor, etc.  In loadBeanDefinition() method of the =
XmlBeanFactory class, the supporting proxy classes (ProxyFactoryBean  =
and PrototypeInvokerInterceptor) could be automatically generated and =
registered.

  Any suggestions, comments, ...?



  Rajeev

    ----- Original Message -----=20
    From: Rajeev Kaul=20
    To: spr...@li...=20
    Sent: Tuesday, November 18, 2003 1:29 PM
    Subject: [Springframework-developer] AutoProxyCreator problem


    I have been trying to use BeanNameAutoProxyCreator class (I noticed =
there are no test cases for it) to create proxies for "prototype" =
business objects. I extended the BeanNameAutoProxyCreator class to use =
the PrototypeInvokerInterceptor in the "createInvokerInterceptor()" =
method.  However, this results in an infinite loop, as the =
PrototypeInvokerInterceptor calls the beanFactory getBean() method which =
in turn triggers the beanPostProcessor and the cycle repeats endlessly.

    Any suggestions on getting around this problem?

    It would have been better, if the BeanNameAutoProxyCreator class was =
designed to take invokerInterceptor as a property, which could be =
specified in the configuration, instead of having to subclass it to use =
other invokerInterceptor(s).=20

    Rajeev Kaul

RE: [Springframework-developer] Re: Intercepting a Prototype Bean

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

Roger,

This is indeed true, and I have not been aware of it: If a FactoryBean =
is defined as prototype, getBean will currently return the FactoryBean =
itself.

There are obviously two solutions for this:
1. make getBean return the FactoryBean-created object even for =
FactoryBean prototypes
2. require FactoryBeans to be defined as singletons by forbidding =
singleton=3D"false"

Option 2 isn't bad in the first place, as it's hard to image why a =
FactoryBean itself should be a prototype. Of course, option 1 could be =
easily implemented too, and it leaves the choice to the application =
developer. Opinions?

We should definitely address this for 1.0 M3, to be released this =
weekend!

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of roger holbrook
Sent: Thursday, November 20, 2003 7:28 PM
To: spr...@li...
Subject: [Springframework-developer] Re: Intercepting a Prototype Bean


Rod

I think this is a probably bug in AbstractBeanFactory - currently any
getBean() for a FactoryBean that was defined with a bean attribute of
singleton=3D"false", will always return the FactoryBean instance, rather =
than
a Proxy instance.  This happens because createBean() does not do any =
factory
dereferencing.

One fix would just be to trap the combination when the beans are being
defined.

Even if createBean() were actually handling the dereferencing correctly,
I think there would still be a problem on a normal sequence of getBean()
calls - since each call would generate a new FactoryBean instance and a =
new
Proxy instance, but the application code would only ever see a reference =
to
the latter.  Application code would only be able collect references to =
the
FactoryBean themselves by explicitly calling getBean("&name"), and then
using these to generate Proxy instances.

A bit confusing really

Roger


"Rod Johnson" <rod...@in...> wrote in message
news:06aa01c3af8b$d4467c90$e900a8c0@chopin...
> Mark,
>
> > Is it possible to apply an interceptor to a prototype bean?
> Yes.
>
> > The prototype is stateful - i.e one per user
> Yes, Spring supports mixins, ie one interceptor per mixin instance.
>
> > I have defined the following in applicationContext.xml
> >
> >
> > <bean id=3D"TestTarget" class=3D"test.MyTarget" singleton=3D"false">
> > </bean>
> >
> >
> > <bean id=3D"TestInterceptor"
> >
>
class=3D"org.springframework.transaction.interceptor.TransactionProxyFact=
oryBe
> > an" singleton=3D"false">
> > <property name=3D"transactionManager"><ref
> > local=3D"transactionManager"/></property>
> >
> > <property name=3D"target"><ref local=3D"TestTarget"/></property>
> >
> >
> > <property name=3D"transactionAttributes">
> > <props>
> > <prop key=3D"foo">PROPAGATION_REQUIRED</prop>
> > </props>
> > </property>
> > </bean>
> >
> >
> >
> > When I invoke the method foo I get a ClassCastException
>
> Not sure why this is happening but you may need to create the =
interceptor
> chain manually to use a prototype, as TransactionProxyFactoryBean =
propably
> assumes it's dealing with a singleton. So you need to create a chain =
that
> includes:
> - the name of your prototype
> - the interceptor names, which may be singletons or prototypes as you
> require. Use a prototype for mixin support.
>
> The following example comes from the test suite, with minor changes to
make
> it more obvious:
>
>
> <bean id=3D"prototypeTarget"
> class=3D"org.springframework.aop.interceptor.SideEffectBean"
>  singleton=3D"false">
>  <property name=3D"count"><value>10</value></property>
> </bean>
>
> <!-- This can be a singleton or a prototype (for mixin behaviour) -->
> <bean id=3D"debugInterceptor"
> class=3D"org.springframework.aop.interceptor.DebugInterceptor">
> </bean>
>
>
> <bean id=3D"prototype"
>  class=3D"org.springframework.aop.framework.ProxyFactoryBean">
>  <!-- will automatically create invoker interceptor for the prototype =
-->
>  <property
>
name=3D"interceptorNames"><value>debugInterceptor,prototypeTarget</value>=
</pro
> perty>
>
> <!-- Note this -->
>  <property name=3D"singleton"><value>false</value></property>
> </bean>
>
> There is a bug in M2 to do with prototype AOP handling, which is fixed =
in
> the forthcoming M3. However I don't think it should affect you in such =
a
> simple usage.
>
>
> Regards,
> Rod
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/





















-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

[Springframework-developer] Re: Intercepting a Prototype Bean

[roger h. <apo...@sn...>]

Rod

I think this is a probably bug in AbstractBeanFactory - currently any
getBean() for a FactoryBean that was defined with a bean attribute of
singleton="false", will always return the FactoryBean instance, rather than
a Proxy instance.  This happens because createBean() does not do any factory
dereferencing.

One fix would just be to trap the combination when the beans are being
defined.

Even if createBean() were actually handling the dereferencing correctly,
I think there would still be a problem on a normal sequence of getBean()
calls - since each call would generate a new FactoryBean instance and a new
Proxy instance, but the application code would only ever see a reference to
the latter.  Application code would only be able collect references to the
FactoryBean themselves by explicitly calling getBean("&name"), and then
using these to generate Proxy instances.

A bit confusing really

Roger


"Rod Johnson" <rod...@in...> wrote in message
news:06aa01c3af8b$d4467c90$e900a8c0@chopin...
> Mark,
>
> > Is it possible to apply an interceptor to a prototype bean?
> Yes.
>
> > The prototype is stateful - i.e one per user
> Yes, Spring supports mixins, ie one interceptor per mixin instance.
>
> > I have defined the following in applicationContext.xml
> >
> >
> > <bean id="TestTarget" class="test.MyTarget" singleton="false">
> > </bean>
> >
> >
> > <bean id="TestInterceptor"
> >
>
class="org.springframework.transaction.interceptor.TransactionProxyFactoryBe
> > an" singleton="false">
> > <property name="transactionManager"><ref
> > local="transactionManager"/></property>
> >
> > <property name="target"><ref local="TestTarget"/></property>
> >
> >
> > <property name="transactionAttributes">
> > <props>
> > <prop key="foo">PROPAGATION_REQUIRED</prop>
> > </props>
> > </property>
> > </bean>
> >
> >
> >
> > When I invoke the method foo I get a ClassCastException
>
> Not sure why this is happening but you may need to create the interceptor
> chain manually to use a prototype, as TransactionProxyFactoryBean propably
> assumes it's dealing with a singleton. So you need to create a chain that
> includes:
> - the name of your prototype
> - the interceptor names, which may be singletons or prototypes as you
> require. Use a prototype for mixin support.
>
> The following example comes from the test suite, with minor changes to
make
> it more obvious:
>
>
> <bean id="prototypeTarget"
> class="org.springframework.aop.interceptor.SideEffectBean"
>  singleton="false">
>  <property name="count"><value>10</value></property>
> </bean>
>
> <!-- This can be a singleton or a prototype (for mixin behaviour) -->
> <bean id="debugInterceptor"
> class="org.springframework.aop.interceptor.DebugInterceptor">
> </bean>
>
>
> <bean id="prototype"
>  class="org.springframework.aop.framework.ProxyFactoryBean">
>  <!-- will automatically create invoker interceptor for the prototype -->
>  <property
>
name="interceptorNames"><value>debugInterceptor,prototypeTarget</value></pro
> perty>
>
> <!-- Note this -->
>  <property name="singleton"><value>false</value></property>
> </bean>
>
> There is a bug in M2 to do with prototype AOP handling, which is fixed in
> the forthcoming M3. However I don't think it should affect you in such a
> simple usage.
>
>
> Regards,
> Rod
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/

Re: [Springframework-developer] Intercepting a Prototype Bean

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

Mark,

> Is it possible to apply an interceptor to a prototype bean?
Yes.

> The prototype is stateful - i.e one per user
Yes, Spring supports mixins, ie one interceptor per mixin instance.

> I have defined the following in applicationContext.xml
>
>
> <bean id="TestTarget" class="test.MyTarget" singleton="false">
> </bean>
>
>
> <bean id="TestInterceptor"
>
class="org.springframework.transaction.interceptor.TransactionProxyFactoryBe
> an" singleton="false">
> <property name="transactionManager"><ref
> local="transactionManager"/></property>
>
> <property name="target"><ref local="TestTarget"/></property>
>
>
> <property name="transactionAttributes">
> <props>
> <prop key="foo">PROPAGATION_REQUIRED</prop>
> </props>
> </property>
> </bean>
>
>
>
> When I invoke the method foo I get a ClassCastException

Not sure why this is happening but you may need to create the interceptor
chain manually to use a prototype, as TransactionProxyFactoryBean propably
assumes it's dealing with a singleton. So you need to create a chain that
includes:
- the name of your prototype
- the interceptor names, which may be singletons or prototypes as you
require. Use a prototype for mixin support.

The following example comes from the test suite, with minor changes to make
it more obvious:


<bean id="prototypeTarget"
class="org.springframework.aop.interceptor.SideEffectBean"
 singleton="false">
 <property name="count"><value>10</value></property>
</bean>

<!-- This can be a singleton or a prototype (for mixin behaviour) -->
<bean id="debugInterceptor"
class="org.springframework.aop.interceptor.DebugInterceptor">
</bean>


<bean id="prototype"
 class="org.springframework.aop.framework.ProxyFactoryBean">
 <!-- will automatically create invoker interceptor for the prototype -->
 <property
name="interceptorNames"><value>debugInterceptor,prototypeTarget</value></pro
perty>

<!-- Note this -->
 <property name="singleton"><value>false</value></property>
</bean>

There is a bug in M2 to do with prototype AOP handling, which is fixed in
the forthcoming M3. However I don't think it should affect you in such a
simple usage.


Regards,
Rod

[Springframework-developer] Intercepting a Prototype Bean

[MacMahon, M. <M.M...@em...>]

Hi all,	

Is it possible to apply an interceptor to a prototype bean?

The prototype is stateful - i.e one per user

I have defined the following in applicationContext.xml


<bean id="TestTarget" class="test.MyTarget" singleton="false">
</bean>


<bean id="TestInterceptor"
class="org.springframework.transaction.interceptor.TransactionProxyFactoryBe
an" singleton="false">
	<property name="transactionManager"><ref
local="transactionManager"/></property>
	
	<property name="target"><ref local="TestTarget"/></property>

	
	<property name="transactionAttributes">
		<props>
			<prop key="foo">PROPAGATION_REQUIRED</prop>
		</props>
	</property>
</bean>    



When I invoke the method foo I get a ClassCastException


If I change the TestInterceptor to singleton="true", it works fine but the
bean is no longer a prototype!

Is this a bug or a feature?

Any help much appreciated,


Regards,

Mark.
____________________________________________________ 

emuse technologies 
U24 Trinity Enterprise Centre, Pearse Street, Dublin 2, Ireland.
Tel:  +353 (0)1 6717317 Fax:  +353 (0)1 6717319 
website: <http://www.emusetechnologies.com/> 
email:    in...@em... <mailto:in...@em...>
____________________________________________________ 

This message has been scanned for viruses using GroupShield for Exchange
Server.

CONFIDENTIALITY NOTICE - The information contained in this email message is
intended only for confidential use of the named recipient. If the reader is
not the intended recipient or the person responsible for delivering it to
the recipient, you are hereby notified that you have received this
communication in error and that any review, dissemination or copying of this
communication is strictly prohibited. If you have received this in error,
please notify the sender immediately.

The information, opinions and recommendations contained herein are and must
be construed solely as statements of opinion and not statements of fact. No
warranty, expressed or implied, as to the accuracy, timeliness,
completeness, merchantability or fitness for any particular purpose of any
such recommendation or information is given or made by emuse technologies in
any form or manner whatsoever.

Re: [Springframework-developer] AutoProxyCreator problem

[Rajeev K. <Ra...@cu...>]

Dmitry,

Nice!  A clever workaround.  Thanks for your suggestion.

regards,

Rajeev
----- Original Message -----
From: "Kopylenko, Dmitry" <dko...@su...>
To: "'Rajeev Kaul '" <Ra...@cu...>;
<spr...@li...>
Sent: Wednesday, November 19, 2003 5:16 PM
Subject: RE: [Springframework-developer] AutoProxyCreator problem


> As to your first problem, you would need to create a new instance of the
> BeanFactory
> Consider the following piece of code (taken from
> EnterpriseServices.createInvokerInterceptor() ):
>
> // Infinite cycle: tries to create the bean if we don't use a different
> factory
> ListableBeanFactoryImpl bf2 = new ListableBeanFactoryImpl();
> bf2.registerBeanDefinition(beanName, definition);
> cpii.setBeanFactory(bf2);
>
> ...where cpii is the reference of type AbstractPoolingInvokerInterceptor
> which extends PrototypeInvokerInterceptor
>
> I guess this is what you need.
>
> Dmitriy.
>
> -----Original Message-----
> From: Rajeev Kaul
> To: spr...@li...
> Sent: 11/19/2003 7:33 PM
> Subject: Re: [Springframework-developer] AutoProxyCreator problem
>
> I am thinking of a solution for condensing the verbose configuration
> (shown below) for prototype business logic beans I am using in my
> application.  A shared controller instance (singelton) creates the
> business logic bean.  However the business logic bean must be
> instantiated per each thread that runs through the shared controller.  I
> have been using the configuration shown below:
>
>
> <bean id="prototypeBean" class="xyz.BusLogicBean" singleton="false">
>
> <property name="count"><value>10</value></property>
>
> </bean>
>
> <bean id="prototypeInvokerInterceptor"
> class="org.springframework.aop.interceptor.PrototypeInvokerInterceptor">
>
>
> <property name="targetBeanName"><value>prototypeBean</value></property>
>
> </bean>
>
> <bean id="prototype"
> class="org.springframework.aop.framework.ProxyFactoryBean">
>
> <property
> name="interceptorNames"><value>prototypeInvokerInterceptor</value></prop
> erty>
>
> </bean>
>
>
>
> As you can see this is very verbose, especially if you have a lot of
> these business logic beans in your application.  I tried using a derived
> version of BeanNameAutoProxyCreator to solve this, but ran into
> problems. I would like to replace this configuration with something
> shown below:
>
>
>
> <bean id="prototypeBean" class="xyz.BusLogicBean" singleton="false"
> proxy="prototype">
>
> <property name="count"><value>10</value></property>
>
> </bean>
>
> This would involve adding a "PROXY" attribute which would specify the
> type of proxy interceptor desired for the bean.  For example,
> "prototype" would mean ProxyFactoryBean with
> PrototypeInvokerInterceptor, "default" would mean ProxyFactoryBean with
> InvokerInterceptor, etc.  In loadBeanDefinition() method of the
> XmlBeanFactory class, the supporting proxy classes (ProxyFactoryBean
> and PrototypeInvokerInterceptor) could be automatically generated and
> registered.
>
> Any suggestions, comments, ...?
>
>
>
> Rajeev
>
> ----- Original Message -----
> From: Rajeev Kaul <mailto:Ra...@cu...>
> To: spr...@li...
> <mailto:spr...@li...>
> Sent: Tuesday, November 18, 2003 1:29 PM
> Subject: [Springframework-developer] AutoProxyCreator problem
>
>
> I have been trying to use BeanNameAutoProxyCreator class (I noticed
> there are no test cases for it) to create proxies for "prototype"
> business objects. I extended the BeanNameAutoProxyCreator class to use
> the PrototypeInvokerInterceptor in the "createInvokerInterceptor()"
> method.  However, this results in an infinite loop, as the
> PrototypeInvokerInterceptor calls the beanFactory getBean() method which
> in turn triggers the beanPostProcessor and the cycle repeats endlessly.
>
> Any suggestions on getting around this problem?
>
> It would have been better, if the BeanNameAutoProxyCreator class was
> designed to take invokerInterceptor as a property, which could be
> specified in the configuration, instead of having to subclass it to use
> other invokerInterceptor(s).
>
> Rajeev Kaul
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer

[Springframework-developer] RegexpMethodPointcutAroundAdvisor

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

Everyone,

I've added convenient class called RegexpMethodPointcutAroundAdvisor which
makes it easier to define RegexpMethodPointcuts and associate them with
Interceptors.

Regards,
Dmitriy. 

RE: [Springframework-developer] AutoProxyCreator problem

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

As to your first problem, you would need to create a new instance of the
BeanFactory
Consider the following piece of code (taken from
EnterpriseServices.createInvokerInterceptor() ):

// Infinite cycle: tries to create the bean if we don't use a different
factory
ListableBeanFactoryImpl bf2 = new ListableBeanFactoryImpl();
bf2.registerBeanDefinition(beanName, definition);
cpii.setBeanFactory(bf2);

...where cpii is the reference of type AbstractPoolingInvokerInterceptor
which extends PrototypeInvokerInterceptor

I guess this is what you need.

Dmitriy.

-----Original Message-----
From: Rajeev Kaul
To: spr...@li...
Sent: 11/19/2003 7:33 PM
Subject: Re: [Springframework-developer] AutoProxyCreator problem

I am thinking of a solution for condensing the verbose configuration
(shown below) for prototype business logic beans I am using in my
application.  A shared controller instance (singelton) creates the
business logic bean.  However the business logic bean must be
instantiated per each thread that runs through the shared controller.  I
have been using the configuration shown below:
 
 
<bean id="prototypeBean" class="xyz.BusLogicBean" singleton="false"> 

<property name="count"><value>10</value></property>

</bean>

<bean id="prototypeInvokerInterceptor"
class="org.springframework.aop.interceptor.PrototypeInvokerInterceptor">


<property name="targetBeanName"><value>prototypeBean</value></property>

</bean>

<bean id="prototype"
class="org.springframework.aop.framework.ProxyFactoryBean"> 

<property
name="interceptorNames"><value>prototypeInvokerInterceptor</value></prop
erty>

</bean>

 

As you can see this is very verbose, especially if you have a lot of
these business logic beans in your application.  I tried using a derived
version of BeanNameAutoProxyCreator to solve this, but ran into
problems. I would like to replace this configuration with something
shown below:

 

<bean id="prototypeBean" class="xyz.BusLogicBean" singleton="false"
proxy="prototype"> 

<property name="count"><value>10</value></property>

</bean>

This would involve adding a "PROXY" attribute which would specify the
type of proxy interceptor desired for the bean.  For example,
"prototype" would mean ProxyFactoryBean with
PrototypeInvokerInterceptor, "default" would mean ProxyFactoryBean with
InvokerInterceptor, etc.  In loadBeanDefinition() method of the
XmlBeanFactory class, the supporting proxy classes (ProxyFactoryBean
and PrototypeInvokerInterceptor) could be automatically generated and
registered.

Any suggestions, comments, ...?

 

Rajeev

----- Original Message ----- 
From: Rajeev Kaul <mailto:Ra...@cu...>  
To: spr...@li...
<mailto:spr...@li...>  
Sent: Tuesday, November 18, 2003 1:29 PM
Subject: [Springframework-developer] AutoProxyCreator problem


I have been trying to use BeanNameAutoProxyCreator class (I noticed
there are no test cases for it) to create proxies for "prototype"
business objects. I extended the BeanNameAutoProxyCreator class to use
the PrototypeInvokerInterceptor in the "createInvokerInterceptor()"
method.  However, this results in an infinite loop, as the
PrototypeInvokerInterceptor calls the beanFactory getBean() method which
in turn triggers the beanPostProcessor and the cycle repeats endlessly.
 
Any suggestions on getting around this problem?
 
It would have been better, if the BeanNameAutoProxyCreator class was
designed to take invokerInterceptor as a property, which could be
specified in the configuration, instead of having to subclass it to use
other invokerInterceptor(s). 
 
Rajeev Kaul

RE: [Springframework-developer] AutoProxyCreator problem

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

I guess this could also be solved with source-level metadata and
'enterpriseservices' aouto proxy creation mechanism. Anyone, comments?

Dmitriy.

-----Original Message-----
From: Rajeev Kaul
To: spr...@li...
Sent: 11/19/2003 7:33 PM
Subject: Re: [Springframework-developer] AutoProxyCreator problem

I am thinking of a solution for condensing the verbose configuration
(shown below) for prototype business logic beans I am using in my
application.  A shared controller instance (singelton) creates the
business logic bean.  However the business logic bean must be
instantiated per each thread that runs through the shared controller.  I
have been using the configuration shown below:
 
 
<bean id="prototypeBean" class="xyz.BusLogicBean" singleton="false"> 

<property name="count"><value>10</value></property>

</bean>

<bean id="prototypeInvokerInterceptor"
class="org.springframework.aop.interceptor.PrototypeInvokerInterceptor">


<property name="targetBeanName"><value>prototypeBean</value></property>

</bean>

<bean id="prototype"
class="org.springframework.aop.framework.ProxyFactoryBean"> 

<property
name="interceptorNames"><value>prototypeInvokerInterceptor</value></prop
erty>

</bean>

 

As you can see this is very verbose, especially if you have a lot of
these business logic beans in your application.  I tried using a derived
version of BeanNameAutoProxyCreator to solve this, but ran into
problems. I would like to replace this configuration with something
shown below:

 

<bean id="prototypeBean" class="xyz.BusLogicBean" singleton="false"
proxy="prototype"> 

<property name="count"><value>10</value></property>

</bean>

This would involve adding a "PROXY" attribute which would specify the
type of proxy interceptor desired for the bean.  For example,
"prototype" would mean ProxyFactoryBean with
PrototypeInvokerInterceptor, "default" would mean ProxyFactoryBean with
InvokerInterceptor, etc.  In loadBeanDefinition() method of the
XmlBeanFactory class, the supporting proxy classes (ProxyFactoryBean
and PrototypeInvokerInterceptor) could be automatically generated and
registered.

Any suggestions, comments, ...?

 

Rajeev

----- Original Message ----- 
From: Rajeev Kaul <mailto:Ra...@cu...>  
To: spr...@li...
<mailto:spr...@li...>  
Sent: Tuesday, November 18, 2003 1:29 PM
Subject: [Springframework-developer] AutoProxyCreator problem


I have been trying to use BeanNameAutoProxyCreator class (I noticed
there are no test cases for it) to create proxies for "prototype"
business objects. I extended the BeanNameAutoProxyCreator class to use
the PrototypeInvokerInterceptor in the "createInvokerInterceptor()"
method.  However, this results in an infinite loop, as the
PrototypeInvokerInterceptor calls the beanFactory getBean() method which
in turn triggers the beanPostProcessor and the cycle repeats endlessly.
 
Any suggestions on getting around this problem?
 
It would have been better, if the BeanNameAutoProxyCreator class was
designed to take invokerInterceptor as a property, which could be
specified in the configuration, instead of having to subclass it to use
other invokerInterceptor(s). 
 
Rajeev Kaul

Re: [Springframework-developer] AutoProxyCreator problem

[Rajeev K. <Ra...@cu...>]

I am thinking of a solution for condensing the verbose configuration =
(shown below) for prototype business logic beans I am using in my =
application.  A shared controller instance (singelton) creates the =
business logic bean.  However the business logic bean must be =
instantiated per each thread that runs through the shared controller.  I =
have been using the configuration shown below:


<bean id=3D"prototypeBean" class=3D"xyz.BusLogicBean" =
singleton=3D"false">=20

<property name=3D"count"><value>10</value></property>

</bean>



<bean id=3D"prototypeInvokerInterceptor" =
class=3D"org.springframework.aop.interceptor.PrototypeInvokerInterceptor"=
>=20

<property =
name=3D"targetBeanName"><value>prototypeBean</value></property>

</bean>


<bean id=3D"prototype" =
class=3D"org.springframework.aop.framework.ProxyFactoryBean">=20

<property =
name=3D"interceptorNames"><value>prototypeInvokerInterceptor</value></pro=
perty>


</bean>



As you can see this is very verbose, especially if you have a lot of =
these business logic beans in your application.  I tried using a derived =
version of BeanNameAutoProxyCreator to solve this, but ran into =
problems. I would like to replace this configuration with something =
shown below:



<bean id=3D"prototypeBean" class=3D"xyz.BusLogicBean" =
singleton=3D"false" proxy=3D"prototype">=20

<property name=3D"count"><value>10</value></property>

</bean>

This would involve adding a "PROXY" attribute which would specify the =
type of proxy interceptor desired for the bean.  For example, =
"prototype" would mean ProxyFactoryBean with =
PrototypeInvokerInterceptor, "default" would mean ProxyFactoryBean with =
InvokerInterceptor, etc.  In loadBeanDefinition() method of the =
XmlBeanFactory class, the supporting proxy classes (ProxyFactoryBean  =
and PrototypeInvokerInterceptor) could be automatically generated and =
registered.

Any suggestions, comments, ...?



Rajeev

  ----- Original Message -----=20
  From: Rajeev Kaul=20
  To: spr...@li...=20
  Sent: Tuesday, November 18, 2003 1:29 PM
  Subject: [Springframework-developer] AutoProxyCreator problem


  I have been trying to use BeanNameAutoProxyCreator class (I noticed =
there are no test cases for it) to create proxies for "prototype" =
business objects. I extended the BeanNameAutoProxyCreator class to use =
the PrototypeInvokerInterceptor in the "createInvokerInterceptor()" =
method.  However, this results in an infinite loop, as the =
PrototypeInvokerInterceptor calls the beanFactory getBean() method which =
in turn triggers the beanPostProcessor and the cycle repeats endlessly.

  Any suggestions on getting around this problem?

  It would have been better, if the BeanNameAutoProxyCreator class was =
designed to take invokerInterceptor as a property, which could be =
specified in the configuration, instead of having to subclass it to use =
other invokerInterceptor(s).=20

  Rajeev Kaul

Re: [Springframework-developer] how to determine if a bean exists in registry?

[Rajeev K. <Ra...@cu...>]

Why can't we use beanDefinitionMap.containsKey(beanName) in the
ListableBeanFactoryImpl?


----- Original Message -----
From: "Kopylenko, Dmitry" <dko...@su...>
To: "'Rod Johnson '" <rod...@in...>;
<spr...@li...>
Sent: Wednesday, November 19, 2003 3:05 PM
Subject: RE: [Springframework-developer] how to determine if a bean exists
in registry?


> I would say the impl. for such method would use
> AbstractBeanFactory.getBeanDefinition(String) call, catch
> NoSuchBeanDefinitionException and return false, otherwise return true.
>
> Dmitriy.
>
> -----Original Message-----
> From: Rod Johnson
> To: spr...@li...
> Sent: 11/19/2003 5:15 PM
> Subject: Re: [Springframework-developer] how to determine if a bean exists
> in registry?
>
> >It would still make sense to add a containsBean method to BeanFactory,
> I
> guess, to avoid workarounds like isSingleton or getAliases checks. If
> noone
> objects, I'll do that - is that OK with you, Darren? Rod, what do you
> think?
>
> This makes sense so long as the bean won't be instantiated by that call.
> Otherwise getBean() with a catch block would work.
>
> R
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer

[Springframework-developer] FW: Spring logical modules

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

To the list...

-----Original Message-----
From: j=FCrgen h=F6ller [werk3AT]
To: Kopylenko, Dmitry; al...@jt...; Kopylenko, Dmitry; Rod Johnson; =
Colin
Sampaleanu; Trevor Cook; Thomas Risberg; dar...@hs...; =
Luke
Taylor; mpo...@sp...; Tony Falabella
Sent: 11/19/2003 4:11 PM
Subject: Re: Spring logical modules

I like the idea of modules for documentation and marketing purposes =
too,
although we still need to discuss the naming, as we will have to stick
with what we choose for quite a while. We shouldn't try to get too
fine-granular, I guess.
=20
Regarding validation: The validation.ObjectError class has a dependency
on context.MessageSourceResolvable, therefore doesn't belong to core =
but
rather to context/container.
=20
Regarding web MVC: I'd rather call this SpringWeb or something similar,
as it isn't purely about web MVC but also offers a lot for use with
other web frameworks.
=20
Juergen
=20

________________________________

Von: Kopylenko, Dmitry [mailto:dko...@ac...]
Gesendet: Mi 19.11.2003 19:11
An: 'al...@jt...'; Kopylenko, Dmitry; 'Rod Johnson'; j=FCrgen =
h=F6ller
[werk3AT]; 'Colin Sampaleanu'; 'Trevor Cook'; 'Thomas Risberg';
'dar...@hs...'; 'Luke Taylor'; 'mpo...@sp...';
'Tony Falabella'
Betreff: RE: Spring logical modules


So the logical modules names is a good idea. Ok. So validation could be
part of SpringCore and remoting, jndi, mail, ejb part of SpringJ2EE
=20
JIRA - I've got the open source license. Also Mike sent me an email =
last
week saying that they will install Spring instance on their server some
time this week (they've upgraded to the latest version of 2.5) So if I
don't hear from him by the end of this week, I'll contact him. We're
almost there :-)
=20
Dmitriy.

	-----Original Message-----
	From: Alef Arendsen (JTeam) [mailto:al...@jt...]=20
	Sent: Wednesday, November 19, 2003 12:40 PM
	To: 'Kopylenko, Dmitry'; 'Rod Johnson'; 'j=FCrgen h=F6ller
[werk3AT]'; 'Colin Sampaleanu'; 'Trevor Cook'; 'Thomas Risberg';
dar...@hs...; 'Luke Taylor'; mpo...@sp...; 'Tony
Falabella'
	Subject: RE: Spring logical modules
=09
=09
	Sounds good.=20
	=20
	When creating the initial structure for the reference
documentation (on which I hope to spend some time coming weekend), I =
had
almost the same structure except for the following:
	=20
	SpringContainer split into beans and context (but it seems
logical to see it as one)
	SpringDAO split into JDBC and ORM (idem)
	=20
	Furtermore I had a separate chapter for validation (part of
SpringCore??), email and remoting (but those being part of J2EE is fine
with me).
	=20
	How's the JIRA thing going by the way?
	=20
	alef
	=20

		-----Oorspronkelijk bericht-----
		Van: Kopylenko, Dmitry
[mailto:dko...@ac...]=20
		Verzonden: Wednesday, November 19, 2003 6:04 PM
		Aan: 'Rod Johnson (rod...@in...)';
'j=FCrgen h=F6ller [werk3AT]'; 'Colin Sampaleanu'; 'Trevor Cook'; =
'Thomas
Risberg'; 'al...@jt...'; 'dar...@hs...'; 'Luke Taylor';
'mpo...@sp...'; 'Tony Falabella'
		Onderwerp: Spring logical modules
	=09
	=09

		Helo everyone,=20

		Here is the proposal to use "logical" modules (just
names) of the Spring framework grouped by functional area=20
		analogous to JBoss's logical modules e.g. JBossMX,
JBossNS, JBossTX etc. Then these module names could be used in
documentation,

		marketing and as JIRA components.=20

		Modules:=20

		* SpringAOP (aop framework)=20
		* SpringContainer (beans, context packages)=20
		* SpringCore (core, util packages)=20
		* SpringDAO (dao, jdbc, orm packages)=20
		* SpringMVC (web packages)=20
		* SpringTX (transaction infrastructure)=20
		* SpringMetadata (metadata packages)=20
		* SpringJ2EE (jndi, mail packages)=20

		Anything else? Any comments/ideas?=20

		Regards,=20
		Dmitriy.=20

RE: [Springframework-developer] how to determine if a bean exists in registry?

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

I would say the impl. for such method would use
AbstractBeanFactory.getBeanDefinition(String) call, catch
NoSuchBeanDefinitionException and return false, otherwise return true.

Dmitriy. 

-----Original Message-----
From: Rod Johnson
To: spr...@li...
Sent: 11/19/2003 5:15 PM
Subject: Re: [Springframework-developer] how to determine if a bean exists
in registry?

>It would still make sense to add a containsBean method to BeanFactory,
I
guess, to avoid workarounds like isSingleton or getAliases checks. If
noone
objects, I'll do that - is that OK with you, Darren? Rod, what do you
think?

This makes sense so long as the bean won't be instantiated by that call.
Otherwise getBean() with a catch block would work.

R




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] how to determine if a bean exists in registry?

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

>It would still make sense to add a containsBean method to BeanFactory, I
guess, to avoid workarounds like isSingleton or getAliases checks. If noone
objects, I'll do that - is that OK with you, Darren? Rod, what do you think?

This makes sense so long as the bean won't be instantiated by that call.
Otherwise getBean() with a catch block would work.

R

RE: [Springframework-developer] RedirectView

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

I've commited it this morning. Could help the temptation ;-)

Dmitriy.

-----Original Message-----
From: j=FCrgen h=F6ller [werk3AT]
To: spr...@li...
Sent: 11/19/2003 4:29 PM
Subject: Re: [Springframework-developer] RedirectView

+1 - and do it quickly, 1.0 M3 is just around the corner :-)
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag
von Trevor Cook
Gesendet: Mi 19.11.2003 22:30
An: spr...@li...
Betreff: RE: [Springframework-developer] RedirectView


+1 That's what I use (and what the jaf api recommends)
=20
Trevor

	-----Original Message-----
	From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Kopylenko, Dmitry
	Sent: November 18, 2003 2:07 PM
	To: 'spr...@li...'
	Subject: [Springframework-developer] RedirectView
=09
=09

	Everyone,=20

	In org.springframework.web.servlet.view.RedirectView=20

	Line 71:
url.append(URLEncoder.encode(entry.getKey().toString());=20
	Line 73:
url.append(URLEncoder.encode(entry.getValue().toString()));=20

	URLEncoder.encode(String) is deprecated. Does anyone mind if I
change it to url.append(URLEncoder.encode(entry.getKey().toString(),
"UTF-8"))

	 and url.append(URLEncoder.encode(entry.getValue().toString(),
"UTF-8")) respectively ?=20

	Regards,=20
	Dmitriy.=20



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] RedirectView

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

+1 - and do it quickly, 1.0 M3 is just around the corner :-)
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Trevor Cook
Gesendet: Mi 19.11.2003 22:30
An: spr...@li...
Betreff: RE: [Springframework-developer] RedirectView


+1 That's what I use (and what the jaf api recommends)
=20
Trevor

	-----Original Message-----
	From: spr...@li... =
[mailto:spr...@li...]On Behalf =
Of Kopylenko, Dmitry
	Sent: November 18, 2003 2:07 PM
	To: 'spr...@li...'
	Subject: [Springframework-developer] RedirectView
=09
=09

	Everyone,=20

	In org.springframework.web.servlet.view.RedirectView=20

	Line 71: url.append(URLEncoder.encode(entry.getKey().toString());=20
	Line 73: url.append(URLEncoder.encode(entry.getValue().toString()));=20

	URLEncoder.encode(String) is deprecated. Does anyone mind if I change =
it to url.append(URLEncoder.encode(entry.getKey().toString(), "UTF-8"))

	 and url.append(URLEncoder.encode(entry.getValue().toString(), =
"UTF-8")) respectively ?=20

	Regards,=20
	Dmitriy.=20

RE: [Springframework-developer] RedirectView

[Trevor C. <pr...@se...>]

RedirectView+1 That's what I use (and what the jaf api recommends)

Trevor
  -----Original Message-----
  From: spr...@li...
[mailto:spr...@li...]On Behalf Of
Kopylenko, Dmitry
  Sent: November 18, 2003 2:07 PM
  To: 'spr...@li...'
  Subject: [Springframework-developer] RedirectView


  Everyone,

  In org.springframework.web.servlet.view.RedirectView

  Line 71: url.append(URLEncoder.encode(entry.getKey().toString());
  Line 73: url.append(URLEncoder.encode(entry.getValue().toString()));

  URLEncoder.encode(String) is deprecated. Does anyone mind if I change it
to url.append(URLEncoder.encode(entry.getKey().toString(), "UTF-8"))

   and url.append(URLEncoder.encode(entry.getValue().toString(), "UTF-8"))
respectively ?

  Regards,
  Dmitriy.

Re: [Springframework-developer] how to determine if a bean exists in registry?

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

Why not use ListableBeanFactory's getBeanDefinitionNames method? If the =
returned String array contains the bean name, then it is available in =
the factory.
=20
It would still make sense to add a containsBean method to BeanFactory, I =
guess, to avoid workarounds like isSingleton or getAliases checks. If =
noone objects, I'll do that - is that OK with you, Darren? Rod, what do =
you think?
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Kopylenko, Dmitry
Gesendet: Mi 19.11.2003 21:46
An: 'spr...@li...'
Betreff: RE: [Springframework-developer] how to determine if a bean =
exists in registry?


If there is a big demand for such a "query" method I could add it to =
BeanFactory or AbstractBeanFactory. What everybody thinks?
=20
Dmitriy.

	-----Original Message-----
	From: Rajeev Kaul [mailto:Ra...@cu...]=20
	Sent: Wednesday, November 19, 2003 3:42 PM
	To: spr...@li...
	Subject: Re: [Springframework-developer] how to determine if a bean =
exists in registry?
=09
=09
	 Although, I would still prefer a simpler method that just returns a =
boolean, but your solution will work for me.
	=20
	Thanks!!!!
	=20
	=20
	----- Original Message -----=20

		From: Dmitriy Kopylenko <mailto:dko...@ru...> =20
		To: spr...@li...=20
		Sent: Wednesday, November 19, 2003 11:15 AM
		Subject: RE: [Springframework-developer] how to determine if a bean =
exists in registry?

		Or better yet use AbstractBeanFactory.getBeanDefinition(String =
beanName) which would throw NoSuchBeanDefinitionException if bean does =
not exist.
		=20
		Regards,
		Dmitriy.

			-----Original Message-----
			From: spr...@li... =
[mailto:spr...@li...] On Behalf =
Of Kopylenko, Dmitry
			Sent: Wednesday, November 19, 2003 2:08 PM
			To: 'spr...@li...'
			Subject: RE: [Springframework-developer] how to determine if a bean =
exists in registry?
		=09
		=09
			Rajeev,
			=20
			you could use String[] getAliases(String name) throws =
NoSuchBeanDefinitionException in BeanFactory and catch =
NoSuchBeanDefinitionException. If caught, then bean does not exist in =
the factory.
			=20
			Dmitriy.

				-----Original Message-----
				From: Rajeev Kaul [mailto:Ra...@cu...]=20
				Sent: Wednesday, November 19, 2003 1:54 PM
				To: spr...@li...
				Subject: [Springframework-developer] how to determine if a bean =
exists in registry?
			=09
			=09
				Is there an easy way to determine if a certain bean exists in the =
beanFactory?  I know one can use the getBean(name) to determine that, =
but it seems an expensive call,  especially, if there are bean post =
processors associated with it.  Don't you think having a function like   =
 boolean containsBean(String beanName) in a beanFactory class would be =
useful here?
				=20
				Rajeev Kaul
			=09

RE: [Springframework-developer] how to determine if a bean exists in registry?

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

If there is a big demand for such a "query" method I could add it to
BeanFactory or AbstractBeanFactory. What everybody thinks?
 
Dmitriy.

-----Original Message-----
From: Rajeev Kaul [mailto:Ra...@cu...] 
Sent: Wednesday, November 19, 2003 3:42 PM
To: spr...@li...
Subject: Re: [Springframework-developer] how to determine if a bean exists
in registry?


 Although, I would still prefer a simpler method that just returns a
boolean, but your solution will work for me.
 
Thanks!!!!
 
 
----- Original Message ----- 

From: Dmitriy  <mailto:dko...@ru...> Kopylenko 
To: spr...@li...
<mailto:spr...@li...>  
Sent: Wednesday, November 19, 2003 11:15 AM
Subject: RE: [Springframework-developer] how to determine if a bean exists
in registry?

Or better yet use AbstractBeanFactory.getBeanDefinition(String beanName)
which would throw NoSuchBeanDefinitionException if bean does not exist.
 
Regards,
Dmitriy.

-----Original Message-----
From: spr...@li...
<mailto:spr...@li...>
[mailto:spr...@li...] On Behalf Of
Kopylenko, Dmitry
Sent: Wednesday, November 19, 2003 2:08 PM
To: 'spr...@li...'
Subject: RE: [Springframework-developer] how to determine if a bean exists
in registry?


Rajeev,
 
you could use String[] getAliases(String name) throws
NoSuchBeanDefinitionException in BeanFactory and catch
NoSuchBeanDefinitionException. If caught, then bean does not exist in the
factory.
 
Dmitriy.

-----Original Message-----
From: Rajeev Kaul [mailto:Ra...@cu...] 
Sent: Wednesday, November 19, 2003 1:54 PM
To: spr...@li...
Subject: [Springframework-developer] how to determine if a bean exists in
registry?


Is there an easy way to determine if a certain bean exists in the
beanFactory?  I know one can use the getBean(name) to determine that, but it
seems an expensive call,  especially, if there are bean post processors
associated with it.  Don't you think having a function like    boolean
containsBean(String beanName) in a beanFactory class would be useful here?
 
Rajeev Kaul