So if we get target to work on these XJC tasks and generate JAXB models
without required... does that hinder runtime binding at all in Java 7/8?
On Thu, Apr 2, 2015 at 9:50 AM, Steve Ebersole wrote:
> I just want the one that "works" :)
>
> On Thu, Apr 2, 2015 at 9:37 AM, Gunnar Morling
> wrote
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
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
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
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
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
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
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
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
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
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
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.
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
13 matches
Mail list logo
