Re: [hibernate-dev] ValidationMode

See inline... On Fri 22 Feb 2013 02:38:32 PM CST, Hardy Ferentschik wrote: > > On 22 Jan 2013, at 9:17 PM, Steve Ebersole wrote: > >> Kind of. What I mean is that the HEM integration code is allowing Set >> . So our impl allows a value like "auto, ddl" or other >> combos. I am not able to gr

Re: [hibernate-dev] ValidationMode

On 22 Jan 2013, at 9:17 PM, Steve Ebersole wrote: > Kind of. What I mean is that the HEM integration code is allowing Set > . So our impl allows a value like "auto, ddl" or other > combos. I am not able to grok why we allow multiples. I think this is a Hibernate specific "feature" to suppo

Re: [hibernate-dev] ValidationMode

Kind of. What I mean is that the HEM integration code is allowing Set . So our impl allows a value like "auto, ddl" or other combos. I am not able to grok why we allow multiples. Also auto and callback are slightly different. callback causes an error if no bv provider is available whereas auto

Re: [hibernate-dev] ValidationMode

On 22 Jan 2013, at 6:26 PM, Steve Ebersole wrote: > Any idea why the ORM/JPA Bean Validation integration code allows > multiple validation modes to be specified? Are you talking about "auto", "callback", "none"? Well, "callback" to enable validation, "none" to disable it. Why there is also "

[hibernate-dev] ValidationMode

Any idea why the ORM/JPA Bean Validation integration code allows multiple validation modes to be specified? ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] OGM-270 [MongoDB] Expose the WriteConcern settings to the configuration

That's what I thought thanks 2013/2/22 Davide D'Alto > Hi, > in the documentation I think we should list the different options, the > one in the link seems good to me. > > I think you need at least a test that checks that the String in the > configuration is converted into the right WriteConcer

Re: [hibernate-dev] OGM-270 [MongoDB] Expose the WriteConcern settings to the configuration

Hi, in the documentation I think we should list the different options, the one in the link seems good to me. I think you need at least a test that checks that the String in the configuration is converted into the right WriteConcern constant, a test that checks that the value is set in the driver a

Re: [hibernate-dev] Fwd: [Hibernate-JIRA] (HSEARCH-1275) Upgrade to Hibernate Validator 5

Wasn't expected, seems I had a mistake in the new notification schema: should be solved now. Thanks! On 22 February 2013 10:36, Guillaume SCHEIBEL wrote: > Is it normal that I received this email from JIRA ? > > Guillaume > > -- Forwarded message -- > From: Hardy Ferentschik (JIRA

[hibernate-dev] Fwd: [Hibernate-JIRA] (HSEARCH-1275) Upgrade to Hibernate Validator 5

Is it normal that I received this email from JIRA ? Guillaume -- Forwarded message -- From: Hardy Ferentschik (JIRA) Date: 2013/2/22 Subject: [Hibernate-JIRA] (HSEARCH-1275) Upgrade to Hibernate Validator 5 To: guillaume.schei...@gmail.com Hardy Ferentschik

[hibernate-dev] OGM-270 [MongoDB] Expose the WriteConcern settings to the configuration

Hello guys, I was wondering do we need to test all the new writeconcern settings ? If the answer is yes, do we test all values with all "classic" tests like we did for the association strategies or we just check that the value is properly set as in DatastoreInitializationTest. Second question, fo

Re: [hibernate-dev] IRC meeting

oh, sorry guys, after that long holiday, I forgot this meeting :( On Feb 21, 2013, at 8:50 PM, Steve Ebersole wrote: > I may not be able to make todays meeting either. The warranty folks are > coming to look at my laptop this morning, so depending on how that goes... >