[hibernate-dev] Hibernate Validator 4.0.0.CR1 - released

2009-08-27 Thread Hardy Ferentschik
Hibernate Validator 4.0.0.CR1 has been released. Please see http://in.relation.to/12235.lace for details. --Hardy ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] [infinispan-dev] [HSearch] DSL for Lucene queries (was: Re: Query module new API and configurations)

2009-08-27 Thread Hardy Ferentschik
That's what I said as well. Separate maven module. However, one can feel a disturbance in the force when one mentions MAVEN MODULE within the Hibernate Team :) On Thu, 27 Aug 2009 17:18:23 +0200, Manik Surtani wrote: > Ok. Just make sure we use a different maven module or something so that

Re: [hibernate-dev] [infinispan-dev] [HSearch] DSL for Lucene queries (was: Re: Query module new API and configurations)

2009-08-27 Thread Manik Surtani
On 27 Aug 2009, at 16:10, Emmanuel Bernard wrote: queryBuilder.withAnalyzer(Analyzer) queryBuilder.withEntityAnalyzer(Class) queryBuilder.basedOnEntityAnalyzer(Class) .overridesForField(String field, Analyzer) .overridesForField(String field, Analyzer

Re: [hibernate-dev] [infinispan-dev] [HSearch] DSL for Lucene queries (was: Re: Query module new API and configurations)

2009-08-27 Thread Emmanuel Bernard
queryBuilder.withAnalyzer(Analyzer) queryBuilder.withEntityAnalyzer(Class) queryBuilder.basedOnEntityAnalyzer(Class) .overridesForField(String field, Analyzer) .overridesForField(String field, Analyzer) .build() //sucky name Perhaps

[hibernate-dev] how to disable the annotation where

2009-08-27 Thread Tiago Mesquita
Hi Guys, I'm making a soft delete using @SQLDelete and @Where with a flag called "active"... when active = 1 the object is not deleted, else, the object was removed and don't come back in the search queries... but i want to bring him back even active = 0... so maybe i'll have to disable the @Where

Re: [hibernate-dev] [infinispan-dev] [HSearch] DSL for Lucene queries (was: Re: Query module new API and configurations)

2009-08-27 Thread Manik Surtani
On 27 Aug 2009, at 13:06, Emmanuel Bernard wrote: On 27 août 09, at 13:07, Manik Surtani wrote: Very elegant. I'm generally a big fan of 'builder' patterns like this, but this really isn't a DSL, is it? :) When you first mentioned a DSL I had visions of defining a new grammar and an

Re: [hibernate-dev] [infinispan-dev] [HSearch] DSL for Lucene queries (was: Re: Query module new API and configurations)

2009-08-27 Thread Emmanuel Bernard
On 27 août 09, at 13:07, Manik Surtani wrote: > Very elegant. I'm generally a big fan of 'builder' patterns like > this, but this really isn't a DSL, is it? :) When you first > mentioned a DSL I had visions of defining a new grammar and an ANTLR > parser, etc. But that is overkill. Thi

Re: [hibernate-dev] [HSearch] DSL for Lucene queries (was: Re: [infinispan-dev] Query module new API and configurations)

2009-08-27 Thread Hardy Ferentschik
On Thu, 27 Aug 2009 10:48:42 +0200, Emmanuel Bernard wrote: > Did I make my case? Yes. I can agree that your code is more readable and it will help building queries. That said, why not suggesting something like this to the Lucene folks directly. I agree on this one with Manik. --Hardy >

Re: [hibernate-dev] [infinispan-dev] [HSearch] DSL for Lucene queries (was: Re: Query module new API and configurations)

2009-08-27 Thread Manik Surtani
Very elegant. I'm generally a big fan of 'builder' patterns like this, but this really isn't a DSL, is it? :) When you first mentioned a DSL I had visions of defining a new grammar and an ANTLR parser, etc. But that is overkill. This approach certainly works, and will almost certainly p

Re: [hibernate-dev] [HSearch] DSL for Lucene queries (was: Re: [infinispan-dev] Query module new API and configurations)

2009-08-27 Thread Emmanuel Bernard
On 26 août 09, at 22:08, Hardy Ferentschik wrote: On Wed, 2009-08-26 at 13:39 +0200, Emmanuel Bernard wrote: I've been thinking about a DSL to build Lucene queries in the last day. What do you think of this proposal? What do you really gain compared to native Lucene queries? If your API achi