[rules-users] which libraries to use api or core

[keithnielsen]

I have been trying to upgrade to V5M4 with little success. I have all the
Drools libraries in a single Eclipse plug-in. I have both API and Core
libraries which is certainly confusing Eclipse and any plug-ins that are
dependent on it. I have also tried just using Core and deleting API from my
workspace but it appears that some of the classes may have been built
against the classes in API, specifically:

FactHandle accountHandle = session.insert(account); throws a compiler error
of 

The project was not built since its build path is incomplete. Cannot find
the class file for org.drools.runtime.rule.WorkingMemoryEntryPoint. 

Why calling insert on StatefulSession which is in core would be complaining
about an API class is beyond me unless Core was compiled against API and for
some reason the core class had a reference to WorkingMemoryEntryPoint from
the API library.

Again this is in an Eclipse plug-in world so you may not face these problems
depending on your runtime environment. I think the only way you can be sure
is to migrate and try in your own runtime.


Brody bach wrote:
> 
> Hi drools-developers,
> 
> I'd like to integrate drools in my application.
> I read in some threads that the structure of the libs has been changed in
> the newest version, so that same classes exist in several jars.
> So, if I am to use a class from the old one (core), is it safe enough for
> my appl? I mean will it run later when the libraries are completely
> separated?
> Or would it be preferable to use directly the new ones (from drools-api)?
> Thanks for advise
> BB
> 
> 
>       
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
> 
> 

-- 
View this message in context: http://www.nabble.com/which-libraries-to-use-api-or-core-tp21014726p21015865.html
Sent from the drools - user mailing list archive at Nabble.com.