<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 2 Oct 2012, at 07:29, Ioannis Canellos <<a href="mailto:iocanel@gmail.com">iocanel@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Our OSGi stuff is best effort - working on OSGi was like sticking needles directly into the back of my eyeball, not fun. tbh I find OSGi a real PITA. Too many of our dependencies do not have real OSGi bundles available, so we have to resort to the spring repository - where the versions almost never match our original target version. Further when it fails it's almost freaking impossible to determine why it fails.<br>
</blockquote><div><br></div><div>The problem with the spring enterprise bundle repository, is that spring source is no longer actively interested in OSGi (ever since they donated spring-dm to the eclipse foundation) and a lot of the bundles they provide are either out of date, or just say not optimal. A much shorter repository but with better maintained bundles is the repository of service-mix bundles: <a href="http://repo1.maven.org/maven2/org/apache/servicemix/bundles/">http://repo1.maven.org/maven2/org/apache/servicemix/bundles/</a> which host bundles for service-mix, camel etc.</div>
<div><br></div><div>Of course, bundles and metadata are always one side of the problem. Usually, the use of class loaders requires some treatment too.</div><div><br></div><div>I'd like to contribute too, in providing a better OSGi support and maybe add some integration tests using pax-exam or arquillian.</div></div></blockquote>Please feel free to submit a pull request that moves us to maintained OSGi bundles.</div><div><br></div><div>There is an outstanding OSGi pull request for Camel. However I cannot accept the submission until it comes with a unit test. Anyone want to finish that off? Here is the JIRA, pull requests are linked from the JIRA.</div><div><a href="https://issues.jboss.org/browse/JBRULES-3389">https://issues.jboss.org/browse/JBRULES-3389</a></div><div><br></div><div>Here is a sample OSGi unit test:</div><div><a href="https://github.com/droolsjbpm/droolsjbpm-build-distribution/blob/master/drools-osgi-bundles/org.drools.osgi.test/src/test/java/org/drools/osgi/integrationtests/SimpleOsgiTest.java">https://github.com/droolsjbpm/droolsjbpm-build-distribution/blob/master/drools-osgi-bundles/org.drools.osgi.test/src/test/java/org/drools/osgi/integrationtests/SimpleOsgiTest.java</a></div><div><br></div><div>The unit test doesn't need to do much, just show we can build an end point and drive data through it.</div><div><br></div><div>Mark<br><blockquote type="cite"><div class="gmail_quote">
<div> </div></div>-- <br><b>Ioannis Canellos</b><div><div><i><div style="font-style:normal"><font size="1"><br></font></div></i><b><span style="font-weight:normal"><i><div style="font-style:normal;font-size:small"><span style="font-size:x-small"><i>Blog: <a href="http://iocanel.blogspot.com/" target="_blank">http://iocanel.blogspot.com</a></i></span></div>
</i></span></b><i><font size="1">Twitter: iocanel</font></i></div><div><br></div></div><br>
_______________________________________________<br>rules-users mailing list<br><a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/rules-users<br></blockquote></div><br></body></html>