Hi Patrik, Sorry to bother you about this again, but can you tell me what the root problem is with having the same domain object names? What part of the system is resolving these names and having problems? Is this in oAW limitation? Or was it a problem with generating the database table names? I mean I definitely appreciate having the workaround that you gave me. I'm just coming back to this again and thinking that it would be nice if the fix can be built into Sculptor. Obviously if you are too busy to fix it, that is ok. I'm just trying to understand the problem better to see if this is something that we can fix for ourselves.
Thanks, Polly Patrik Nordwall wrote: > > It is currently not possible to do this. I'm not sure how complicated it > would be to implement this, but my feeling is that it is a limitation that > most people can live with. > > How would we name things in the database? > > /Patrik > > -- View this message in context: http://www.nabble.com/-Sculptor--resolving-references-to-domain-objects-with-same-name-in-different-modules-tp19152982s17564p19615520.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
