This is interesting behavior. Does anyone know if this is by design, and if it's also true in JSF 2 Facelets? Sounds like a bug to me, but I don't see it in the issue tracker (although I may have missed it). --- Kito D. Mann | twitter: kito99 | Author, JSF in Action Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info | twitter: jsfcentral +1 203-404-4848 x3 Sign up for the JSFCentral newsletter: http://oi.vresp.com/?fid=ac048d0e17 ---------- Forwarded message ---------- From: <havis(a)email.cz&gt; Date: Sun, Jan 31, 2010 at 12:02 PM Subject: [jsr-314-open] Composite components To: users(a)facelets.dev.java.net Hi Users, I'm comming here with such a trivial problem as the composite component is. But, I have one real problem with this. Imagine I've created simple panel component, i.e. named panelBox. My question is: "Is there a way to stop passing component attributes deep down to another one?" Code snippet to illustrate my problem: <my:panelBox style="border:1px solid red"> <my:panelBox/> </my:panelBox> Even if the second panelBox does not define attribute style, it inherits it from parent panelBox. That's the way, how Facelets using attribute searching mechanism. But, I don't realy want to set style attribute of first panelBox component to the second one. Is there a solution how to avoid this passing? Thx Tom