I have a Spring application that expose Rest API (implements with RestEasy) that deploy on JBoss, The client want to add security - implement by OAuth framework.

Does any one have experience with this type of configuration? 

Just recently, I was writing a little Spring-enabled http sampler (my next post), and I needed to introduce some values (hostname, port, ping url) from an outside configuration file. As I automatically used PropertyPlaceholderConfigurer (better known as <context:property-placeholder location="classpath:..." />), I noticed that only part of my problem was solved: the values taken from the configuration file could ONLY be injected into beans declared in my applicationContext.xml! This means that if I wanted to use Spring annotations for declaring beans (which I do), I had to write an "Adapter Beans", "Configuration Bean" or whatever name you want to call it... The Configuration bean would be declared in the xml file, and I'll @Autowire it to whatever other bean that needs that configuration...

Apparently, the @PostConstruct idiom in Spring / JSE isn't that well defined: If you have a service class annotated with @Transactional and a method defined as @PostConstruct tries to do transactional work (calling on DAOs, for instance), it will fail due to non existing transaction in context, sad as true.

Yeah, you could add some boolean init member and check it on every invocation of every service method, perhaps even via an interceptor, but why not use a new annotation that causes a method to get called after the object is fully initialized?

Well, high time to meet @PostInitialize. It'll do just that. Written by jbaruch, published on Spring forums and patched by yours truely:

http://forum.springsource.org/showthread.php?p=252616#post252616

Between their DM/OSGi server releases, the Spring guys found the time to develop what seems like a promising platform for round-trip development configuration tool called Spring Roo. The tool allows adding various features to a project, including auto generation of configurations, code and tests for various technologies and APIs. In short, Roo allows for development-time configuration similar to Spring's runtime DI...

have a peek at this recently added a step-by-step tutorial:

http://blog.springsource.com/2009/05/27/roo-part-2/