3 Replies Latest reply on Aug 15, 2005 2:31 PM by epbernard

    What the heck is broken? 4.0.3RC2

    elkner

      Just tried to deploy my app (which works without any problem in 4.0.3RC1) to 4.0.3RC2:

      2005-08-15 06:09:11,378 INFO [ScannerThread:org.hibernate.ejb.HibernatePersistence:330] - found EJB3 Entity bean: foo.A_Bar
      2005-08-15 06:09:11,671 WARN [ScannerThread:org.jboss.system.ServiceController:363] - Problem creating service jboss.j2ee:service=EJB3,module=fooBar.par
      org.hibernate.AnnotationException: referencedColumnName not mapped to a property is not supported: id,
       at org.hibernate.cfg.BinderHelper.createSyntheticPropertyReference(BinderHelper.java:106)
       at org.hibernate.cfg.AnnotationBinder.bindFkSecondPass(AnnotationBinder.java:1481)
       at org.hibernate.cfg.FkSecondPass.secondPass(FkSecondPass.java:37)
       at org.hibernate.cfg.FkSecondPass.doSecondPass(FkSecondPass.java:31)
       at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:215)
      


      What the heck is broken? Is there a way to find out the suspected entity?

      BTW: This is another case for bad log usage: Just dumping a silly stacktrace of several hundred lines buys nothing - I would prefer a warning, what says clearly, what's wrong and stacktraces only, if debug level is enabled (otherwise one has to search/analyze the logs for several hours, until one finds ? - nothing ...) grrrr

        • 1. Re: What the heck is broken? 4.0.3RC2
          epbernard

          I've enhanced the exception to give the appropriated referenced entity.

          In the meanwhile, you can search your relations using referencedColumnName="id" and having a referenced entity wo "id" column. Let me know if this is actually the case. Otherwise a minimal failing test case is very welcome.

          • 2. Re: What the heck is broken? 4.0.3RC2
            elkner

             

            "epbernard" wrote:
            I've enhanced the exception to give the appropriated referenced entity.


            Yepp. Looks better! Even better would be, to have the property owner listed as well. AFAIS it should be accessable via associatedClass ?

            BTW: In fact, it was a wrong referencedColumn value (typo error). Hmmm, wondering, why this was not encountered previously / had no side effects in earlier releases ...

            • 3. Re: What the heck is broken? 4.0.3RC2
              epbernard

              This release is the first to support referencedColumnName.