Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

On Mon, Apr 6, 2015 at 2:41 PM, Petar Tahchiev wrote: > Hi Steve, > > just tested - works like a charm. Thanks a ton :) The only 2 things left > for me are > 1) "[main] WARN : HHH72: Duplicate joins for class" - I'm not really > bothered with this one as it is a warning. > Like I mentioned e

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Hi Steve, just tested - works like a charm. Thanks a ton :) The only 2 things left for me are 1) "[main] WARN : HHH72: Duplicate joins for class" - I'm not really bothered with this one as it is a warning. 2) "TRACE: Ignoring persistent instance" - as I already mentioned there's a massive TRAC

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Petar, I just resolved HHH-9713 and it was working against my simplified version of your demo. Just fyi... On Mon, Apr 6, 2015 at 9:37 AM, Steve Ebersole wrote: > Petar, not sure what to say. That sounds like a local set up problem. I > cannot really help with that. > > Anyway, I have a "stri

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Petar, not sure what to say. That sounds like a local set up problem. I cannot really help with that. Anyway, I have a "stripped down" version of your test. I ripped out Spring and added a Gradle build script. The actual test class/method changed slightly to be just one test method: public c

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Hi Steve, thank you soo much for your support. I tried changing it but it had no effect. I also added a breakpoint in InformationExtractorJdbcDatabaseMetaDataImpl:135 and :151 but the flow never really goes through those breakpoints :( 2015-04-06 15:22 GMT+03:00 Steve Ebersole : > I am not fully

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

I am not fully aware of HSQLDB usage, but I wonder if you end up using 2 different databases. I am fairly certain you are using an in-memory database. In the test you are asking Hibernate to create a ConnectionProvider explicitly (your buildHibernateConfiguration method). I know absolutely zero

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Because compiling told me that none of the 5.0 bootstrapping packages/classes could be found. Anyway, I am working on simplifying your demo thing into something simpler. On Mon, Apr 6, 2015 at 6:33 AM, Petar Tahchiev wrote: > Hmm.. here's the result of mvn dependency:tree -Dverbose > -Dincludes

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Hmm.. here's the result of mvn dependency:tree -Dverbose -Dincludes=org.hibernate [INFO] --- maven-dependency-plugin:2.9:tree (default-cli) @ HHH-8805 --- [WARNING] Using Maven 2 dependency tree to get verbose output, which may be inconsistent with actual Maven 3 resolution [INFO] org.test:HHH-880

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

So your repo is still trying to use Hibernate 4.3.8. So I cannot reproduce this. On top of that, it uses tons of dependencies not needed for a simple bug reproducer. On Mon, Apr 6, 2015 at 5:58 AM, Steve Ebersole wrote: > So on export the tables simply are not created due to lack of privileges

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

So on export the tables simply are not created due to lack of privileges. So that explains why they are not found later. On Mon, Apr 6, 2015 at 5:56 AM, Steve Ebersole wrote: > Well there is a gigantic comment in org.hibernate.tool.schema. > extract.internal.*legacy*.DatabaseInformationImpl that

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Well there is a gigantic comment in org.hibernate.tool.schema. extract.internal.*legacy*.DatabaseInformationImpl that says how the tableInformationMap is not used, and why :) The problem is the HHH000262 log statement. That is saying that the tables are not found querying the database metadata.

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Wow, that's interesting. When I set the hbm2ddl-auto property to *create*, then I get a lot of these: 2015-04-06 10:35:14,243 org.hibernate.tool.hbm2ddl.SchemaExport [main] ERROR: HHH000389: Unsuccessful: alter table abstract_order drop constraint FKqmp2kh2yeov0xhpk0heyrxg6q 2015-04-06 10:35:14,24

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Just a quick follow-up here: SchemaMigratorImpl:125 is calling existingDatabase.getTableInformation where existingDatabase is of type org.hibernate.tool.schema.extract.internal.*legacy*.DatabaseInformationImpl (I have no idea why is it using the legacy one), and If I step into it I can see it's usi

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

I see you have a test repository reproducing the error. I will try to run from there. On Sun, Apr 5, 2015 at 3:02 AM, Petar Tahchiev wrote: > Hi Steve, > > the test project that I created still fails with the latest SNAPSHOT > release, although the foreign keys are not created. Can you please >

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

On Thu, Apr 2, 2015 at 6:54 PM, Petar Tahchiev wrote: > Hi Steve, > > I just pulled and did ./gradlew install. Unfortunately this didn't install > the jars in my local maven repo because the maven plugin declaration was > missing (you might want to consider adding it). > That's because the task

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Hi Steve, the test project that I created still fails with the latest SNAPSHOT release, although the foreign keys are not created. Can you please investigate if that is related to the same issue. The test repository is here: https://github.com/paranoiabla/HHH-8805 2015-04-03 16:15 GMT+03:00 Emm

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Steve, I think there is something fishy. I have created a branch with a blatant usage of a JDK 8 API in hibernate-core There is one commit above today’s master: protected EmptyInterceptor() { + final java.time.ZoneId id = java.time.ZoneId.systemDefault(); + Sys

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Hi Steve, I just pulled and did ./gradlew install. Unfortunately this didn't install the jars in my local maven repo because the maven plugin declaration was missing (you might want to consider adding it). Anyways, after I added it the jars were installed in my repo. I ran schema export and the sc

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Ok Petar, when you get a chance pull and give that a try wrt ForeignKeys On Thu, Apr 2, 2015 at 2:06 PM, Steve Ebersole wrote: > I am working on it as we speak :) > > On Thu, Apr 2, 2015 at 2:05 PM, Petar Tahchiev > wrote: > >> Cool, >> >> ping me once resolved - I'm eager to test it :) >> >> 2

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

I am working on it as we speak :) On Thu, Apr 2, 2015 at 2:05 PM, Petar Tahchiev wrote: > Cool, > > ping me once resolved - I'm eager to test it :) > > 2015-04-02 21:57 GMT+03:00 Steve Ebersole : > >> Petar, so I was unfortunately remembering the work done for 6.0 when >> saying that wrt the FK

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Cool, ping me once resolved - I'm eager to test it :) 2015-04-02 21:57 GMT+03:00 Steve Ebersole : > Petar, so I was unfortunately remembering the work done for 6.0 when > saying that wrt the FK name. What I found is that binding support for JPA > @FK is, lets say "spotty" at best: > https://hib

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Petar, so I was unfortunately remembering the work done for 6.0 when saying that wrt the FK name. What I found is that binding support for JPA @FK is, lets say "spotty" at best: https://hibernate.atlassian.net/browse/HHH-9709 On Wed, Apr 1, 2015 at 8:02 AM, Petar Tahchiev wrote: > > OK, maybe

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

I'm not going to argue with you man. AnimalSniffer *is* run. If you don't believe that and don't want to verify it for yourself, oh well, nothing I can do about that... On Wed, Apr 1, 2015 at 8:32 AM, Gunnar Morling wrote: > Hum, you are not April-fooling me, right ;) > > There is something Ja

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Hum, you are not April-fooling me, right ;) There is something Java-8-specific in already: the usage of ConcurrentHashMap#keySet() (in SessionFactoryImpl#iterateEntityNameResolvers()) which - when compiled on Java 8 - adds a reference to the Java-8-only type KeySetView to the class file of Session

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Gunnar, it is applied. Add something that is java 8 specific and see... On Apr 1, 2015 7:59 AM, "Gunnar Morling" wrote: > I saw the plug-in, Steve. But how/when is it executed? > > Running "./gradlew build" used to execute AnimalSniffer and would have > revealed that accidental usage of KeySetVi

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

OK, maybe I'm doing something wrong. I also tried setting the foreign key name to "none" like this: @ManyToMany(targetEntity = AbstractFilterModel.class, cascade = { CascadeType.PERSIST, CascadeType.MERGE, CascadeType.REFRESH }, fetch = FetchType.LAZY) @JoinTable(inverseJoinColumns = {

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

I saw the plug-in, Steve. But how/when is it executed? Running "./gradlew build" used to execute AnimalSniffer and would have revealed that accidental usage of KeySetView. That's not the case anymore. It would be nice if that new plug-in could be applied automatically after compileJava as it used

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Increase your Gradle-fu we must young apprentice :) AnimalSniffer is still run. I simply converted it to be a plugin. Check out org.hibernate.build.animalsniffer.AnimalSnifferPlugin in ORM's /buildSrc project AnimalSniffer will apparently not detect this :) On Wed, Apr 1, 2015 at 4:32 AM, Gunn

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

https://hibernate.atlassian.net/browse/HHH-9704 On Wed, Apr 1, 2015 at 6:20 AM, Steve Ebersole wrote: > And no, we generally do not reopen issues from Closed state. And here, > given the different branches, I'd be more inclined to create a different > issue referencing the original. > > On Wed,

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

https://hibernate.atlassian.net/browse/HHH-8805?focusedCommentId=66093&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-66093 On Wed, Apr 1, 2015 at 6:20 AM, Steve Ebersole wrote: > And no, we generally do not reopen issues from Closed state. And here, > given the d

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Hi, On Wed, Apr 01, 2015 at 11:45:55AM +0100, Sanne Grinovero wrote: > the version issue of jboss-logging is a known limitation; I've > described some details on the wildfly-dev mailing list. > I was expecting for people to choose the most up to date version of > jboss-logging in case of conflicti

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Hmm, it seems I inadvertently set the wrong fix version on HHH-8805. It is fixed in our metamodel branch which is 6.0. I pulled the necessary metamodel (org.hibernate.mapping) changes back to master (5.0), but only the hbm.xml form of naming the FK "none" (magic value) is supported to truly disab

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

And no, we generally do not reopen issues from Closed state. And here, given the different branches, I'd be more inclined to create a different issue referencing the original. On Wed, Apr 1, 2015 at 6:18 AM, Steve Ebersole wrote: > Hmm, it seems I inadvertently set the wrong fix version on HHH-

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Frankly I don't know if it is enabled or how to enable it :) I'm using spring-boot with log4j2 as a logging implementation and It was working perfectly fine with hibernate 4.3.8.Final and hibernate-validator 5.1.3.Final 2015-04-01 13:45 GMT+03:00 Sanne Grinovero : > Hi Petar, > the version issue

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Hi Petar, the version issue of jboss-logging is a known limitation; I've described some details on the wildfly-dev mailing list. I was expecting for people to choose the most up to date version of jboss-logging in case of conflicting versions though, or manage the version explicitly rather than lea

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Oh, and one last thing: I don't think this is fixed: https://hibernate.atlassian.net/browse/HHH-8805 Here's my mapping: @ManyToMany(targetEntity = AbstractFilterModel.class, cascade = { CascadeType.PERSIST, CascadeType.MERGE, CascadeType.REFRESH }, fetch = FetchTy

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

One other thing I noticed: hibernate-core-5 depends on org.jboss.logging jboss-logging 3.2.1.Final and if you have hibernate-validator 5.1.3.Final (the last stable), it will depend on org.jboss.logging jboss-logging 3.1.4.GA So you will get an exception of method not found on some jboss-logging

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

> Currently, AnimalSniffer is in place to prevent this very category of error and I'm wondering why it didn't detect the "usage" of KeySetView. Looked at this a bit closer. Turns out, AnimalSniffer *will* detect this issue if it actually is run. The problem is that AS apparently is not executed by

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

2015-04-01 2:21 GMT+02:00 Steve Ebersole : > Just to clarify... I *think* that as long as we run the build with Java 8 > and set the bootclasspath to 6 or 7 we should be fine. > Yes, setting the boot classpath to 6 (or 7) makes sure you only use classes present in that JDK (be it explicitly or i

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Those messages are not errors, just warnings. To be precise... Not sure about that constraint one. Would need more info. On Tue, Mar 31, 2015 at 7:18 PM, Petar Tahchiev wrote: > Hi all, > > just to confirm - I tried it with java8 and the exception is gone. I still > see the "Duplicate joins f

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Just to clarify... I *think* that as long as we run the build with Java 8 and set the bootclasspath to 6 or 7 we should be fine. On Tue, Mar 31, 2015 at 7:13 PM, Steve Ebersole wrote: > Well the idea is to run the Gradle process with Java 8 (the build itself > is a Java process too don't forget

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Hi all, just to confirm - I tried it with java8 and the exception is gone. I still see the "Duplicate joins for class.." error, as well as a new foreign key exception: WARN : SQL Error: 1452, SQLState: 23000 ERROR: Cannot add or update a child row: a foreign key constraint fails (`solarapparel`.`

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Well the idea is to run the Gradle process with Java 8 (the build itself is a Java process too don't forget). We pass in the older JDK specifically to be able to set the bootclasspath for compilation and the executable for running tests. That's the theory. Interestingly I developed a simplified

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

There are many similar issues discussed on the Lucene developer's mailing list, it's an interesting read: - http://mail-archives.apache.org/mod_mbox/lucene-dev/201503.mbox/%3C07c401d06aba%240b477c80%2421d67580%24%40thetaphi.de%3E I see no alternative than to have those test jobs actually exercis

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

And no that's not a typo :) It's JDK6_HOME, but you pass it a Java 7 jdk :) On Tue, Mar 31, 2015 at 6:56 PM, Steve Ebersole wrote: > Actually this may have been a brain-fart on my part when building the > release. I think I may have forgotten to pass in the Java 6 JDK to the > build, which I u

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Actually this may have been a brain-fart on my part when building the release. I think I may have forgotten to pass in the Java 6 JDK to the build, which I use to set the javac bootclasspath. So in that case it would have used the bootclasspath from the Java 8 JDK I used to launch gradle. If you

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Ahh, seems this may be an option to work around it: Using the general *Map* interface in place of the concrete *ConcurrentHashMap* type here side-steps the coupling to the Java 8 return type and will allow this code to be compiled with Java 8 and run on Java 7. I had missed that part. On Tue,

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

When I say "internal" here, I mean internal to java classes. On Tue, Mar 31, 2015 at 6:30 PM, Steve Ebersole wrote: > Nope. It just effects any code compiled with Java 8 even though the > change is internal. The problem is the generated bytecode incorporates > this change. Like I said, this

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Nope. It just effects any code compiled with Java 8 even though the change is internal. The problem is the generated bytecode incorporates this change. Like I said, this should be compiled with 1.6 compatibility, but that is apparently not working atm. I am having a struggle getting a mixed JD

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

According to this: https://gist.github.com/AlainODea/1375759b8720a3f9f094 Notably the Java 1.7 *ConcurrentHashMap#keySet()* returns a Set while the 1.8*ConcurrentHashMap#keySet()* returns a ConcurrentHashMap.KeySetView`. I think you're using some Java8 API. 2015-04-01 2:25 GMT+03:00 Petar Tahc

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

So this should have been compiled for 1.6 compatibility (although Java 7 is required really as I mentioned). Looks like that maybe did not work. Try running with Java 8 On Tue, Mar 31, 2015 at 6:25 PM, Petar Tahchiev wrote: > petar@petar-ThinkPad-X1-Carbon:~$ java -version > java version "1.7.

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

BTW, thanks for adopting this and trying it! On Tue, Mar 31, 2015 at 6:21 PM, Steve Ebersole wrote: > What JRE are you trying to use? This error: > > java.lang.NoSuchMethodError: java.util.concurrent. > ConcurrentHashMap.keySet()Ljava/util/concurrent/ > ConcurrentHashMap$KeySetView; > > is indi

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

petar@petar-ThinkPad-X1-Carbon:~$ java -version java version "1.7.0_71" Java(TM) SE Runtime Environment (build 1.7.0_71-b14) Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode) petar@petar-ThinkPad-X1-Carbon:~$ uname -a Linux petar-ThinkPad-X1-Carbon 3.16.0-33-generic #44-Ubuntu SMP Thu

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

What JRE are you trying to use? This error: java.lang.NoSuchMethodError: java.util.concurrent.ConcurrentHashMap.keySet() Ljava/util/concurrent/ConcurrentHashMap$KeySetView; is indicative of an issue in cross-jre support due to a change internal to java classes. On Tue, Mar 31, 2015 at 6:03 PM,

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Yeah, too late though.. I need some sleep :)) 2015-04-01 2:18 GMT+03:00 Steve Ebersole : > So then you also noticed that I replied to him :) > > Jean-Baptiste Nizet > Awesome, > thanks for trying it out! I have noticed that occ

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

So then you also noticed that I replied to him :) Jean-Baptiste Nizet Awesome, thanks for trying it out! I have noticed that occasionally too wrt HHH72, but have been so heads down trying to get ready for the 5.0.0 Beta rele

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

BTW, I see here: https://hibernate.atlassian.net/browse/HHH-8844 that Jean-Baptiste Nizet commented he also gets these "Duplicate joins for class" warnings: - - unrelated: I get a warning for **every** entity that I didn't get with Hibernate 4, which is not very clear and seems like a

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

Thanks Steve, I managed to migrate my configuration to the new MetamodelImplementor. Now when I run the scema export I get a lot of these warning: INFO : HHH000400: Using dialect: org.hibernate.dialect.MySQL5Dialect WARN : JDBC Driver reports it stores quoted identifiers in both mixed and upper c

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

I am told that the bug does not affect the JBoss->Central sync process. So at some point the artifacts should all be available in Central On Tue, Mar 31, 2015 at 5:19 PM, Steve Ebersole wrote: > hibernate-core seems to be the only artifact that is available in JBoss > Nexus. > > On Tue, Mar 31,

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

hibernate-core seems to be the only artifact that is available in JBoss Nexus. On Tue, Mar 31, 2015 at 5:18 PM, Steve Ebersole wrote: > So apparently the artifacts / repo issue is a Nexus bug that is effecting > the JBoss repo (and therefore us)... > http://issues.sonatype.org/browse/NEXUS-7654

Re: [hibernate-dev] Trying Hibernate 5.0.0.Beta1

So apparently the artifacts / repo issue is a Nexus bug that is effecting the JBoss repo (and therefore us)... http://issues.sonatype.org/browse/NEXUS-7654 As I pointed out in the announcement, I am managing the "migration guide" in source repo while I develop the Betas. See https://github.com/hi

[hibernate-dev] Trying Hibernate 5.0.0.Beta1

Hi guys, I just tried the latest beta and I cannot compile my project. With the latest hibernate 4.3.X I was able to do this: --- final org.hibernate.cfg.Configuration configuration = getHibernateConfiguration(); configuration.buildMappings(); final SchemaUpdate schemaU