Not much I can offer, I have never used the tomahawk tree component, and never seen that exception.
The problem seems related to having more than one component with the same name in the app: this sometimes makes strange things happen (perhaps depending on init order).
In knew it was something stupid I did...
Is there a way to have the name of the component appear in the logs together with the message that says "Seam component hides managed bean with the same name"?
No, not really. We should WARN when multiple Seam components have the same name, however.
Suddenly I stumbled upon another nice thing: the following query works:
from Tol t order by t.name
while the following doesn't work:
from Tol order by Tol.name
and the only clue you get is an error saying that the property "rowCount" is not available... which is caused by the error in the query, not by the absence of the object in the context (a missing object in the context passes unnoticed in the JSP).
Of course, the second thing is not a correct EJB-QL query.