"bill.burke(a)jboss.com" wrote : When you deploy a component, it can have both dependencies as well as a precedence level. Basically the precedence level is a numerical value of where in the chain the component should be deployed. Gavin uses this so that somebody could say: "I want this component deployed after all Seam BUILT IN components". Just to clarify, precedence is actually used to say "I want this component used INSTEAD OF this other component (with the same name)". So if I had a built-in-to-seam component foo (precedence 0) and a component I had developed also called foo, but with precedence 40, my component would get used instead of the built in one (both by Seam and by my app). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008975#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...