Hello,

our scenario is like this:
From our customer, we get an Excel file which contains something rule-like 
which we convert into actual Drools rule strings. Those, we want to deploy in 
our local Maven repository (the one being used by Drools/KIE/Maven) as an 
actual artifact. This allows us later, to create new rules with KIE-WB, which 
are then deployed into the same repository, but with a higher artifact version. 
The actual application can then initially, when it doesn't have a connection to 
KIE-WB, use the rules created from the Excel sheet. In a second step, it can 
later get a more current rule artifact from the KIE-WB repository.

This is why we create an actual artifact out of the Excel sheet. That process 
takes a while, so we do it in the startup listener.

As far as I understand it and as far as I could see it on the filesystem, when 
I build a KieModule programmatically, it is not persisted anywhere and it is 
lost on restart of the system. That is why I wanted to explicitly persist it 
with the Aether facilities, as depicted in my previous post. If I do not do 
that and if I then check at startup if the artifact version does exist, I get 
back a "false" and it is created again - which takes quite some time. This is 
the reason why I want to store my created artifact in the local, persistent 
repository.

Am I getting something wrong? Is the artifact already stored somewhere?

I hope my intentions are a bit clearer now ...

Thanks in advance!
Dominik

-----Ursprüngliche Nachricht-----
Von: [email protected] 
[mailto:[email protected]] Im Auftrag von Mario Fusco
Gesendet: Dienstag, 10. Juni 2014 17:06
An: [email protected]
Betreff: Re: [rules-users] Memory leak when deploying to Maven repository?

Hi Dominik,

I'm honestly not understanding why you're creating a kieModule and most 
important why you're deploying it on maven in a ServletContextListener, but I 
am guessing you're doing this only to demonstrate the problem. Also be aware 
that for doing so you're using some drools internal API and these API aren't 
guaranteed to be stable.

However every time you build a kieModule or you load it from a maven repo, it 
is stored in the KieRepository. If you need to remove it from there you can do 
this explicitly by using the KieRepository.removeKieModule(ReleaseId)
method.

I hope this helps,
Mario



--
View this message in context: 
http://drools.46999.n3.nabble.com/rules-users-Memory-leak-when-deploying-to-Maven-repository-tp4029950p4029955.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/rules-users

…………………………………………………………………
mit freundlichen Grüßen / kind regards
Dominik Sandjaja
Fon: +49 (0) 203 60878 183
Fax: +49 (0) 203 60878 222
e-mail: [email protected]

it-motive AG
Zum Walkmüller 6
47269 Duisburg
[email protected]
http://www.it-motive.de
……………………………………………………………………
Vorsitzender des Aufsichtsrats: Dr.-Ing. Jürgen Sturm
Vorstand: Horst-Dieter Deelmann (Vors.),  Matthias Heming, Christoph Tim Klose
HRB 9207, Amtsgericht Duisburg

_______________________________________________
rules-users mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/rules-users

Reply via email to