Yes, that would be great!
Thanks,
Gail
- Original Message -
> From: "Steve Ebersole"
> To: "Strong Liu"
> Cc: "Hibernate hibernate-dev"
> Sent: Tuesday, March 19, 2013 10:51:05 AM
> Subject: Re: [hibernate-dev] merge master onto metamodel regularly
>
> +1000 for me
>
> On 03/19/2013 1
+1000 for me
On 03/19/2013 11:29 AM, Strong Liu wrote:
> Hi there,
>
> I just finished the merge of master onto metamodel, and there were tons of
> conflicts :(
>
> I'm suggesting we ( well, I'm voluntary to do this ) do the merge by weekly,
> to minimise the conflicts
> I will do the merge in
Hi there,
I just finished the merge of master onto metamodel, and there were tons of
conflicts :(
I'm suggesting we ( well, I'm voluntary to do this ) do the merge by weekly, to
minimise the conflicts
I will do the merge in every monday ( my time ) if no objections, so, others
living in U.S.
The problem is what Hibernate does once it returns from the Scanner
calls. It applies filters. And the filters is applies are different
based on whether the url being scanned is the PU root url or a
non-root. You simply don't have that info; so I don't think it will
work.
On Tue 19 Mar 201
It's probably too early in the process to know for sure, but I'm already headed
down the path of using the existing Scanner contract for OSGi scanning in 4.2.
I provide a custom Scanner that ignores the "jar URL" completely -- all scans
tap into the OSGi BundleWiring. The scanning methods shou
I would like to test that everything work setting up infinispan to work on DIST.
Is there anywhere an example that I can look at?
On Tue, Mar 19, 2013 at 11:19 AM, Sanne Grinovero wrote:
> On Friday we had been pair-programming and likely finished the implementation:
> it looks good but we couldn
Yes, part of the redesign was to return class names (and streams)
rather than Class instances, but thats just part of the reasoning.
The problem is that we really can't continue to use the Scanner
contract as-is; it is not great for OSGi environments. Could we hack
up the OSGi stuff to work wi
Definitely should be targetting 4.3 imho
On Mar 19, 2013 10:09 AM, "Brett Meyer" wrote:
> During initial discussions about ORM in OSGi [1], we had targeted OSGi
> 4.2. However, in order to completely handle bundle scanning [2], we need
> an API that was not introduced until OSGi 4.3 (BundleWirin
During initial discussions about ORM in OSGi [1], we had targeted OSGi 4.2.
However, in order to completely handle bundle scanning [2], we need an API that
was not introduced until OSGi 4.3 (BundleWiring). There's nothing like it in
4.2 and it's not easily/reliably replaced. Although I believ
On 03/18/2013 09:15 AM, Steve Ebersole wrote:
> On Mon 18 Mar 2013 05:14:01 AM CDT, Emmanuel Bernard wrote:
>>
>> JBoss AS does use this contract so if you break it, we will need some
>> kind of compatibility matrix between Hibernate and JBoss AS and EAP.
>> Not unsurmountable but always a small an
Hi all,
as these users are reporting:
https://forum.hibernate.org/viewtopic.php?f=1&t=1025404
apparently the MasIndexer in Hibernate Search triggers this log, but I
don't actually want it to lock I just want to re-attach objects to the
Session so I'm using Lock.NONE.
I'm not familiar with this,
On Friday we had been pair-programming and likely finished the implementation:
it looks good but we couldn't run the test.
The blocker is that Map/Reduce on Infinispan only works on DIST, and since
we can't iterate on entries we need M/R so we might need to
reconfigure Infinispan in our tests.
Tha
12 matches
Mail list logo
