Hi Patrik,
Ah, so I think you're saying the reference would have to be defined like
this:
ModuleA {
Entity Car {
...
}
}
ModuleB {
Entity Car {
...
}
}
ModuleC {
Entity ParkingLot {
- @ModuleB.Car car
}
}
And then how would this ModuleB.Car reference get resolved? Does OAW have
a built-in way of resolving something like that? Or would that have to be
done with a Sculptor Transformation? I'm still trying to understand how
much more complicated things get. :)
Thanks,
Polly
Patrik Nordwall wrote:
>
> The big change is in the xtext grammar. It must support prefixing with
> module name. That is possible, but it complicates things somewhat.
>
> The database issue is difficult to solve with a naming convention.
> Prefixing all tables is not good, since length of names of database tables
> are limited. I think the user has to decide the name of the conflicting
> table names.
>
> /Patrik
>
>
>
--
View this message in context:
http://www.nabble.com/-Sculptor--resolving-references-to-domain-objects-with-same-name-in-different-modules-tp19152982s17564p19636631.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
