<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; ">There are bugs with loadClass and serialisation :(<div><a href="http://lists.jboss.org/pipermail/rules-dev/2011-November/003681.html">http://lists.jboss.org/pipermail/rules-dev/2011-November/003681.html</a></div><div><br></div><div><a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6500212">http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6500212</a></div><div>"<span style="background-color: rgb(255, 255, 255); font-size: 12px; text-align: -webkit-left; white-space: pre-wrap; ">Thus, we highly recommend replacement of this code:</span></div><pre style="margin-top: 0px; margin-bottom: 0px; padding: 0px; list-style: none; white-space: pre-wrap; word-wrap: break-word; font-size: 12px; text-align: -webkit-left; background-color: rgb(255, 255, 255); position: static; z-index: auto; ">
myClassLoader.loadClass(className);
With this code:
Class.forName(className,false,myClassLoader);"</pre><div><br></div><div>Mark<br><div><div>On 20 Jun 2013, at 15:01, Florian Pirchner <<a href="mailto:florian.pirchner@gmail.com">florian.pirchner@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi,<br><br>i also saw all the Class.forName. Class.forName additionally uses a very <br>aggressive class caching policy.<br>See here:<br><a href="http://blog.osgi.org/2011/05/what-you-should-know-about-class.html">http://blog.osgi.org/2011/05/what-you-should-know-about-class.html</a><br>http://blog.bjhargrave.com/2007/09/classforname-caches-defined-class-in.html<br><br>I do not understand why API imports compiler.impl? Maybe to enable <br>class#forname i guess.<br><br><br>Is there an intention to use a more modularized way in v6 beta4 when <br>OSGi support will be implemented?<br><br>Thanks Florian<br><br><br>Am 20.06.13 15:43, schrieb Cristiano Gavião:<br><blockquote type="cite">Hi,<br><br>Well, besides the fact that the services that we used on version 5.x is<br>still there, I'm not that optimist with Drools 6 running well in an OSGi<br>container... at least not currently...<br><br>Last week I played a bit too with Jbosgi and Wildfly and got a lot of<br>classloading errors due some factory classes trying to load classes that<br>are in another bundles...<br><br>what surprise me most was that kie-api has an import to<br>org.drools.compiler.kie.builder.impl ! :)<br><br>regards,<br><br>John<br>On 17/06/13 19:39, Florian.Pirchner wrote:<br><blockquote type="cite">hi,<br><br>i got a question about osgi support.<br>is beta 3 already useable in osgi environments? could see that activators are registering v5 api as services.<br><br>is it possible to consume osgi services in the script tasks and rules by context? is this planned for version 6? would be a great feature.<br><br>thanks a lot for answer<br>florian<br>_______________________________________________<br>rules-users mailing list<br>rules-users@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/rules-users<br></blockquote>_______________________________________________<br>rules-users mailing list<br>rules-users@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/rules-users<br></blockquote><br><br>_______________________________________________<br>rules-users mailing list<br>rules-users@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/rules-users<br></blockquote></div><br></div></body></html>