Christian, I'm not guessing. Here is my persistence.xml: <?xml version="1.0" encoding="UTF-8"?> | <persistence xmlns="..."> | <persistence-unit name="codename"> | <provider>org.hibernate.ejb.HibernatePersistence</provider> | <jta-data-source>java:/codenameDatasource</jta-data-source> | <properties> | <property name="hibernate.hbm2ddl.auto" value="update"/> | <property name="hibernate.show_sql" value="true"/> | <property name="jboss.entity.manager.factory.jndi.name" value="java:/codenameEntityManagerFactory"/> | </properties> | </persistence-unit> | </persistence> | There is single SQL statement in the log that looks similar to "select fields from table where parent_id=? and (isTemplate=0)". Nothing special. Is it enough to figure out what SQL is generated? As I wrote I'm going to analyze Facelets overhead. I'm intensively using source components. I think problem is in debug mode. In production mode it caches all the xhtmls. I like Seam. I found "Step Filters" in Eclipse. I hope it will help me to cope with debugging inter-EJB calls. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008242#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...