[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2476) Verify and attempt to use EAR/WAR ANTLR lib rather than weblogic 10's lib for examples in reference doc

[Max Andersen (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-2476?page=comments#action_12394463 ] 
            
Max Andersen commented on JBSEAM-2476:
--------------------------------------

>From Hibernate 3 Migration guide comments on hibernate.org:

"No problems with WebLogic, the only issue is that WLS has a configurable
Classloader behaviour and, by default, is not the one used by Tomcat
(with WEB-INF/lib before System Classpath). 
Infact it's enough to use the <prefer-web-inf-lib> tag in 8.1 (or the
appropriate flag in 6.1) and all will works great !!!!
Hope this can help."

I did not try it but worth a shot.

btw. I did not not classicquerytranslator had performance issues - I thought it was only about not having all the features of HQL available.

> Verify and attempt to use EAR/WAR ANTLR lib rather than weblogic 10's lib for examples in reference doc
> -------------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-2476
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2476
>             Project: JBoss Seam
>          Issue Type: Task
>          Components: Examples
>    Affects Versions: 2.0.1.GA
>         Environment: Weblogic 10.3.TP
>            Reporter: Jay Balunas
>            Priority: Minor
>
> Current reference guide chapter for weblogic uses the ClassicQueryTranslatorFactory for the hibernate properties in persistence.xml file.  This is listed as required because Weblogic ships with an older version of the ANTLR libraries.  First verify the ANTLR version.  If that is still a problem there may be a way to set a preference in the classloaders for libraries deployed in the EAR/WAR.  Using ClassicQueryTranslatorFactory causes performance issues with hibernate.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira