There are bugs with loadClass and serialisation :(
"Thus, we highly recommend replacement of this code:
myClassLoader.loadClass(className);
With this code:
Class.forName(className,false,myClassLoader);"
Mark
Hi,
i also saw all the Class.forName. Class.forName additionally uses a very
aggressive class caching policy.
See here:
http://blog.osgi.org/2011/05/what-you-should-know-about-class.html
http://blog.bjhargrave.com/2007/09/classforname-caches-defined-class-in.html
I do not understand why API imports compiler.impl? Maybe to enable
class#forname i guess.
Is there an intention to use a more modularized way in v6 beta4 when
OSGi support will be implemented?
Thanks Florian
Am 20.06.13 15:43, schrieb Cristiano Gavião:
Hi,
Well, besides the fact that the services that we used on version 5.x is
still there, I'm not that optimist with Drools 6 running well in an OSGi
container... at least not currently...
Last week I played a bit too with Jbosgi and Wildfly and got a lot of
classloading errors due some factory classes trying to load classes that
are in another bundles...
what surprise me most was that kie-api has an import to
org.drools.compiler.kie.builder.impl ! :)
regards,
John
On 17/06/13 19:39, Florian.Pirchner wrote:
hi,
i got a question about osgi support.
is beta 3 already useable in osgi environments? could see that activators are registering v5 api as services.
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.
thanks a lot for answer
florian
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users