Well, looks like the persistence context is flushed before you execute that query, because
the query touches entities that have been modified. Either enable cascading persist on the
association from Category to Application (I'm guessing here that this is the
association in question), or call persist() on the Category instance before
flushing/querying, or disable automatic flushing with FlushModeType.MANUAL by using a
Seam-managed persistence context.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067373#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...