FAQ - Technical details
What are the "rulesets"?
Rulesets allow CtoJ's generator to migrate from one source language to the target language. These rules can be as simple as a mapping from "cout" to "System.out.println" or as complex as the mapping of multiple inheritance. CtoJ's generator already includes a standard ruleset with hundreds of rules to ensure a high initial percentage of compilable code. This standard ruleset can be extended with customer specific rulesets to achieve even better results.
Why are they customer specific?
Different rulesets exist. The basic ruleset of CtoJ's generator is not customer specific, but target language specific. This standard ruleset can be extended to achieve even better results during the migration. The reason behind these extensions being customer specific is that even business logic code might have different, non-standard approaches to solving problems.
Can I define my own "rulesets"?
The customer specific rulesets are usually defined between the client and CtoJ, and implemented by CtoJ. At the beginning of the project the client and CtoJ agree upon a contingent for custom rule definition and implementation.
Do I need a runtime after migration?
No the only runtime needed will be the Java runtime. The Java code generated by CtoJ is 100% pure Java. You don't need a CtoJ runtime to run the migrated code.
Will the migration change the look and feel (renaming) of my code?
No. By default CtoJ's generator will not change any naming or look and feel. Your source code will look the same as before, it is just migrated to the target language. This enables your developers that worked with the legacy code, to continue working with the migrated code right away.
How do you handle ... ?
For detailed technical information please take a look at the How section. There you can find a white paper explaining the technical details of CtoJ's technology. If you should have further questions, feel free to contact us.
Go back to FAQ section.