Databases
StackOverflow2013
Postsdbo
POHibernate 3.5-Final in JBoss 5.1.0.GA
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHibernate 3.5-Final in JBoss 5.1.0.GA
    primarykey
    data
    text
    <p><a href="http://relation.to/Bloggers/Hibernate350FinalRelease" rel="noreferrer">Hibernate 3.5-Final</a> is finally here and it offers the much anticipated JPA2 support, amongst other features. I am working on a project(EJB3 based) using JBoss 5.1.0.GA and Hibernate 3.3, but I wanted to take advantage of the JPA2 and tried to upgrade to Hibernate 3.5.</p> <p>What I did was fairly simple and standard - I just put all the hibernate 3.5 jars in the server/configuration(default,all,etc)/lib folder - that way they take precedence over the hibernate artifacts shipped with JBoss. It seems though that JBoss ships with libraries that are dependent on the JPA1 implementation part of the hibernate 3.3, because I started getting some errors about unimplemented abstract methods and stuff like that on deploy:</p> <pre><code> 23:21:26,792 WARN [Ejb3Configuration] Persistence provider caller does not implement the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null. 23:21:26,792 ERROR [AbstractKernelController] Error installing to Start: name=persistence.unit:unitName=kernel-ear-3.3.0-SNAPSHOT.ear/config-persistence.jar#ConfigurationPersistenceUnit state=Create java.lang.AbstractMethodError: org.jboss.jpa.deployment.PersistenceUnitInfoImpl.getValidationMode()Ljavax/persistence/ValidationMode; at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:613) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:72) at org.jboss.jpa.deployment.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:301) at sun.reflect.GeneratedMethodAccessor308.invoke(Unknown Source) </code></pre> <p>Maybe I should use a different persistence provided? Currently it's:</p> <blockquote> <p>org.hibernate.ejb.HibernatePersistence</p> </blockquote> <p>I looked around the net and didn't find any documented upgrade paths. There was even an unanswered question here in stack overflow on the topic. </p> <p>Any ideas, suggestions? Thanks in advance for your help. </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPascal Thivent
    1. USBozhidar Batsov
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHibernate 3.5-Final in JBoss 5.1.0.GA
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHibernate 3.5-Final in JBoss 5.1.0.GA
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHibernate 3.5-Final in JBoss 5.1.0.GA
      1. This table or related slice is empty.
      1. VTUpMod
    1. COUpgrading Hibernate within JBossAS is rarely easy, as you've discovered. The inter-dependencies are just too tight for all but the most trivial JBoss configurations.
      singulars
      1. POHibernate 3.5-Final in JBoss 5.1.0.GA
      1. USskaffman
    2. COhi, were you able to resolve this? I am after doing something same and facing lot of difficulties.
      singulars
      1. POHibernate 3.5-Final in JBoss 5.1.0.GA
      1. USadi
    3. COTry using a diferent name for your persistence.xml file, like foo-persistence.xml
      singulars
      1. POHibernate 3.5-Final in JBoss 5.1.0.GA
      1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload