Hello. The Topcased support will be improved in the next release. Right now, the test are based on Magic Draw models, we plan to add more Topcased model testcases.
GroovieMan wrote: > > The funny thing now is, that i receive a couple of > error messages with an untyped property id, that i did not specified. > Every <<Entity>> need a <<Key>>. If you don't model a <<Key>> a default pk is added to the entity by a model transformation. The model transformation creates a property 'id' with type 'long'. The type 'long' is received from the model. But if the model, does not contain a type long, no type is set. I think you discovered a bug. GroovieMan wrote: > > I guess they appear by connecting two <<entity>>classes with an > arc, definig a relational dependency. > In the above described case, every <<entity>> without <<key>> should throw this error. GroovieMan wrote: > > This effect stays regardless iff i add some PK's into each class/table > or not. > Hm, I added a <<Key>> from type <<Integer>> to the entities from my very simple topcased model, and everything works fine. Do you assigned the stereotype <<Key>> to this properties? Have the keys a type? Regards -- View this message in context: http://www.nabble.com/hibernate-cartridge-fails-to-create-POJO%27s-and-a-DB-Ddl-file-tp17590388s17564p17618917.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
