Illegal type in constant pool

[angela]

hello!

i have exactly the same problem! My aop.xml looks like that:

<?xml version="1.0" encoding="UTF-8"?>
<!--  <!DOCTYPE aspectj  SYSTEM "/home/devuser/workspace/NDBJS_Re7/WebContent/WEB-INF/aspectj.dtd"> -->

<!DOCTYPE aspectj PUBLIC    
  "-//AspectJ//DTD//EN"    "http://www.eclipse.org/aspectj/dtd/aspectj.dtd">    

<aspectj>   
  <weaver 
    options="-showWeaveInfo -XmessageHandlerClass:org.springframework.aop.aspectj.AspectJWeaverMessageHandler">
    <include within="najsre7..*"/>
  </weaver> 
  
  <aspects>
    <include within="org.springframework.beans.factory.aspectj.AnnotationBeanConfigurerAspect"/>
  </aspects> 
</aspectj>

Exception:

java.lang.VerifyError: (class: org/hibernate/impl/SessionFactoryImpl, method: readResolve signature: ()Ljava/lang/Object;) Illegal type in constant pool
	at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294)
	at org.springframework.orm.hibernate3.LocalSessionFactoryBean.newSessionFactory(LocalSessionFactoryBean.java:728)

Any ideas?
Angela

[ksarantakos]

I do have a include within in there, but only in the META-INF of the main application war. In addition I have many other jar files that don't have aop.xml in their META-INFs and the war references these. I thought the main aop.xml from war would prevent the weaving of those too.

I try adding aop.xml to all my jars, and let you know what happens.

[angryangel9]

Hey there!

I have the same problem. First i had it with Log4j. Using the same log4j.jar file in ${catalina.home}/common/lib and in my webapp solved the problem with Log4j. But now i have the same error with hibernate as you have. Does anyone has found a solution for that? By now i'm sitting for three days on the error. Using a workaround instead of AspectJ would make my domain model very ugly. Maybe some of the Spring Guys have an answer?

Thanks in advance!

Regards Torben

[leonardoborges]

Anybody got past this?

I'm using spring 2.1-m4 and getting the Illegal type in constant pool while creating the session factory.

[ortizfabio]

jwijgerd,

Life saver answer I was missing the META-INF/aop.xml in my deployment and all the classes in the server were being process of course hibernate jar was different in the server. java.lang.VerificationError if you get that exception make sure your aop.xml is deployed.


Fabio

[al0]

I have used LTW for more then a year without any issues and then all from sudden this damned error (for log4j Logger) appeared on my development notebook (there are several Spring projects in different stages of development deploeyd into tomcat 5.5 and at the time being no one of them really uses AOP). Error appeared after redeployment of one of the projects. Nothing special.
All other prohjects start absolutely normally,

I have added aop.xml to the affected project excluding all clsees from weaving to no avail.

The only solution that I have found was to remove agent. But I do not like it as in a short time I would need it.

Any suggestions?

Regards,
Oleksandr