Initially when I filed this issue, I thought it was simple to fix, but then I
realised that NamedQuery can be placed in two places like this:

@Entity
@NamedQuery(name="foo1", query="...)
public class Employee{...}


as well as
@Entity
@NamedQueries({@NamedQuery(name="bar1", query="...), @NamedQuery(name="bar2",
query="...)})
public class Employee{...}

It is not clear to me, how such cases are dealt. So assigning this to owner of
ORM model.

AFAIK ORMNNListener doesn't listen to NamedQuery at all. You need to either add
a NNMB mapping or a custom code if the NNMB is not capable to handle the case. I
would probably use JMI for the verification as a workaround.

An old issue - Andrei, is this resolved now?

Not fixed, I didn't know about this requirement. Not hard to fix, but unless it blocks a showstopper issue I see no
point in fixing it for 6.0.

Closing as wontfix, since I don't see an issue blocked by this one. Please reopen with details.