JIT-Compiling OCL : WHY we should compile OCL at runtime?

Session Type: 
Standard [35 minutes]

What is 'JIT-compiling OCL'? It’s compiling OCL requests at runtime, on the deployment target. The idea consists in direct generation of java bytecode from OCL requests represented as strings. Much the same way the Java Virtual Machine compiles java bytecode to machine code, at runtime.
Why should-we do such a thing? Beside performance, compilation on the deployment target has a lot to offer. It lets you handle OCL requests as mere strings as far as your deployment target and still provides fast evaluation. It provides a lot of flexibility and ease of deployment by avoiding nasty binary compatibility issues. It also eases enforcing the "ship-what-you-test-and-test-what-you-ship" discipline as you can ship what you write!

This talk will drive you in the wonderful world of compilers but not too deep inside. It will also look at perspectives offered by this approach to OCL-compilation.
We intend to provide a fair sense of what's going under the hood of the compiler and especially provide performance results. But, we also intend to examine perspectives offered by JIT Compilation of OCL requests through a specific use case : OCL for writing business rules.
Business rules by their ever changing nature are a good candidate to demonstrate the advantages of JIT-compilation: such an approach even makes it possible to envision patching a running set of rules. But it shouldn't be necessary to go as far as that to convince the audience on the benefits of JIT-Compilation for OCL requests.

Schedule info



Experience level: 

Copyright © 2013 The Eclipse Foundation. All Rights Reserved.