I've been thinking about how we can have the metamodel API in place in time for the 4.0.0.beta1. One alternative is to use a fully built o.h.cfg.Configuration to provide the data for generating the new metamodel. This is obviously not what we would want in the end, but in the near term it would give us the data with everything already resolved. It would be available sooner so Steve could get going more quickly on building the SessionFactory/persisters. I've thought of 2 ways we could use the Configuration: 1) create a separate type of metamodel source for Configuration data (e.g., org.hibernate.metamodel.source.configuration) and use data from this source to generate the metamodel. 2) use Configuration for binding missing data (what we haven't finished) from annotations and hbm sources; as more data is available, we can remove the references to Configuration. Comments? Gail _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

To be absolutely clear, I'm suggesting this as a way to put the new

The Configuration would simply supply the data that would go into the new

----- Original Message ----- From: "Hardy Ferentschik" <hardy(a)hibernate.org&gt; To: hibernate-dev(a)lists.jboss.org, "Gail Badner" <gbadner(a)redhat.com&gt; Sent: Monday, May 23, 2011 1:51:30 AM Subject: Re: [hibernate-dev] Configuration as data for generating

Hi, I don't see what we would gain by this. In fact I don't know how you want to do this. The way forward is the new metamodel. Given the current state I don't believe into a beta1 either (at least not w/ the functionality we discussed), but if we are looking for a way out, I don't think this is it. --Hardy On Mon, 23 May 2011 10:19:19 +0200, Gail Badner <gbadner(a)redhat.com&gt;

> I've been thinking about how we can have the metamodel API in place in > time for the 4.0.0.beta1. > > One alternative is to use a fully built o.h.cfg.Configuration to provide > the data for generating the new metamodel. > > This is obviously not what we would want in the end, but in the near > term it would give us the data with everything already resolved. > > It would be available sooner so Steve could get going more quickly on > building the SessionFactory/persisters. > > I've thought of 2 ways we could use the Configuration: > 1) create a separate type of metamodel source for Configuration data > (e.g., org.hibernate.metamodel.source.configuration) and use data from > this source to generate the metamodel. > 2) use Configuration for binding missing data (what we haven't finished) > from annotations and hbm sources; as more data is available, we can > remove the references to Configuration. > > Comments? > > Gail > > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev