The JADE 2022 release meets tomorrow’s business demands.
Hi,
We need to be able to add method that will execute on demand. We want to be able to code and run a method on a class without having to promote the code. We have to create a rule enging that can run certain checks , but we need to be able to add it on-dement to clients live without the need for code promotion. User should be able to add this to their system without jade expertise. Similar to the concept to dynamic property, but with dynamic method.
Thaban
Thaban Segaran
Closing because we already address the customer requirement that prompted the initial JEDI. If you have a unique request that is different to this please submit as a new JEDI.
Attachments Open full size
Yes I think that will work for me. I just need to be able to add it dynamically and run it. Thanks Bee-Jay!
Attachments Open full size
@thaban does Bee-Jay's suggestion address your particular use case? Thanks for the input, also, @Kevin.
Attachments Open full size
@BeeJay - Persistence could be the main difference. We've got a rules engine which uses Process::createTransientMethods, but they have to be re-created/compiled for each process using the rules engine. We've struck performance issues previously with the time it can take for transient methods to be created (compiler locks in particular). It would be useful, & likely perform better, if we could create dynamic methods persistently (that we generate based on user inputs, etc), with flags/options to prevent the dynamic methods from performing updates or starting transactions. These would be stored/used like a normal method (so they can be invoked via sendMsg), but would be excluded from general schema load operations (need to persist beyond a complete schema/class load), aside from causing an error when attempting to load a normal method with the same name. But we would need the ability to delete/rename dynamic methods, from within our applications based on user input, and via JCF (should we need to explicitly remove before loading a normal method with the same name).
Attachments Open full size
I'
How would this be any different to the existing Process::createTransientMethod feature?
Attachments Open full size