I noticed two problems when using XMI2PHP to generate code compatible with the EZPDO object relational tools. The first is that appending a "_" character to the start of non-public association names breaks the use of the get/set methods in EZPDO. The other is the use of type hinting (e.g. function myfunc(ObjectType $obj) ) because objects are actually EZPDO epObject objects and thus not the type name generated. I've made changes to XMIParser.php, PHPGenerator.php, and Facade.php to correct this if the EZPDO support is enabled in the configuration. I can send you patch files if you'd like.
Steve
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I noticed two problems when using XMI2PHP to generate code compatible with the EZPDO object relational tools. The first is that appending a "_" character to the start of non-public association names breaks the use of the get/set methods in EZPDO. The other is the use of type hinting (e.g. function myfunc(ObjectType $obj) ) because objects are actually EZPDO epObject objects and thus not the type name generated. I've made changes to XMIParser.php, PHPGenerator.php, and Facade.php to correct this if the EZPDO support is enabled in the configuration. I can send you patch files if you'd like.
Steve
Hi Steve,
Yes please. I'll take a look and apply it to the next release.
Thanks for your effort,
Pawel