Re: [hibernate-dev] Community newsletter contribution

2016-04-27 Thread Sanne Grinovero
Thanks Vlad, good idea! On 27 April 2016 at 11:33, Vlad Mihalcea wrote: > Hi, > > I wanted to ask everyone to let me know if you'd like to include any > resource in the Community newsletter. > If you stumble on a blog post, forum or StackOverflow question, that you > happened to like and was wort

Re: [hibernate-dev] "Service" in Hibernate Search: history, lessons learned and rewrite

2016-04-27 Thread Sanne Grinovero
I can't mention Service w/o getting your attention :) On 27 April 2016 at 13:34, Hardy Ferentschik wrote: > Hi, > >> Yet it is a good idea nowadays to have LuceneWorkSerializer extend >> Service, as we dropped that level of flexibility. This implies that >> there's a single type of serializer (at

Re: [hibernate-dev] "Service" in Hibernate Search: history, lessons learned and rewrite

2016-04-27 Thread Sanne Grinovero
On 27 April 2016 at 11:35, Gunnar Morling wrote: > Hey Sanne, > > great write-up! > > 2016-04-27 0:04 GMT+02:00 Sanne Grinovero : >> >> The "Service" and "ServiceManager" concepts in Hibernate Search have a >> specific meaning which is often misunderstood and/or abused, causing >> trouble. >> >> T

Re: [hibernate-dev] "Service" in Hibernate Search: history, lessons learned and rewrite

2016-04-27 Thread Sanne Grinovero
On 27 April 2016 at 10:33, Davide D'Alto wrote: > This is an interesting sum up. > Shouldn't we keep these thoughts in a separate document for developer? > > Together with some higher level diagrams of the architecture, maybe. I indeed wrote it as you expressed need for an high-level overview of

Re: [hibernate-dev] Various expectation changes in hibernate-core after consolidating hibernate-entitymanager

2016-04-27 Thread Hardy Ferentschik
Hi, On Mon, 25-Apr-2016 11:13, Gunnar Morling wrote: > The strategy approach sounds nice on first thought, but it also adds > complexity. +1 > I think the underlying question is: What's the long-term strategy around > the "Classic API"? Should it remain in place for all times as a complete > alt

Re: [hibernate-dev] "Service" in Hibernate Search: history, lessons learned and rewrite

2016-04-27 Thread Hardy Ferentschik
Hi, > Yet it is a good idea nowadays to have LuceneWorkSerializer extend > Service, as we dropped that level of flexibility. This implies that > there's a single type of serializer (at most) Ok > and it's totally fine to expose this as: >SearchIntegrator#getLuceneWorkSerializer() How is tha

Re: [hibernate-dev] "Service" in Hibernate Search: history, lessons learned and rewrite

2016-04-27 Thread Gunnar Morling
Hey Sanne, great write-up! 2016-04-27 0:04 GMT+02:00 Sanne Grinovero : > The "Service" and "ServiceManager" concepts in Hibernate Search have a > specific meaning which is often misunderstood and/or abused, causing > trouble. > > They also changed over time: victim of two major refactorings whic

[hibernate-dev] Community newsletter contribution

2016-04-27 Thread Vlad Mihalcea
Hi, I wanted to ask everyone to let me know if you'd like to include any resource in the Community newsletter. If you stumble on a blog post, forum or StackOverflow question, that you happened to like and was worth sharing, you can send it to me, and I'll include it in the next edition. Thanks, V

Re: [hibernate-dev] "Service" in Hibernate Search: history, lessons learned and rewrite

2016-04-27 Thread Davide D'Alto
This is an interesting sum up. Shouldn't we keep these thoughts in a separate document for developer? Together with some higher level diagrams of the architecture, maybe. On Tue, Apr 26, 2016 at 11:04 PM, Sanne Grinovero wrote: > The "Service" and "ServiceManager" concepts in Hibernate Search