Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Virgo » Optional import of a hibernate's package unexpectedly became unresolved
Optional import of a hibernate's package unexpectedly became unresolved [message #1006711] Fri, 01 February 2013 09:18 Go to previous message
Anton Lem is currently offline Anton Lem
Messages: 11
Registered: January 2013
Junior Member
During a migration process my web-bundle unexpectedly threw the exception:
Could not instantiate bean class [com.liferay.portal.spring.hibernate.PortalHibernateConfiguration]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: org/hibernate/cfg/Configuration
at org.springframework.orm.hibernate3.LocalSessionFactoryBean.<init>(LocalSessionFactoryBean.java:189)

I turned up, that org.springframework.orm_3.1.0.RELEASE bundle discontinued to resolve the optional import org.hibernate.cfg;version="[3.2.0, 5.0.0)";resolution:="optional". I have my own handmade hibernate 3.6 distribution bundle but it was being successfully resolved earlier. I've removed the "optional" directive from the org.hibernate.cfg import in the spring.orm bundle, repacked the bundle and the exception has disappeared.
Although, I've found and fixed the problem I don't like my solution to repack an existing system bundle. And a sudden appearance of an unresolved package I don't like too. Is this a normal resolver's behavior and I misunderstand something or is this some kind of bug?
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic:[SOLVED] AspectJ Weaver error on @Aspect
Next Topic:Initial artifact vs plan deployed in pickup
Goto Forum:
  


Current Time: Sun May 19 06:25:12 EDT 2013

Powered by FUDForum. Page generated in 0.03015 seconds