Laird - This sounds pretty familiar, but I thought it has been fixed. Can you post snippets of your Entities?
Thanks, Rick On Tue, May 1, 2012 at 9:31 AM, Laird Nelson <ljnel...@gmail.com> wrote: > On Tue, May 1, 2012 at 9:57 AM, Laird Nelson <ljnel...@gmail.com> wrote: > > > I'm getting a stack trace on some integration tests after making the > > upgrade from 2.0.0 to 2.2.0. > > > > The code in question that triggers the stack: > > final TypedQuery<NameTypeEntity> query = > em.createNamedQuery(NameTypeEntity.NameTypeQuery.FIND_BY_CODE.getName(), > NameTypeEntity.class); > query.setParameter("code", CodeConstants.ALPHA_NAME); > NameTypeEntity ntype = query.getSingleResult(); > > In this case NameTypeEntity is an entity listed in persistence.xml in a > <class> element. The enum call just returns a name of a valid query. All > of this to say: these are valid entities, listed appropriately, and the > 2.0.0 version didn't have trouble here. > > The stack is triggered by the getSingleResult() call. > > Best, > Laird > > -- > http://about.me/lairdnelson > -- *Rick Curtis*