<div dir="ltr"><div><div>Hi Emmanuel,<br><br></div>I will give another try these days but I believe OSGi support in infinispan is almost there now. <br><br></div>As for Camel integration, having a string based query language would definitely be useful, for the time being I've provided a QueryBuilderStrategy where the users has to manually build a QueryBuilder from a QueryFactory Not ideal but works.<br>
<br>Cheers,<br><br><div><div><br><div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Brett has offered to help you but I know for sure he won?t lead it. He would be more like a good expect to talk to.<br>
Bilgin has shown a Camel integration prototype but he also seemed to imply that he had some significant problems that needed Infinispan improvements.<br>
<br>
Also, I?m not quite sure but looking at these Camel routes, they seem to be very URI driven. If we want to support query over a Camel route and express them via a URI, we will need a string based query language. I might be talking nonsense and somehow the query is written in Java. But better anticipate. Bilgin would know more, he has written in his demo CamelInfinispanOperationQuery after all :)<br>
<br>
Emmanuel<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Thu, 27 Mar 2014 11:32:37 +0100<br>
From: Giovanni Meo <<a href="mailto:gmeo@cisco.com">gmeo@cisco.com</a>><br>
Subject: Re: [infinispan-dev] OSGi<br>
To: infinispan -Dev List <<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a>>,<br>
<a href="mailto:emmanuel@hibernate.org">emmanuel@hibernate.org</a><br>
Message-ID: <<a href="mailto:5333FE45.3080909@cisco.com">5333FE45.3080909@cisco.com</a>><br>
Content-Type: text/plain; charset=windows-1252<br>
<br>
Hi Emmanuel and infinispan folks,<br>
<br>
we have been using Infinispan in OSGi environment in a project called<br>
OpenDayLight, if interested you can look at:<br>
<br>
> <a href="https://git.opendaylight.org/gerrit/gitweb?p=controller.git;a=blob;f=opendaylight/clustering/services_implementation/pom.xml;h=d7a3db3841888f3c08e5cf8795aa42cf9cd9b4bc;hb=HEAD" target="_blank">https://git.opendaylight.org/gerrit/gitweb?p=controller.git;a=blob;f=opendaylight/clustering/services_implementation/pom.xml;h=d7a3db3841888f3c08e5cf8795aa42cf9cd9b4bc;hb=HEAD</a><br>
<br>
Granted we are using a tiny part of the infinispan capabilities, but we found<br>
very helpful to first of all define the contract the applications would have<br>
with the infinispan. For other issues like the classloading, we just made sure<br>
to provider a ClassResolver that always enforce the lookup in the OSGi class<br>
loader, and in spite of some initial unreliability things has been doing ok for us.<br>
<br>
My 2 cents,<br>
Giovanni<br>
<br>
On 27-Mar-14 10:28, Emmanuel Bernard wrote:<br>
> Hey guys,<br>
><br>
> Sanne and Hardy are working on the OSGi-ification of Hibernate Search and it<br>
> does not come without trouble.<br>
><br>
> Who is leading this effort on the Infinispan side? I recommend you start<br>
> early in a release cycle because you will have to butcher APIs and packages<br>
> to do it properly. Worse, you will suffer from you dependencies.<br>
><br>
> Brett has offered to help you but I know for sure he won?t lead it. He would<br>
> be more like a good expect to talk to. Bilgin has shown a Camel integration<br>
> prototype but he also seemed to imply that he had some significant problems<br>
> that needed Infinispan improvements.<br>
><br>
> Also, I?m not quite sure but looking at these Camel routes, they seem to be<br>
> very URI driven. If we want to support query over a Camel route and express<br>
> them via a URI, we will need a string based query language. I might be<br>
> talking nonsense and somehow the query is written in Java. But better<br>
> anticipate. Bilgin would know more, he has written in his demo<br>
> CamelInfinispanOperationQuery after all :)<br>
><br>
> Emmanuel _______________________________________________ infinispan-dev<br>
> mailing list <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
><br>
<br>
--<br>
Giovanni Meo<br>
Via del Serafico, 200 Telephone: <a href="tel:%2B390651644000" value="+390651644000">+390651644000</a><br>
00142, Roma Mobile: <a href="tel:%2B393480700958" value="+393480700958">+393480700958</a><br>
Italia Fax: <a href="tel:%2B390651645917" value="+390651645917">+390651645917</a><br>
VOIP: 8-3964000<br>
?The pessimist complains about the wind;<br>
the optimist expects it to change;<br>
the realist adjusts the sails.? -- Wm. Arthur Ward<br>
IETF credo: "Rough consensus and running code"<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
<br>
End of infinispan-dev Digest, Vol 60, Issue 30<br>
**********************************************<br>
</blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr">Bilgin Ibryam<br><br>Apache Camel & Apache OFBiz committer<br>
Blog: <a href="http://ofbizian.com" target="_blank">ofbizian.com</a><br>Twitter: <a href="https://twitter.com/bibryam" target="_blank">@bibryam</a><br><br>Author of Instant Apache Camel Message Routing <br><a href="http://www.amazon.com/dp/1783283475" target="_blank">http://www.amazon.com/dp/1783283475</a><br>
<span><font color="#888888"></font></span></div>
</div></div></div></div></div>