Hi fellows, Just a small mail because I need some help and I'm pretty sure you'll answer me.
For one of my projects, I've defined a persistent session based on a code manager and I provide some def files generated by the database persistent object tie in. By the way, I need to make this process reproductible and this is apparently not clear for me : I certainly need best practices you may know for this component. Here's the point where I've got issues : - the persistent object, call it "person", cannot be extended. The persistent session needs the exact "person" class and not a "director" or "administrator" class inheriting "person". So I have to make a PersonManager that will deal with the persistent object. - the tie in does not generate relations settings in the def file, so I've tried to shortcut it by giving to my persistent session manager a directory with files including the generated ones. I've got an error message telling me that the def file does not contain any definition. For purpose, my "fake" def file is like that : <?php $def = include(defs/person.php); ... return $def; ?> The objective is avoiding the loss of code during the regeneration. I know that's not a big priority over there, but I'm quite stuck with those ones because I'm loosing time merging files and so on. Thanks guys for the help you can provide. Max
-- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
