On Tue, Jul 07, 2015 at 04:50:36PM -0400, Scott Marlow wrote:
> Hardy,
>
> It seems that the ValidatorFactoryBean#createConstraintValidatorFactory is
> getting called too late for some reason. http://pastebin.com/WrdD91Hr shows
> the call stack for
> ValidatorFactoryBean#create(CreationalContext c
On 8 July 2015 at 11:42, Hardy Ferentschik wrote:
> On Tue, Jul 07, 2015 at 04:50:36PM -0400, Scott Marlow wrote:
>> Hardy,
>>
>> It seems that the ValidatorFactoryBean#createConstraintValidatorFactory is
>> getting called too late for some reason. http://pastebin.com/WrdD91Hr shows
>> the call st
On Tue, Jul 07, 2015 at 04:50:36PM -0400, Scott Marlow wrote:
> To recreate the WildFly ORM 5 issue on WildFly (if you want to see it
> yourself), steps are:
For the record, I see the same test failures locally. I have not looked any
further regarding their cause.
@Scott, on a high level what are
On 07/08/2015 07:15 AM, Sanne Grinovero wrote:
> On 8 July 2015 at 11:42, Hardy Ferentschik wrote:
>> On Tue, Jul 07, 2015 at 04:50:36PM -0400, Scott Marlow wrote:
>>> Hardy,
>>>
>>> It seems that the ValidatorFactoryBean#createConstraintValidatorFactory is
>>> getting called too late for some r
On 07/08/2015 08:16 AM, Hardy Ferentschik wrote:
> On Tue, Jul 07, 2015 at 04:50:36PM -0400, Scott Marlow wrote:
>> To recreate the WildFly ORM 5 issue on WildFly (if you want to see it
>> yourself), steps are:
>
> For the record, I see the same test failures locally. I have not looked any
> furt
Scott, could you update the Gist with the complete stack trace you got? It
seems to only contains parts of it.
2015-07-08 14:32 GMT+02:00 Scott Marlow :
>
>
> On 07/08/2015 08:16 AM, Hardy Ferentschik wrote:
> > On Tue, Jul 07, 2015 at 04:50:36PM -0400, Scott Marlow wrote:
> >> To recreate the Wi
Here are a few different call stacks:
1. http://pastebin.com/ZiZL5vEh shows the call stack when running
against the WildFly master branch (with ORM 4.3.x) and the @Inject works
(the test
org.jboss.as.test.integration.jpa.beanvalidation.cdi.CustomMinValidator.setMinimumValueProvider()
method
Hi,
> The same test works with the WildFly master branch, which is using ORM
> 4.3.x. The Bean Validation integration code is unchanged in my WildFly
> branch, as is the Bean Validator. The only thing different, is the ORM 5
> integration code and the ORM 5 persistence provider.
Just fishing he
On 07/08/2015 09:02 AM, Hardy Ferentschik wrote:
> Hi,
>
>> The same test works with the WildFly master branch, which is using ORM
>> 4.3.x. The Bean Validation integration code is unchanged in my WildFly
>> branch, as is the Bean Validator. The only thing different, is the ORM 5
>> integration
On 07/08/2015 09:02 AM, Hardy Ferentschik wrote:
> Hi,
>
>> The same test works with the WildFly master branch, which is using ORM
>> 4.3.x. The Bean Validation integration code is unchanged in my WildFly
>> branch, as is the Bean Validator. The only thing different, is the ORM 5
>> integration
On Wed, Jul 08, 2015 at 09:11:55AM -0400, Scott Marlow wrote:
> >Just fishing here, but "integration code and the ORM 5 persistence provider"
> >might
> >indicate a problem in the persistence bootstrapping.
> >Have a look at
> >org.hibernate.cfg.beanvalidation.TypeSafeActivator#getValidatorFactor
org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl#populate(SessionFactoryBuilder
sfBuilder, StandardServiceRegistry ssr) does pass the correct VF to
sfBuilder.applyValidatorFactory (using the ValidatorFactory passed to
the EntityManagerFactoryBuilderImpl.withValidatorFactory). Ho
On 07/08/2015 09:32 AM, Hardy Ferentschik wrote:
> On Wed, Jul 08, 2015 at 09:11:55AM -0400, Scott Marlow wrote:
>>> Just fishing here, but "integration code and the ORM 5 persistence
>>> provider" might
>>> indicate a problem in the persistence bootstrapping.
>>> Have a look at
>>> org.hiberna
Hi,
> http://pastebin.com/4X0h1VPA is the call stack in. We are in the second
> bootstrap phase, which is good. The validator factory is passed into the
> integration properties but we are only checking the persistence unit
> properties in ORM 5. Since we are not looking in the integration pro
Steve,
I created HHH-9905 for this, which I was able to workaround with a quick
hack (set the missing "javax.persistence.validation.factory" property in
the ConfigurationService). I was able to pass the WildFly test with the
workaround.
Steve, is that the right fix? I assigned the jira to yo
Looks like I missed a small piece there. The intention was to have
TypeSafeActivator
pick up SessionFactoryOptions#getValidatorFactoryReference. Scott, can you
make sure SessionFactoryOptions#getValidatorFactoryReference contains the
proper ValidatorFactory reference when we get into TypeSafeActi
I would assume part of that is the Atlassian Connector for IntelliJ that I
use. Which sucks because now I would have to use the non-community version
of the IDE to use tasks stuff.
Out of curiosity, how does everyone else using IntelliJ connect it to Jira
or do y'all not connect it at all?
On Tu
Please no more pushing to master until I am done. Thanks
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Ok, I am done with the release. I am still writing up the announcement in
the new blog system; the information is here too:
https://github.com/hibernate/hibernate-orm/releases/tag/5.0.0.CR2
On Wed, Jul 8, 2015 at 11:18 AM Steve Ebersole wrote:
> Please no more pushing to master until I am done.
Hibernate ORM 5.0.0.CR2 has just been released. Details can be found at
https://github.com/hibernate/hibernate-orm/releases/tag/5.0.0.CR2
* - I ran into problems getting the new blog site to work for me, so
pointed here to the GitHub release comment
___
As I said, I had trouble writing this blog in the new asciidoctor stuff. I
had some trouble getting ruby etal set up locally. Sanne had mentioned
that I could just push to staging branch and CI would automatically build
it for me and I could check it that way. Well the CI job clearly saw my
chan
Wow, now it shows up. Like almost an hour later.
On Wed, Jul 8, 2015 at 2:17 PM Steve Ebersole wrote:
> As I said, I had trouble writing this blog in the new asciidoctor stuff.
> I had some trouble getting ruby etal set up locally. Sanne had mentioned
> that I could just push to staging branch
We are getting a "Failed to define class
org.jboss.as.test.integration.jpa.hibernate.SFSBHibernateSessionFactory"
error when running the WildFly tests on the CI machine. I don't see
this error locally which is why we didn't see this before.
[1] shows the WildFly console at the time of error.
Hi,
On Wed, Jul 08, 2015 at 07:17:07PM +, Steve Ebersole wrote:
> As I said, I had trouble writing this blog in the new asciidoctor stuff. I
> had some trouble getting ruby etal set up locally
Can you provide any more info than that? I am happy to help you setting
this up, but I need some m
> As I said, I had trouble writing this blog in the new asciidoctor stuff. I
> had some trouble getting ruby etal set up locally. Sanne had mentioned
> that I could just push to staging branch and CI would automatically build
> it for me and I could check it that way. Well the CI job clearly saw
I noticed that CI test failure is only occurring on Windows. I wonder
if
https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src/main/java/org/hibernate/bytecode/enhance/spi/Enhancer.java#L114
is misbehaving on Windows.
On 07/08/2015 04:00 PM, Scott Marlow wrote:
> We are ge
On 07/08/2015 07:00 PM, Scott Marlow wrote:
> I noticed that CI test failure is only occurring on Windows. I wonder
> if
> https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src/main/java/org/hibernate/bytecode/enhance/spi/Enhancer.java#L114
> is misbehaving on Windows.
We mi
I did review the code and come up with the same conclusion.
Issue: https://hibernate.atlassian.net/browse/HHH-9907
PR open: https://github.com/hibernate/hibernate-orm/pull/996
Regards,
On 07/09/2015 02:03 AM, Scott Marlow wrote:
>
> On 07/08/2015 07:00 PM, Scott Marlow wrote:
>> I noticed that
28 matches
Mail list logo
