---------- Forwarded message ---------- From: "Steve Ebersole" <steven.ebers...@gmail.com> Date: Jul 27, 2012 7:25 AM Subject: Re: [hibernate-dev] schema export question To: "Hardy Ferentschik" <ha...@hibernate.org>
This is all changing as we had discussed the other day. If for now you want to change Exporter to be public for what you need, go for it. However as for setter keep in mind there are actually multiple export ers in play. We can discuss the state of the changes so far locally on my machine if you want. But I don't understand why you need to supply new exporter. Why aren't you just changing the "relational model" (adding check constraints, etc) for the exports to pick up? And no, that should be using System.out. Its output it sent to stdout specifically for purposes of command line piping/redirection. On Jul 27, 2012 5:35 AM, "Hardy Ferentschik" <ha...@hibernate.org> wrote: > Hi, > > I am trying to write some tests related to schema constraints application > in conjunction with Bean Validation. > In this context I came across org.hibernate.tool.hbm2ddl.Exporter which is > atm a package visible interface. > I was wondering whether it would make sense to make is a public interface > and add a setter to SchemaExport in > order to provide a custom exporter. This way I could get hold of the > created sql and use it in my tests. > > On a side note, org.hibernate.tool.hbm2ddl.ScriptExporter uses System.out. > Should it not use the logger instead? > > Thoughts? > > --Hardy > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
