Good morning.
I was looking for building a plugin code, for using it as module for billing policies in a java program. Looking that, I saw many libraries, equinox, jpf, all hard to implement for nothing really curious and bizzarre.
The only thing I wanted is to have a jar, once-compiled. One jar that always gets compiled and has inside it the pricing parameter functionality. If it is with the same signature then just compile the pricing plugin, and load it by reloading the main core of java application. Simple? Yes.
In the end, I made a test. I created an app. I compiled it once. Then the plugin. Then I attached the fresh and fresher plugin version to the directory, and I had the results. Always new data. Without compiling the main big java code.
Question, I don't get it why I hadn't the answer in front of me? Why so many frameworks? In the end is...java so loveable really?
I was looking for building a plugin code, for using it as module for billing policies in a java program. Looking that, I saw many libraries, equinox, jpf, all hard to implement for nothing really curious and bizzarre.
The only thing I wanted is to have a jar, once-compiled. One jar that always gets compiled and has inside it the pricing parameter functionality. If it is with the same signature then just compile the pricing plugin, and load it by reloading the main core of java application. Simple? Yes.
In the end, I made a test. I created an app. I compiled it once. Then the plugin. Then I attached the fresh and fresher plugin version to the directory, and I had the results. Always new data. Without compiling the main big java code.
Question, I don't get it why I hadn't the answer in front of me? Why so many frameworks? In the end is...java so loveable really?
Comment