[rsmagdum]

Hi Mauricio,

As you said -

You will not need to redeploy your existing application if a kjar changes.. that's why we use embedded maven (aether) to retrieve new kjars that are installed in the maven repo on runtime. The kjars will live inside the m2 repo so you don't need to worry about putting the kjars inside your application

- this maven repository will be on server? (where we will deploy kjar)
- if yes, my application will pick up new kjar automatically or I have to write some code in my application to do this?

I will have an embedded jBPM in my application and deployed it as war file on tomcat.

This war will have my java/jsp/servlet code, jBPM libraries and BPMN files. right?

I can't deploy anything extra like KIE-WB on server.
Now my application is running on server and I want to upgrade any BPMN.

-As per my current understanding, anything that we want to deploy should be bundled as kjar. So in this case, my kjar will have new BPMN and its version information etc.
We will have a folder/repository on server. For deployment of new/upgraded BPMN, we will deploy our kjar into that folder/repository and application will pick up kjar from that folder/repo.
right?
So any newly deployed kjar will be automatically picked up by my application? or I have to write some code to this?

Thanks,
Rahul

[salaboy21]

Yes in your application you need to use the KIE container and the KIE scanner to locate the new artefacts when you change them. They will be stored in the local maven repository when you deploy it.. It seems that you need to look deeper on how maven works to see the full picture.