On 27 May 2015, at 5:49, Steve Ebersole wrote:
If anyone is interested, the issue is here:
https://hibernate.atlassian.net/browse/HHH-9820
I do wonder overall about the interplay that should happen between a
Dialect and the JdbcEnvironment.
I reckon your issue is that you need access to
On Wed, May 27, 2015 at 5:23 AM, Max Rydahl Andersen mande...@redhat.com
wrote:
On 27 May 2015, at 5:49, Steve Ebersole wrote:
If anyone is interested, the issue is here:
https://hibernate.atlassian.net/browse/HHH-9820
I do wonder overall about the interplay that should happen between a
The old
way was calling one or more of the 50,000 (give or take ;) true/false
methods on Dialect at runtime. The new evolving approach is to build
delegates/helpers at boot time that encapsulate all that. Most of that
work so far is encapsulated by JdbcEnvironment. One piece of this
At the moment we write release announcements using in.relation.to and then
announce in other mediums by posting that link. We all agree (more or
less) that the wiki editor and rendering on there leaves much to be desired.
Brett had mentioned a long time ago about GitHub and its release
If I may dig up a zombie thread.. :)
What I plan to do unless I hear loud arguments to the contrary is to
truncate this to just the current major release indicated by branch. E.g.
the 4.2 branch would maintain changes just for 4.2 release family, etc.
This kind of goes hand-on-hand with what I
Is that the best way to know when TransactionManagers and DataSources come
and go too? Or is there a more specific concept for listening to an OSGi
service?
At least for TransactionManagers, yes, the BundleListener is probably the best
approach. I'm not aware of a more specific way beyond
http://in.relation.to/Bloggers/HibernateORM500CR1Release
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
On Wed, May 27, 2015 at 9:09 PM, Brett Meyer brme...@redhat.com wrote:
Is that the best way to know when TransactionManagers and DataSources
come
and go too? Or is there a more specific concept for listening to an
OSGi
service?
At least for TransactionManagers, yes, the BundleListener
In regards to OsgiClassLoader and dynamically managing the classpath, any
thoughts on how to handle out single call to OsgiClassLoader#addClassLoader
(from OsgiPersistenceProvider passing
the javax.persistence.spi.PersistenceUnitInfo#getClassLoader we get from
the e-OSGi container)?
I am
Personally I also think that we should refer people to Jira for this
information. We already have an authoritative version of this list (Jira)
and I generally dislike duplication.
But I am just trying to manage different perspectives. A few people raised
points that relying on Jira might not be
More I mean what bundle(s) should I listen to in order to know that the
ClassLoader is no longer valid? Or how would I otherwise know that or be
notified of that?
I can ping Christian regarding Aries specifically and get his thoughts.
On Wed, May 27, 2015 at 9:16 PM, Brett Meyer
WildFly consuming ORM 5.0 is still hitting one last TCCL issue with HCANN.
It happens in
the org.hibernate.annotations.common.annotationfactory.AnnotationFactory#create
method trying to build the annotation proxy class.
There are a few possible approaches to resolve this...
The simplest
12 matches
Mail list logo
