Just a quick question: When defining @NamedQueries for jboss ejb3 entities, can I use old EJB-QL from our EJB2 Entity Beans
e.g
@NamedQuery(name="findAllApplications", query="SELECT OBJECT(application) FROM Application application")
Seem to be getting a lot of sytax errors reported:
No data type for node: org.hibernate.hql.ast.tree.IdentNode \-[ALIAS_REF] IdentNode: 'application' {alias=application, no from element}
It looks like it is expecting a HQL statement, however tons of the EJB3 tutorials online show NamedQueries containing the old EJB 2 finder syntax.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080584#4080584
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080584
Damien: yes, I can reproduce.
I don't think Vincent's patch will make it into Seam. Currently Seam serializes concurrent requests to Conversational scoped beans (failing if it has to wait longer that the concurrent-request-timeout).
Vincent's patch (afaics) alters this to allow concurrent access to conversational scoped beans (which IIRC will fail when accessing SFSBs) - though I'm not sure of Vincent's exact intention as he says he is serializing calls to getTotal - but I think he is actually parallelizing calls.
I need to spend some time looking at this part of Seam (I'm not overly familiar with it) and talk to Seam/Richfaces dev on this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080581#4080581
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080581