[hibernate-dev] [BVAL]

[Emmanuel Bernard]

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 even if we agree that it should be one (of which I'm not convinced 
yet), I'd like to keep history from both and I'm not sure we can do that.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] [BVAL]

[Hardy Ferentschik]

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, do these share the same release / tag cycle all the time?

+1 I think having them in the same repo makes sense. IMO they have the  
same release/tag cycle.

If it is too hard though I am happy w/ a new repo under the  
https://github.com/beanvalidation/
umbrella.

--Hardy
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Scott Marlow]

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 a recent request for 
help deploying a Seam 2 app on AS7.

Should AS7 include org.hibernate:hibernate-validator-legacy and should 
we include the org.hibernate:hibernate-validator-legacy:4.0.2.GA 
version?  Or is there a better version that goes with 
hibernate-validator 4.1.0.Final?

Thanks,
Scott

___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Hardy Ferentschik]

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 2 applications.
> http://community.jboss.org/message/608953#608953 is a recent request for
> help deploying a Seam 2 app on AS7.
>
> Should AS7 include org.hibernate:hibernate-validator-legacy and should
> we include the org.hibernate:hibernate-validator-legacy:4.0.2.GA
> version?  Or is there a better version that goes with
> hibernate-validator 4.1.0.Final?

Personally I feel it would be time to move away from the legacy validator.
Is there no way to replace the legacy validator in Seam 2 apps w/ Hibernate
Vaidator 4.x?

But in case you really want to include the legacy code (Validator 3.x  
effectively),
then 4.0.2.GA is the latest. We published the legacy code for some time as  
a module
of the current Hibernate Validator 4.x code, but since there is no active  
development
on this code we dropped the module some time ago.

--Hardy
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Emmanuel Bernard]

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 was included in previous AS releases (see 
> JBAS-7608) to help with running Seam 2 applications.
> http://community.jboss.org/message/608953#608953 is a recent request for 
> help deploying a Seam 2 app on AS7.
> 
> Should AS7 include org.hibernate:hibernate-validator-legacy and should 
> we include the org.hibernate:hibernate-validator-legacy:4.0.2.GA 
> version?  Or is there a better version that goes with 
> hibernate-validator 4.1.0.Final?
> 
> Thanks,
> Scott
> 
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev


___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Gunnar Morling]

+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 still get it manually.

--Gunnar

2011/6/7 Emmanuel Bernard :
> 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 was included in previous AS releases (see
>> JBAS-7608) to help with running Seam 2 applications.
>> http://community.jboss.org/message/608953#608953 is a recent request for
>> help deploying a Seam 2 app on AS7.
>>
>> Should AS7 include org.hibernate:hibernate-validator-legacy and should
>> we include the org.hibernate:hibernate-validator-legacy:4.0.2.GA
>> version?  Or is there a better version that goes with
>> hibernate-validator 4.1.0.Final?
>>
>> Thanks,
>> Scott
>>
>> ___
>> hibernate-dev mailing list
>> hibernate-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>

___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] [BVAL]

[Gunnar Morling]

+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/7 Hardy Ferentschik :
> 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, do these share the same release / tag cycle all the time?
>
> +1 I think having them in the same repo makes sense. IMO they have the
> same release/tag cycle.
>
> If it is too hard though I am happy w/ a new repo under the
> https://github.com/beanvalidation/
> umbrella.
>
> --Hardy
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Sanne Grinovero]

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 with Hibernate4 ?

Sanne

2011/6/7 Gunnar Morling :
> +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 still get it manually.
>
> --Gunnar
>
> 2011/6/7 Emmanuel Bernard :
>> 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 was included in previous AS releases (see
>>> JBAS-7608) to help with running Seam 2 applications.
>>> http://community.jboss.org/message/608953#608953 is a recent request for
>>> help deploying a Seam 2 app on AS7.
>>>
>>> Should AS7 include org.hibernate:hibernate-validator-legacy and should
>>> we include the org.hibernate:hibernate-validator-legacy:4.0.2.GA
>>> version?  Or is there a better version that goes with
>>> hibernate-validator 4.1.0.Final?
>>>
>>> Thanks,
>>> Scott
>>>
>>> ___
>>> hibernate-dev mailing list
>>> hibernate-dev@lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>>
>> ___
>> hibernate-dev mailing list
>> hibernate-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>

___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Strong Liu]

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
org.hibernate.cache.spi.ReadWriteCache
org.hibernate.cache.spi.TransactionalCache

---
Strong Liu 
http://hibernate.org
http://github.com/stliu


___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Steve Ebersole]

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 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
> org.hibernate.cache.spi.ReadWriteCache
> org.hibernate.cache.spi.TransactionalCache
>
> ---
> Strong Liu 
> http://hibernate.org
> http://github.com/stliu
>
>
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Dmitry Geraskov]

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:
> > Hey, guys,
> >
> > I decided to write to this list to force this mistake to be fixed in 
> Beta1.
> >
> > There is a widely used class JdbcServicesImpl in hibernate4.
> > In the configure(Map configValues) it gets Connection object and does
> > the configuration. But what if the connection can't be established? It
> > do some steps in case of SQLException. But there are could be other
> > reasons of connection problem. For example missing
> > Driver(ClassNotFoundException), but this exception isn't handled. Why I
> > think it should be handled here?
> >
> > Look at SchemaExport. It has an option "export" to database. And in 
> case
> > this option is set to false we don't need the connection and Driver to
> > make it generate schema script successfully. But we still need some
> > configuration data from JdbcServices. And actually in hibernate 3 it
> > works nice without db connection. I guess it also would work in
> > hibernate4 too, but only if connection can't be established because of
> > SQLException, but not any other problem.
> >
> > Dmitry Geraskov
> >
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev