Hey Roy, Sounds like you're understanding how metafacades work :) And yes that sounds like what is going on. We use DataType for things such as String, Long (basically any type that wouldn't really be modeled), because basically they are simple datatypes, Classifiers and such are reserved for the classes that we're actually interested in modeling, so yes that explains your problem. What modeling tool do you use? We have an andromda-profile*.xml.zip that you can either use as a module inside Magic Draw or import into some other tool like poseidon and it will have all the datatypes, stereotypes, and tagged values for AndroMDA.
Chad ----- Original Message ----- From: "Roy Feldman" <[EMAIL PROTECTED]> To: "Andromda User" <[EMAIL PROTECTED]> Sent: Sunday, August 22, 2004 10:51 AM Subject: [Andromda-user] Possible problem with Hibernate cartridge definition? > Hi Hibernate fans, > > > With very limited knowledge of the metafacade architecture, I think I > may have come across a inconsistency in the definition of the Hibernate > cartridge. > > The Hibernate Metamodel defines a <<metafacade>> called HibernateType > which extends the common <<metafacade>> ClassifierFacade. > > HibernateType defines one method, "getFullyQualfiedHibernateType". > > It looks like HibernateTypeLogicImpl implements > getFullyQualifiedHibernateType. > > When I look at the template, HibernateEntity.vsl, it > has the following line: > > * type="$attribute.type.getfullyQualifiedHibernateType" > > The type of type of an attribute is Classifier. This is shown by the > code automatically generated for the interface AttributeFacade: > > public org.andromda.metafacades.uml.ClassifierFacade getType(); > > > Where I am think there may be a problem, given my limited knowledge, > lies in "andromda-metafacades.xml". The last line is > <metafacade > metaobjectClass="org.omg.uml.foundation.core.DataType$Impl" > > metafacadeClass="org.andromda.cartridges.hibernate.metafacades.HibernateType LogicImpl"> > <property reference="hibernateTypeMappingsUri" default=""/> > </metafacade> > > > My interpretation of this is that Andromda will wrap every instance of > Datatype$Impl, the MDR implementation of Datatype, with an instance of > HibernateTypeImpl. Datatype is a subclass of Classifier, but in most > cases the type of an attributes type will not be a Datatype, but some > other subclass of Classifier, such as Class. > > My guess is that is why their are Velocity runtime errors in my example, > because the types of my attributes of not primitive DataTypes like int, > but rather Classes like String and Float. > > > Any feedback would be greatly appreciated. I would like get to the > point so I understand the Andromda well enough to start contributing to > this project. > > > thanks, > > roy > > > > > > > > > > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > Andromda-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/andromda-user ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
