Re: [hibernate-dev] metamodel thoughts

2011-06-24 Thread Max Rydahl Andersen
On Jun 24, 2011, at 02:32, Steve Ebersole wrote: > Here is one of the tests I pointed you to before: > https://github.com/hibernate/hibernate-core/blob/master/hibernate-core/src/test/java/org/hibernate/metamodel/binding/SimpleValueBindingTests.java > > It shows the basic steps. Pretty similar t

Re: [hibernate-dev] metamodel thoughts

2011-06-23 Thread Steve Ebersole
Here is one of the tests I pointed you to before: https://github.com/hibernate/hibernate-core/blob/master/hibernate-core/src/test/java/org/hibernate/metamodel/binding/SimpleValueBindingTests.java It shows the basic steps. Pretty similar to what you had. On 06/23/2011 02:18 PM, Max Rydahl Anderse

Re: [hibernate-dev] metamodel thoughts

2011-06-23 Thread Steve Ebersole
Right. One of the design goals is to keep this startup time metamodel both buildable by third parties and mutable by third parties. I say 'keep' because you *can* do this today. The problem in my opinion and that of others is simply that the old api is less then friendly. On Jun 23, 2011 2:53 P

Re: [hibernate-dev] metamodel thoughts

2011-06-23 Thread John Verhaeg
I think the immutability Gail was talking about only applied to classes used internally, not anything configurable by developers. The new design should allow for exactly what you're looking for wrt alternative deployment mechanisms. On Jun 23, 2011, at 2:37 PM, Bill Burke wrote: > Would be coo

Re: [hibernate-dev] metamodel thoughts

2011-06-23 Thread Bill Burke
Would be cool if it was metadata driven so that we could deploy Java objects that represented a Hibernate deployment rather than relying on configuration files. XML and annotation processors would just be used to build the metamodel which is then handed off to the hibernate engine for initiali

Re: [hibernate-dev] metamodel thoughts

2011-06-23 Thread Max Rydahl Andersen
sorry i'm a bit slow here but could someone show (pseudo) code for how the new approach would look like versus before? Here is what I remember being used to (approximately from memory): PersistentClass pc = new PersistentClass(); pc.setEntityName("org.model.Customer"); pc.setTable(new Table("CUS

Re: [hibernate-dev] metamodel thoughts

2011-06-23 Thread Gail Badner
1) is very much how I envisioned the state objects to be used (e.g., data processed from a particular source that initializes an implementation of a common "state" interface). I like what you proposed for 2), however I would like to see bindings that are immutable, at least after being built.