This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
LightSpeed v. 5, current. I receives strange exception.
It pops-up when I reads the field of the entity, which is represented as a value object. The strangeness of this:
I have no idea how to even reproduce this behavior on my workstation. This problem is related to this topic www.mindscapehq.com/forums/thread/2474. This topic provides a workaround to add property name to the get-property in the model's code. Like that:
replacing the get-line with:
... and that helps! Would you concider adding property name to get-methods in your code generation templates? Or maybe fix this problem other way. |
|
|
No we would prefer not to do this but we do give you the option to achieve this yourself :) If you follow the details on this blog post http://www.mindscapehq.com/blog/index.php/2009/09/16/customising-lightspeed-entity-templates/ you can set up a custom version of the templates for your project and then modify them to append the additional argument when generating property getters.
|
|