Hello Chad,
Tuesday, October 18, 2005, 5:22:42 AM, you wrote:
CB> Ok I thought about it and it isn't possible at the moment:
CB> Currently there is no way to tell which namespace properties are
CB> of what type until we actually use the namespace property to
CB> retrieve the property value, namespace properties store a property
CB> without defining its type, for example:
CB> protected TypeMappings handleGetLanguageMappings()
CB> {
CB> ...
CB> }
CB> As you can see from the example above that we actually construct
CB> the TypeMappings instance from the given namespace property URI
CB> value and that this doesn't happen until we actually call
CB> getLanguageMappings for the first time (i.e. lazily), because
CB> first its a string Do you have any ideas about a clean way we
CB> might go about indicating a namespace property is a mapping so
CB> that they can be loaded before we construct any metafacades? (I
CB> don't really like the idea of introducing a new property type in
CB> the andromda configuration).
just got a new idea: We could throw away the config metamodel and
write a new class that adapts Namespaces and Mappings to ASMModel:
public class ConfigModel extends ASMModel {
...
}
That way, ATL would believe it accesses a model but in reality the
namespace properties or mappings would be accessed. This would make
eager loading un-necessary.
WDYT?
Matthias
---
Matthias Bohlen
AndroMDA.com
Services for a model driven world
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
