This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
There is scope attribute for the setProperty nor getProperty. you introduce the bean using useBean and there you specify the scope. Now whenever you se/get a property, you will be working on a bean that you have introduced using the useBean. i.e there is no point in having the scope again for get/set properties.