>-----Original Message----- >From: Adam Taft [mailto:[EMAIL PROTECTED] >It should be either one of two ways: > >a) <bean id="fooResource" scope="request" class="FooResource" /> > >b) <bean id="fooResource" scope="prototype" class="FooResource" /> > >-a- should "theoretically" work in a servlet environment (like >he's using). I say theoretically, because this is getting >into some edge case uses of spring. > >-b- would be the only reasonable choice outside of the servlet >environment or if things didn't work with -a-.
I'm going to switch back to "b" because "a" doesn't gain me anything in my case, so no good reason to add complexity. >Again, as mentioned, generating proxies on top of proxies will >likely lead to edge case goofiness and hard to track down >bugs, so pay particular attention to this. Interesting. I'm using lookup-method in production without any problems. But, there are no transactions and no other proxies so I guess we got lucky. Do the clashes only occur within the class or does it cause problems everywhere? In other words, am I safe if the resource class is not transactional, but is uses a service class that is? ....Michael
