I've used similar setups frequently. As another example, the Eclipse RCP
framework provides "ExtensionPoints." They're essentially an interface and a
bit of metadata used by the bundles. The core system provides the interfaces.
Additional plugins/bundles provide their own implementations of
Hi all,
I feel the need to share some thoughts on this quite tricky patch proposal:
https://github.com/infinispan/infinispan/pull/1245
I'm tempted to say that Hibernate Search should "scan ahead" to look
for more results to fill the gap; but -even assuming this was easy to
implement (which it is n
I am not familiar enough to know how this hooks in with OSGi.
StrategySelector is already pushed to master, if you want to incorporate
what this might look like using that I will certainly take a look.
On 08/28/2012 03:33 PM, mail...@bibbernet.org wrote:
> I had a similar problem before:
>
> In
If I haven't mentioned before, a osgi service could also carry
properties. This is used as example in the OSGI JPA Spec. where it is
written:
> The service must be registered with the following service property:
> javax.persistence.provider – The JPA Provider implementation class
> name, a docu
I had a similar problem before:
In an osgi project we needed the ability to extend a main system with
functionality provided in addon bundles
We developed a main system which could be extended and complemented with
extenders of several kinds.
The main system provided (exported) a tree of marker
On 08/28/2012 09:40 PM, Steve Ebersole wrote:
> Imagine we have acme.jar. acme.jar provides a new TransactionFactory
> to Hibernate for a new way to integrate with transactions. For
> hopefully obvious reasons Hibernate jars/bundles cannot name acme.jar
> as a import nor as a dependency (whate
Following a discussion about this on the dev IRC I did a little bit of
this work today.
See:
1)
http://transcripts.jboss.org/channel/irc.freenode.org/%23hibernate-dev/2012/%23hibernate-dev.2012-08-28.log.html
2) https://hibernate.onjira.com/browse/HHH-7556
The first step was moving all Bootstra
Imagine we have acme.jar. acme.jar provides a new TransactionFactory
to Hibernate for a new way to integrate with transactions. For
hopefully obvious reasons Hibernate jars/bundles cannot name acme.jar
as a import nor as a dependency (whatever the correct OSGi parlance is
there). So under no
On 08/28/2012 02:39 PM, Steve Ebersole wrote:
> The problem there is timing. Hibernate already has to be started in order
> for "this" to work. But what "this" is doing is providing things Hibernate
> needs to start. Its chicken-egg.
>
> Interestingly this is very similar to the proposal Scott M
Ok, should be back now.
It does need to get restarted a little later to perform an upgrade due
to Atlassian's latest security advisory.
On Tue 28 Aug 2012 08:45:32 AM CDT, Steve Ebersole wrote:
> The Hibernate Jira is not feeling well today :)
>
> I have notified Atlassian/Contegix. We should
The Hibernate Jira is not feeling well today :)
I have notified Atlassian/Contegix. We should hear shortly
--
st...@hibernate.org
http://hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinf
The problem there is timing. Hibernate already has to be started in order
for "this" to work. But what "this" is doing is providing things Hibernate
needs to start. Its chicken-egg.
Interestingly this is very similar to the proposal Scott Marlow and I made
to the JPA group. And in fact that co
12 matches
Mail list logo
