Hi Tom, hi Jielin,
attached you find a fix for issue 1236 "Need Better Message when Named
Query uses incorrect Entity Name":
https://glassfish.dev.java.net/issues/show_bug.cgi?id=1236
I added a new EJBQLException message used in case the abstract schema
type given in the FROM clause is not known. So a query "SELECT o FROM
Orders o" now results in an error message: Unknown abstract schema type
[Orders]
Jielin,
my fix may conflict with your change to fix 269, because I also changes
classes EJBQLException and EJBQLExceptionResource. So however checkins
second needs to adapt the error code in the two classes.
Thanks!
Regards Michael