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 potenti
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 wrote:
> > In
On Wed, May 27, 2015 at 9:09 PM, Brett Meyer 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 is prob
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
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
capabiliti
> 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)?
>
> 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 beyo
http://in.relation.to/Bloggers/HibernateORM500CR1Release
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
+1 from me. Although, on the other hand, do we really need to keep maintaining
that to begin with? I guess I never thought simply having users go to the JIRA
release notes was a big deal. Just my $.02.
- Original Message -
> From: "Steve Ebersole"
> To: "Brett Meyer"
> Cc: "Hibernat
https://hibernate.atlassian.net/browse/HHH-9827
On Wed, May 27, 2015 at 8:56 PM, Steve Ebersole wrote:
> 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.
> th
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 am
I went ahead and got something in for CR1. Take a look...
On Wed, May 27, 2015 at 8:50 AM, Steve Ebersole wrote:
> I actually started with the third approach. But you bring up a good point
> about allowing the Dialect to access the DatabaseMetaData (and hence
> Connection) if it wanted to. So
I actually started with the third approach. But you bring up a good point
about allowing the Dialect to access the DatabaseMetaData (and hence
Connection) if it wanted to. So I would change that a bit. See the
updated gist
On Wed, May 27, 2015 at 7:33 AM, Max Rydahl Andersen
wrote:
>
> > The
> 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
>
On Wed, May 27, 2015 at 5:23 AM, Max Rydahl Andersen
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
>> Dialect an
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
16 matches
Mail list logo
