CharScanner; panic: ClassNotFoundException: org.hibernate.hq

jadeite1000 · **Joined:** Thu May 25, 2006 3:23 pm **Posts:** 12

Hi All:

tenwit · **Joined:** Thu Dec 23, 2004 9:08 pm **Posts:** 2008

In your hibernate.cfg.xml, anywhere inside the <session-factory> element, add this line:

Code:

<property name="hibernate.query.factory_class">org.hibernate.hql.classic.ClassicQueryTranslatorFactory</property>

I didn't know that weblogic conflicts with HqlToken. That's what you get for not going open source :)

jadeite1000 · **Joined:** Thu May 25, 2006 3:23 pm **Posts:** 12

tenwit wrote:

In your hibernate.cfg.xml, anywhere inside the <session-factory> element, add this line:

Code:

<property name="hibernate.query.factory_class">org.hibernate.hql.classic.ClassicQueryTranslatorFactory</property>

I didn't know that weblogic conflicts with HqlToken. That's what you get for not going open source :)

Hi All:

What does it mean when we use
<property name="hibernate.query.factory_class">org.hibernate.hql.classic.ClassicQueryTranslatorFactory</property>.
Does it mean our HQL will be compliant to Hibernate 2.1 or the HQL in the book "Hibernate In Action". Also what about the domain object and java classes, do we have to inherit a package related to hibernate classic?

steve · **Posted:** Tue May 30, 2006 2:27 pm

http://hibernate.org/250.html#A24

tenwit · **Joined:** Thu Dec 23, 2004 9:08 pm **Posts:** 2008

Using the classic HQL parser doesn't mean that you're using Hibernate 2.1, or any other "classic" stuff (org.hibernate.class.Session, for example). All it means that you are using the class HQL parser. This supports old-style aliasing ("from Table a join a.TableB as b"), though newer code doesn't allow that (you have to omit the "as"). Also, there's no support for insert, update or delete via classic HQL.

As Steve's link points out, the fix is known and will be resolved as other projects come up to speed. You'll only have to live with this for a short while.