anonymous wrote : From your point of view is what I am doing wrong or is it just another way to do the same things ? IMO, there is rarely a right/wrong way just better ways. For client configuration your way is better. The Java EE Client container can provide the same funtionality for you though in most cases (minus interceptors and XML reloading). The JBoss equivalent to Spring container is JBoss Microcontainer i fyou want to try that out. anonymous wrote : JNDI parameters are in XMLs, they can be changed easily. | Moving services from one EAR to another does not have impact on client source code but only on XMLs. Don't bash annotations. Using annotations are great for fast prototyping or generally providing default values for your injections. What I'm saying is that even if you use annotations, you can still override them in XML (web.xml, ejb-jar.xml, etc...) to provide the JNDI mappings you desire. The specifications also support partial XML deployment descriptors so it is real easy to override one env/ entry. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999064#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...