I do not disagree, especially about the clutter. I had two related
concerns with that this approach though:
1) minor, but this thing is then no longer just collecting the sources
of metadata which is what a MetadataSources is.
2) this is no longer a "directed API" at all. What do I mean by that
On 04/22/2011 06:43 PM, Emmanuel Bernard wrote:
> I've been working on Hibernate OGM documentation. I am still very unhappy
> with what I have but that's a start.
>
> You can read it at
> http://docs.jboss.org/hibernate/ogm/3.0/reference/en-US/html_single/
> You can contribute to it by forking on
Hi all
I've been working on Hibernate OGM documentation. I am still very unhappy with
what I have but that's a start.
You can read it at
http://docs.jboss.org/hibernate/ogm/3.0/reference/en-US/html_single/
You can contribute to it by forking on github
https://github.com/hibernate/hibernate-ogm
My preference would go to a MetadataSources#setMetadata(NamingStrategy)
My fear is that more functions could be needed overtime and make the
constructor or the buildMetadata signature cluttered and less readable.
On 21 avr. 2011, at 15:08, Steve Ebersole wrote:
> NamingStrategy is not a servi
