>> - The shared non-thread-safe content finding looks like it spots a
>> symptom of a real bug: in the method 'getNamedEntityManagerFactory', a
>> hashmap is extracted from a concurrent hash map and read from.
>> Concurrently, there is the possibility that items are removed from the
>>
On 08/01/2013 10:41 AM, Scott Marlow wrote:
>>> - The shared non-thread-safe content finding looks like it spots a
>>> symptom of a real bug: in the method 'getNamedEntityManagerFactory', a
>>> hashmap is extracted from a concurrent hash map and read
Fixing the 2lc (Infinispan-Hibernate npe) bug HHH-7959 that occurs when
emptying a non-transactional cache, is pretty cool and exciting (IMO)!
On 08/07/2013 11:22 PM, Brett Meyer wrote:
> http://in.relation.to/Bloggers/HibernateORM424FinalReleased
>
> Nothing horribly exciting about this one ;)
On 08/08/2013 11:21 AM, Jeremy Whiting wrote:
> Hi,
>I am looking for feedback on changes to provide the ability for work
> to be completed in a currently running transaction. For example when a
> TableGenerator or SequenceGenerator is being used for generating unique
> ids. The statements that
HHH-8670 is about EntityManager.find() not returning null when a runtime
exception is caught when performing the find(). Returning null when a
ClassCastException (or any other runtime exception) occurs seems
confusing to me, but I suppose that we could log a DEBUG warning (like
we did for Enti
On 11/05/2013 05:13 AM, Sanne Grinovero wrote:
> On 5 November 2013 00:20, Scott Marlow wrote:
>> HHH-8670 is about EntityManager.find() not returning null when a runtime
>> exception is caught when performing the find(). Returning null when a
>> ClassCastException
WFLY-2387 is asking for EntityListeners to be able to (CDI) inject the
PersistenceUnit associated with the entity class.
WFLY-2387 mentions that the Hibernate persistence unit needs to be
available (for injection use) before EntityManagerFactoryBuilder.build()
registers the entity listeners.
W
Arun,
EclipseLink questions are not usually asked in the Hibernate lists.
Next time, try https://community.jboss.org/en/wildfly. I'll take a look
at the below.
Scott
On 11/10/2013 03:19 PM, Arun Gupta wrote:
> Somebody filed a issue at:
>
> https://github.com/arun-gupta/javaee7-samples/issues
Has anyone seen the below error doing a "./gradlew build
:release:distZip"?
Is there a way to skip building ":documentation:asciidoctor" during a
release?
Build error:
"
':documentation:asciidoctor'.
> Could not initialize class org.jruby.runtime.backtrace.FrameType
* Try:
Run with --stacktr
Looks like this commit changed that
https://github.com/hibernate/hibernate-orm/commit/bf26311474257c2f0118615e003553095c2d87b0
On 12/05/2013 10:51 AM, Guillaume Smet wrote:
> Hi all,
>
> ORM 4.2.8.Final breaks the API of EntityKey as it removes tenantId
> from the constructor.
>
> Typically, in H
I think this is an excellent question, my preference is to fail-fast in
some fashion.
JTA 1.1 spec description of Transaction.setRollbackOnly():
"
public void setRollbackOnly() throws IllegalStateException, SystemException
Modify the transaction associated with the target object such that the
On 12/06/2013 04:45 PM, Scott Marlow wrote:
> I think this is an excellent question, my preference is to fail-fast in
> some fashion.
>
> JTA 1.1 spec description of Transaction.setRollbackOnly():
>
> "
> public void setRollbackOnly() throws IllegalStateException, Syst
On 12/11/2013 07:40 AM, Emmanuel Bernard wrote:
> https://hibernate.atlassian.net/browse/HV-818
>
> I am a bit uncertain of the case and frequency when that happens. If
> WildFly does plan to stay on the 5.0.x series, we probably want to fix
> it in a 5.0.2. Same for the classloader leak I imagine.
7;d prefer to have HV use the same version as
> WF does since recently.
>
> Scott, do you know when the cut-off is for delivering stuff into WF CR1?
The cut-off is past but I still see changes being added to WF 8 (there
are a few TCK failures to tackle still). So, I think we should try t
I didn't know about this change either. Are there any WildFly unit
tests using HS?
On 12/16/2013 09:16 AM, Ales Justin wrote:
> Infinispan Subsystem supported Indexing element.
> This then needed Query on the classpath to work properly.
> (it could be hacked, ignored, but we opted not to do this
infinispan-NNN.Final.jar during WildFly 8 build
(currently NNN=4.4.0) which make up the jars in the Hibernate Search module.
>
> On 16 Dec 2013, at 16:24, Scott Marlow wrote:
>
>> I didn't know about this change either. Are there any WildFly unit tests
>> using
I am a big fan of Hibernate technologies and the search capabilities. I
am concerned though that we are deferring how to untangle the Hibernate
Search/Infinispan/WildFly dependencies.
I raised a few questions on the wildfly-dev mailing list, some that got
answered but one important issue didn'
On 03/04/2014 02:32 PM, Hardy Ferentschik wrote:
>
> On 4 Jan 2014, at 18:05, Emmanuel Bernard wrote:
>
>> Here are the meeting minutes.
>> I did add a manual summary since I don’t know how to effectively use the bot
>> to its full potential.
>>
>> ## Validator
>>
>> 5.1 is out and plan to push i
I started to push on Hibernate master integration for WildFly [1] +
Jipijapa [2].
http://pastie.org/9196859 is a NPE that occurs when the CDI BeanManager
is accessed during the first (EntityManagerFactoryBuilder) phase.
Hibernate ORM shouldn't use the BeanManager until the second phase.
Scott
On 05/21/2014 03:36 PM, Scott Marlow wrote:
> I started to push on Hibernate master integration for WildFly [1] +
> Jipijapa [2].
>
> http://pastie.org/9196859 is a NPE that occurs when the CDI BeanManager
> is accessed during the first (EntityManagerFactoryBuilder) phase.
On 05/23/2014 09:27 AM, Scott Marlow wrote:
> On 05/21/2014 03:36 PM, Scott Marlow wrote:
>> I started to push on Hibernate master integration for WildFly [1] +
>> Jipijapa [2].
>>
>> http://pastie.org/9196859 is a NPE that occurs when the CDI BeanManager
>
FYI, Javassist version 3.18.2-GA is now available.
http://issues.jboss.org/browse/JASSIST/fixforversion/12323811 lists the
four issues resolved.
Should we upgrade Hibernate ORM master to use Javassist 3.18.2-GA?
Scott
___
hibernate-dev mailing list
hi
Tue, May 27, 2014 at 12:56 PM, Scott Marlow <mailto:smar...@redhat.com>> wrote:
>
> FYI, Javassist version 3.18.2-GA is now available.
> http://issues.jboss.org/browse/JASSIST/fixforversion/12323811 lists the
> four issues resolved.
>
> Should we upgrade
I don't see anything naughty on the 3.18 branch
https://github.com/jboss-javassist/javassist/tree/3.18
On 05/28/2014 08:44 AM, Scott Marlow wrote:
> The last upgrade (HHH-8463 3.18.1-GA) seemed to work fine. I'll take a
> closer look at the changes to see if I overlooked any
>
>> * Relying on the JTA Synchronization makes sense conceptually, but have we
>> received any feedback from JBossTS?
>
>> * Regarding the above, +1 for (conceptually) not caring about
>> Synchronization failing for rollback-only and failing fast. But, just want
>> to make sure we're not overl
Are there any specific parts that you would still like feedback on?
On 12/04/2013 12:27 PM, Steve Ebersole wrote:
> I found a few spare minutes to work on this a little and move it into
> the next stage with some actual interfaces, impls and usages to help
> illustrate some of the proposed concept
I pushed a test case that simulates what can happen with remote EJB
invocations that share the same JTA transaction & EntityManager. The
"Transaction was rolled back in a different thread!" error [2] is thrown
but shouldn't be, since the active application thread has changed to a
different thr
On 06/30/2014 06:27 AM, Emmanuel Bernard wrote:
> I had a lot of hurdles to make Hibernate ORM run and build on Mac OS X and
> IntelliJ IDEA so here are a few tidbits:
>
> I give Gradle 1GB
>
> export GRADLE_OPTS="-Xmx1024M"
Are you on master or an earlier ORM branch? I have
GRADLE_OPTS="-
On 07/02/2014 02:36 PM, Scott Marlow wrote:
> On 06/30/2014 06:27 AM, Emmanuel Bernard wrote:
>> I had a lot of hurdles to make Hibernate ORM run and build on Mac OS X and
>> IntelliJ IDEA so here are a few tidbits:
>>
>> I give Gradle 1GB
>>
>> export
y
on my 8 gig laptop, that could explain why I'm seeing thrashing).
On 07/02/2014 03:43 PM, Scott Marlow wrote:
> On 07/02/2014 02:36 PM, Scott Marlow wrote:
>> On 06/30/2014 06:27 AM, Emmanuel Bernard wrote:
>>> I had a lot of hurdles to make Hibernate ORM run and build on M
This sounds similar to https://community.jboss.org/message/879546
On 07/08/2014 03:53 PM, Gail Badner wrote:
> HHH-8310 [1] mentions a Spring bug SPR-11125 [2] that results in threads
> having a different ContextClassLoader (CCL) than their caller. As a result,
> SerializableBlobProxy.generatePr
On 07/08/2014 05:04 PM, Scott Marlow wrote:
> This sounds similar to https://community.jboss.org/message/879546
I was hoping to hear more feedback from the above link but didn't. I
suspect that its a classloader issue with ear sub-deployments having
Hibernate on their classpath but not
On 07/09/2014 09:32 AM, Gunnar Morling wrote:
> 2014-07-02 23:24 GMT+02:00 Scott Marlow <mailto:smar...@redhat.com>>:
>
> I removed GRADLE_OPTS and ran again with "-no-daemon --parallel-threads
> 1" and my laptop still pegged the cpu at 100% but seemed
On 07/11/2014 07:53 AM, Petar Tahchiev wrote:
> Hello,
>
> I'm really sorry to post this here but I couldn't find any jboss-logging
> mailing list.
https://lists.jboss.org/mailman/listinfo/wildfly-dev might also be a
good place to post on. The developers that work on jboss-logging, will
see yo
I have been running the EE 7 compatibility tests with the Java security
manager enabled to find issues like http://pastie.org/9378079
Should we try to fix these on the ORM 4.3 branch (WildFly 9.0 currently
is using 4.3.5.Final) or on master (which should show up in WildFly at
some point)?
Scot
/2014 10:23 PM, Scott Marlow wrote:
> I pushed a test case that simulates what can happen with remote EJB
> invocations that share the same JTA transaction & EntityManager. The
> "Transaction was rolled back in a different thread!" error [2] is thrown
> but shouldn't b
More in-line below.
On 08/05/2014 10:52 AM, Scott Marlow wrote:
> Steve,
>
> This is the test case that I was talking about on IRC. It simulates
> what happens when several remote EJB calls occur using the same JTA
> transaction. This case is probably common enough that we
Either the subject or email isn't working to discuss this. Hence, the
rename.
On 08/05/2014 11:32 AM, Scott Marlow wrote:
> More in-line below.
>
> On 08/05/2014 10:52 AM, Scott Marlow wrote:
>> Steve,
>>
>> This is the test case that I was talking about on IR
Sanne,
One question that I didn't ask before, when the Hibernate
Synchronization.afterCompletion(int) is called (with rolledback TX
status), how does Hibernate know if the transaction was rolled back from
the transaction reaper thread? I tried checking the thread name in
WildFly integration c
thread is https://community.jboss.org/thread/243360.
On 08/07/2014 11:33 AM, Scott Marlow wrote:
> Sanne,
>
> One question that I didn't ask before, when the Hibernate
> Synchronization.afterCompletion(int) is called (with rolledback TX
> status), how does Hibernate know if the tr
ll entities are
detached).
I thought we had a valid suggestion, of changing the transaction manager
to set rollback only instead of rolling the transaction back from the
background but that doesn't seem to be happening.
Not an easy problem.
>
>
> On Thu, Aug 7, 2014 at 10:33 AM, S
I'm trying to help a user [1] that is complaining that a local database
transaction is used, instead of the JTA transaction as they expect. I
asked them to enable TRACE logging for { org.jboss.jca, org.hibernate,
org.jboss.as.jpa + com.arjuna} and see the "Skipping JTA sync
registration due to
ions?
I won't be sure until they enable TRACE logging for org.jboss.as.jpa and
give us more logs. I'm waiting for that.
>
>
>
>
> On Thu, Aug 14, 2014 at 10:23 AM, Scott Marlow <mailto:smar...@redhat.com>> wrote:
>
> I'm trying to help a user [1] th
ed to the issue listed below, the
> direct link is:
>
> https://issues.jboss.org/secure/attachment/12384220/server-org-jboss-as-jpa.log
>
> Regards,
> Rob
>
> On Thu, Aug 14, 2014 at 11:28 AM, Scott Marlow
> wrote:
>
> >
> > On 08/14/2014 11:59 AM, Steve
On 08/19/2014 09:07 AM, Scott Marlow wrote:
> Hi Rob,
>
> The new logfile is missing TRACE logging for the other categories.
> Please attach a new log with TRACE enabled for: org.jboss.jca,
> org.hibernate, org.jboss.as.jpa, com.arjuna
Just add the log file with the above categori
the latest log with all required log levels to the jira ticket.
>
> Rob
>
> On 20.08.2014 03:40, Scott Marlow wrote:
>> On 08/19/2014 09:07 AM, Scott Marlow wrote:
>>> Hi Rob,
>>>
>>> The new logfile is missing TRACE logging for the other categorie
te:
> Hi Scott,
>
> looks like the file got a immature , I reattached the full log again.
>
> Can you please remove the defective log to reduce confusion? :)
>
> Thanks
> Rob
>
> On 20.08.2014 15:07, Scott Marlow wrote:
>> Hi Rob,
>>
>> I don'
session.beforeCompletion();
For each Session:
session.closeDBConnections();
Thoughts?
Scott
[3] https://community.jboss.org/message/901701
>
>
> On Thu, Aug 14, 2014 at 11:28 AM, Scott Marlow <mailto:smar...@redhat.com>> wrote:
>
>
> On 08/14/2014 11:59 AM,
On 09/01/2014 07:20 AM, Gunnar Morling wrote:
> Hi,
>
> Running an OGM integration test on WildFly, I noticed that we work with
> JBossStandAloneJtaPlatform. Shouldn't it rather be
> JBossAppServerJtaPlatform in this case so we make use of the transaction
> manager from the container?
org.hibernat
Hello,
How would Hibernate ORM react to its persistence provider class instance
being used with multiple application deployments? Is there any "per
application" state in the ORM persistence provider class instance?
A few different implementations of
javax.persistence.spi.PersistenceProviderRe
Never mind, we will look at caching the PersistenceProvider class
instance at the application deployment level (in WildFly).
On 09/12/2014 04:02 PM, Scott Marlow wrote:
> Hello,
>
> How would Hibernate ORM react to its persistence provider class instance
> being used with multiple
What triggers Hibernate Validator to call
PersistenceProviderResolver.getPersistenceProviders()? Does this happen
during the call to
PersistenceProvider.createContainerEntityManagerFactory() or later after
application deployment completes?
I'm looking at changing
PersistenceProviderResolver.
I'm working on an application server bug fix that I need some advice
with, as Hibernate ORM 4.3.6.Final is throwing a
"o.h.DuplicateMappingException: Duplicate query mapping
EventManager.MyEvents" after I fixed a jar-file reference bug in WildFly
(when I try to deploy a test case).
Prior to my
If the cause is allowing the application to deploy with the persistence unit
root being the entire EAR, I am interested in feedback on what to do. e.g.
throw a deployment exception or log a warning. Logging a warning is probably
best, if this is indeed the cause. It might be harsh to fail the
urn is a static reference object that in its method calls
>> Persistence.getProviders() *each time* to resolve operations like
>> isLoaded(entity).
>>
>> So to answer your question, I think it's after.
>>
>> On Fri 2014-09-12 17:02, Scott Marlow wrote:
>>> What trigge
I don't see how it could be related but a few weeks ago freenode
recommended that everyone change their passwords.
On 10/13/2014 02:48 PM, Steve Ebersole wrote:
> just a heads up that I have not been able to connect to freenode for quite
> a few weeks now. Still no idea what is up there.
> _
On 11/10/2014 07:40 AM, Steve Ebersole wrote:
> It would depend on what is inside the CacheKey, which is the key object
> Hibernate passes to the second-level cache. Usually this situation
> comes up with the identifier Type(s), especially in the case of
> composite identifiers. Some of the Type
Trying to open http://hibernate.org/dtd/hibernate-configuration-3.0.dtd,
gives a:
"
Site temporarily disabled
This page has been temporarily disabled due to a misconfigured custom
domain.
Are you the site owner? Follow the instructions for setting up a custom
domain with GitHub pages to updat
Related question, should we instead be using the
org/hibernate/hibernate-configuration-3.0.dtd in
hibernate-core-4.3.7.Final.jar (instead of accessing the hibernate.org
website)?
On 11/18/2014 07:48 PM, Scott Marlow wrote:
> Trying to open http://hibernate.org/dtd/hibernate-configuration-
On 11/19/2014 08:53 AM, Sanne Grinovero wrote:
> On 19 November 2014 01:13, Scott Marlow wrote:
>> Related question, should we instead be using the
>> org/hibernate/hibernate-configuration-3.0.dtd in
>> hibernate-core-4.3.7.Final.jar (instead of accessing the hibernate.org
our registered
> EntityResolver? Ultimately, this should be resolved
> by org.hibernate.internal.util.xml.DTDEntityResolver
I'll give this a try.
>
> On Wed, Nov 19, 2014 at 10:04 AM, Gunnar Morling <mailto:gun...@hibernate.org>> wrote:
>
> 2014-11-19
> specific resolver is being used.
>
> On Wed, Nov 19, 2014 at 10:35 AM, Scott Marlow <mailto:smar...@redhat.com>> wrote:
>
> On 11/19/2014 11:26 AM, Steve Ebersole wrote:
>
> ORM has had local resolution of these DTDs forever. Something
> is amis
On 11/19/2014 02:43 PM, Steve Ebersole wrote:
> Ah, there is a difference in how core and hem are loading these. This
> is likely a bug, could you open a Jira?
I created HHH-9511 for this.
>
> On Wed, Nov 19, 2014 at 12:15 PM, Scott Marlow <mailto:smar...@redhat.com>>
Not a big deal to change the WildFly default which is in code, since we
don't have a suitable configuration file for the setting.
We should update
org.jboss.as.jpa.config.Configuration.PROVIDER_MODULE_HIBERNATE_OGM,
which currently is set to "org.hibernate:ogm". WildFly 8.x is already
final,
slot="4.x"
> target-name="org.hibernate" target-slot="4.3.8.Final" />
>
> ## The main alias
> name="org.hibernate" slot="main"
> target-name="org.hibernate" target-slot="4.x" />
>
> One
On 01/15/2015 09:49 AM, Emmanuel Bernard wrote:
>
>> On 15 Jan 2015, at 14:56, Scott Marlow > <mailto:smar...@redhat.com>> wrote:
>>
>> When we talked at the f2f, I said that we would do major.minor, I think
>> that is the summary notes from the disc
Hibernate.org is down (seeing WildFly testsuite failures).
On 11/19/2014 03:33 PM, Scott Marlow wrote:
> On 11/19/2014 02:43 PM, Steve Ebersole wrote:
>> Ah, there is a difference in how core and hem are loading these. This
>> is likely a bug, could you open a Jira?
>
> I
> Carlo
>
>
> On 02/03/2015 08:44 PM, Scott Marlow wrote:
>
> Hibernate.org is down (seeing WildFly testsuite failures).
>
> On 11/19/2014 03:33 PM, Scott Marlow wrote:
>
> On 11/19/2014 02:43 PM, Steve Ebersole wrote:
>
>
With a proposed TM level listener, we will have an SPI for notification
of when application threads associated with a JTA transaction, become
disassociated with the transaction (tm.commit/rollback/suspend time).
Having this knowledge in a synchronization callback, can determine
whether the pers
Hi Gunnar,
Yes, this behaviour is expected since you registered an non-interposed
synchronization. For what purpose are you registering the transaction
synchronization? I would like to be aware of the synchronizations that
we register in WildFly.
The non-interposed sync beforeCompletion call
rnate 5.0 SPI can be used by OGM (e.g.
currently the only need is to run the Hibernate Session.clear when we
know that the application thread is not actively using the Session).
>
> Emmanuel
>
>> On 10 Mar 2015, at 14:39, Scott Marlow wrote:
>>
>> Hi Gunnar,
>>
I just saw the below email response after I sent the last one. Sorry
about that, will respond here also. :)
On 03/10/2015 09:14 AM, Emmanuel Bernard wrote:
> Ah synchronization ordering, it never gets old :) Steve might remember better
> but I don’t think we ever managed to convice the tx team
ttps://github.com/jbosstm/jboss-transaction-spi/pull/5
[5] https://github.com/jbosstm/narayana/pull/810
>
> On Mon, Mar 9, 2015 at 1:19 PM, Scott Marlow <mailto:smar...@redhat.com>> wrote:
>
> With a proposed TM level listener, we will have an SPI for notification
n has been
called, then it is safe to clear the Hibernate session. The order that
these conditions are detected, does not matter.
>
> So what is this buying us?
>
>
> On Tue, Mar 10, 2015 at 11:09 AM, Scott Marlow <mailto:smar...@redhat.com>> wrote:
>
>
> So what is this buying us?
>
The current Hibernate ORM thread id checking, does not properly handle
the case when the application thread changes between calls to the
Hibernate session. The new approach does handle the application thread
changing between session invocations and also covers
rprising to me.
>
> My work-around works because my non-interposed sync is added through
> JtaPlatform to the actual (Arjuna) Transaction instance directly
> (rather
> than indirectly via RegisteredSynchronization) and thus gets invoked
> p
Steve,
Wildfly-dev [1] brings up a change expected for WildFly 10, to not
reference the Jandex indexes after deployment completes. I'm curious if
our current/planned ORM 5.0 jandex using code, keeps a reference to the
passed in "hibernate.jandex_index"?
How how hard would it be for ORM, to on
7;t *think* we do, but it sounds like something we definitely
> need to make sure we aren't doing.
>
> On Mar 17, 2015 8:41 AM, "Scott Marlow" <mailto:smar...@redhat.com>> wrote:
>
> Steve,
>
> Wildfly-dev [1] brings up a change ex
gt; On Wed, Mar 18, 2015 at 12:49 PM, Steve Ebersole <mailto:st...@hibernate.org>> wrote:
>
> Massive.
>
> On Wed, Mar 18, 2015 at 12:44 PM, Scott Marlow <mailto:smar...@redhat.com>> wrote:
>
> On 03/18/2015 01:05 PM, Steve Ebersole wrote:
&g
On 03/18/2015 02:56 PM, Scott Marlow wrote:
>
> On 03/18/2015 01:53 PM, Steve Ebersole wrote:
>> Out of curiosity though, since you want more and more and more things
>> pushed to "second phase bootstrapping", I am curious how this new
>> expectation plays in w
Congratulations on the new releases!
On 04/16/2015 02:20 AM, Gail Badner wrote:
> For details, see:
> http://in.relation.to/Bloggers/HibernateORM439Final4218FinalAnd4219FinalReleased
>
> Gail Badner
> Red Hat, Hibernate ORM
> ___
> hibernate-dev mailing
> What is "end of deployment"? Is that the end of phase-2 in our 2-phase
> JPA bootstrap design? If so, that should be fine.
Yes, the end of phase-2 in our 2-phase JPA bootstrap design should occur
before (WildFly) deployment is complete.
___
hibern
Do we need to have a Hibernate ORM continuous integration test setup to
run against Infinispan 7.2.1? How about Infinispan 8.x (master?). Or
is ORM/Infinispan already tested as part of the Infinispan CI testing?
On 05/11/2015 04:31 AM, Galder Zamarreño wrote:
> Hi Gail,
>
> I've sent a PR for
I remember seeing this before but don't remember why. Years ago, I
blogged [1] about using OGM on JBoss AS (before the rename to WildFly).
I didn't name the entity classes in the blog (or git [2]), so not sure
if that was because OGM worked better back then or I just got lucky with
my simple
d need more
hibernate-infinispan changes as well. I think that Infinispan 8.0 might
find its way into WildFly 10.
>
> Regards,
> Gail
>
> - Original Message -
>> From: "Steve Ebersole"
>> To: "Gail Badner"
>> Cc: "Sanne Grinovero&q
initialized based on a value set for on
> hibernate.cache.infinispan..eviction.max_entries. The only place I
> see TypeOverrides.getEvictionMaxEntries() used is in
> InfinispanRegionFactoryTestCase. Does this actually get used anywhere? Does
> the value find its way into a EvictionConfiguration.maxE
I ran part of the WildFly basic integration tests against the
https://github.com/scottmarlow/wildfly/tree/jipijapa3_hibernate5 branch,
which includes the following Hibernate versions:
ORM 5.0.0.CR1
HCA 4.0.5.Final
HS 5.2.0.Final
I am seeing the below errors.
1. The Hibernate Search test
(org.
Also am using Infinispan 7.2.1.Final but noticed that Infinispan
7.2.2.Final is now in WildFly 10, so I'll sync my branch with WF master
to upgrade Infinispan.
On 05/29/2015 12:50 PM, Scott Marlow wrote:
> I ran part of the WildFly basic integration tests against the
> https:/
ardy suggested today on IRC.
>
> 2. this is not expected, especially as I think the Infinispan version
> already in WF is aligned with the one in ORM5?
> Steve, do you remember about classloader strategy changes between
> latest ORM 4.3 and 5.0.0.CR1?
>
> Sanne
>
>
> O
> holds org/infinispan/commons/util/CloseableIteratorSet. Anyone?
infinispan-commons-7.2.1.Final.jar contains
org.infinispan.commons.util.CloseableIteratorSet
> 3) hibernate-infinispan is not able to access
> org/infinispan/commons/util/CloseableIteratorSet
>
> On Fri, May 29, 2015 at 11:57 AM
>
> On 05/29/2015 02:03 PM, Steve Ebersole wrote:
>> Scott, first please use a SNAPSHOT build as you'll need it for the HCANN
>> fix I did, or you could just pull in the newest HCANN (5.0.0.Final)
Should I use a pushed SNAPSHOT?
I can build ORM master via "gradlew clean install", however, "gradle
et up...
>
>
> On Fri, May 29, 2015 at 1:21 PM Scott Marlow <mailto:smar...@redhat.com>> wrote:
>
>
>
> On 05/29/2015 02:03 PM, Steve Ebersole wrote:
> > Scott, first please use a SNAPSHOT build as you'll need it for
> the HCANN
>
sted code changes. I asked for an ETA on
the PR.
>
> thanks,
> Sanne
>
> On 4 June 2015 at 23:47, Sanne Grinovero wrote:
>> On 29 May 2015 at 18:27, Scott Marlow wrote:
>>>
>>>
>>> On 05/29/2015 01:05 PM, Sanne Grinovero wrote:
>>>>
On 06/17/2015 08:57 AM, Sanne Grinovero wrote:
> On 17 June 2015 at 13:44, Scott Marlow wrote:
>>
>>
>> On 06/17/2015 06:44 AM, Sanne Grinovero wrote:
>>>
>>> Hi Scott,
>>> can we expect to see both Hibernate ORM 5 and this latest Hibernate
&g
Sanne,
The [1] pull request to bring Jipijapa source into WildFly master is merged.
I pushed a copy of the (work in progress) ORM 5 changes to github [2].
Is there a WildFly pull request for the changes to upgrade to Hibernate
Search 5.4.0.Alpha1? I didn't see one but I might of missed it.
Sc
On 06/18/2015 11:59 AM, Sanne Grinovero wrote:
> On 18 June 2015 at 15:55, Scott Marlow wrote:
>> Sanne,
>>
>> The [1] pull request to bring Jipijapa source into WildFly master is merged.
>>
>> I pushed a copy of the (work in progress) ORM 5 changes to github [
On 18 June 2015 at 17:17, Scott Marlow <mailto:smar...@redhat.com>> wrote:
> >
> >
> > On 06/18/2015 11:59 AM, Sanne Grinovero wrote:
> >>
> >> On 18 June 2015 at 15:55, Scott Marlow <mailto:smar...@redhat.com&
I tried deploying a simple 2lc enabled test app and got a CNFE on
Infinispan classes being referenced from the application classloader.
http://pastebin.com/PREzm6bn shows the exception. I'm guessing this is
a classloader issue in ORM 5 to be worked out.
with hibernate-infinispan. This seemed to work with Hibernate ORM
4.3.x.
On 06/18/2015 04:28 PM, Scott Marlow wrote:
> I tried deploying a simple 2lc enabled test app and got a CNFE on
> Infinispan classes being referenced from the application classloader.
>
> http://pastebin.com/PR
. Seems to me this is simply a problem in the ClassLoader
> made available to ORM.
>
> On Fri, Jun 19, 2015 at 7:46 AM Scott Marlow <mailto:smar...@redhat.com>> wrote:
>
> To be a little more specific, WildFly is now respecting the Hibernate
> Search desire for In
1 - 100 of 505 matches
Mail list logo
