[hibernate-dev] [BVAL]

Guys I'm considering releasing the specification document as a Git repository. I am wondering if the document should share the same Git repo as beanvalidation-api or if these two should be kept separated. In other words, do these share the same release / tag cycle all the time? WDYT? Note that

Re: [hibernate-dev] [BVAL]

On Tue, 07 Jun 2011 09:10:15 +0200, Emmanuel Bernard wrote: > Guys I'm considering releasing the specification document as a Git > repository. > I am wondering if the document should share the same Git repo as > beanvalidation-api or if these two should be kept separated. In other > words

[hibernate-dev] Question about including hibernate-validator-legacy.jar in AS 7.0?

As 7.0 is not currently including the hibernate-validator-legacy.jar but people are asking me if we should include it. hibernate-validator-legacy.jar was included in previous AS releases (see JBAS-7608) to help with running Seam 2 applications. http://community.jboss.org/message/608953#608953 is

Re: [hibernate-dev] Question about including hibernate-validator-legacy.jar in AS 7.0?

On Tue, 07 Jun 2011 15:29:39 +0200, Scott Marlow wrote: > As 7.0 is not currently including the hibernate-validator-legacy.jar but > people are asking me if we should include it. > > hibernate-validator-legacy.jar was included in previous AS releases (see > JBAS-7608) to help with running Seam

Re: [hibernate-dev] Question about including hibernate-validator-legacy.jar in AS 7.0?

No it should not. People need to migrate to Hibernate Validator 4 and Bean Validation now. On 7 juin 2011, at 15:29, Scott Marlow wrote: > As 7.0 is not currently including the hibernate-validator-legacy.jar but > people are asking me if we should include it. > > hibernate-validator-legacy.jar

Re: [hibernate-dev] Question about including hibernate-validator-legacy.jar in AS 7.0?

+1 for not including the legacy version. BV and HV 4 are out for 1,5 years now and having the old version around just increases the risk that someone is using it accidentally (once there was a related question in the HV feedback forum). And I guess if someone really needs the old version they could

Re: [hibernate-dev] [BVAL]

+1 on having the spec. on github. Does the document also relate to the TCK? If so it maybe makes sense to have it within a third repo next to beanvalidation-api and beanvalidation-tck. Otherwise putting it into beanvalidation-api seems good. What format will the document have? -- Gunnar 2011/6

Re: [hibernate-dev] Question about including hibernate-validator-legacy.jar in AS 7.0?

I agree that we should not include it, but are there viable alternatives to deploy a Seam2 application? Also given the nice classloader isolation AS7 provides, if we really need to have it around we could hide it from non intentional usage by not exposing it. Also in case would it need to work wi

[hibernate-dev] remove old/deprecated cache spi?

the following spi were deprecated in release 3.3, should we remove them in this beta1 release? org.hibernate.cache.spi.Cache org.hibernate.cache.spi.CacheConcurrencyStrategy org.hibernate.cache.spi.CacheProvider org.hibernate.cache.spi.NonstrictReadWriteCache org.hibernate.cache.spi.ReadOnlyCache

Re: [hibernate-dev] remove old/deprecated cache spi?

I had been waiting until I had a chance to convert the simple map based caching to the new api to do the removal. But now is the right time to do the removal. On Jun 7, 2011 10:20 PM, "Strong Liu" wrote: > the following spi were deprecated in release 3.3, should we remove them in this beta1 relea

Re: [hibernate-dev] Wrong JdbcServicesImpl configuration with problematic connection

Done, please check my pull request. 06/06/2011 15:15, Steve Ebersole wrote: > > Then please create a test case that illustrates this problematic > behavior and ideally create a pull request fixing said behavior > > On Jun 6, 2011 5:01 AM, "Dmitry Geraskov" > wrote: >