I have had similar issues with the @andromda.persistence.table tagged value using Poseidon 3.0 and AndroMDA RC1.  I have introduced this tag into two Entity classes and have found that the Hibernate mapping files seem to be ignoring this value.

On Mon, 2005-02-07 at 07:25 -0700, Chad Brandon wrote:

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Paul
Pavlidis
Sent: Monday, February 07, 2005 12:02 AM
To: [email protected]
Subject: [Andromda-user] 3.0-RC1 vs 3.0M3

I'm trying to use the Andromda hibernate cartridge with models built in
Poseidon 3.0.

I'm hoping to get some clarifications about the differences between 3.0 RC1
and M3, and 
some idea of the plans for the next release.

Here is what I observed:

M3: No <<Enumeration>>, XDoclet for hbm.xml file,
@andromda.hibernate.inheritance works 
(at least for us).

RC1: @andromda.hibernate.inheritance is ignored, <<Enumeration>>, no need
for XDoclet.

[CB] 
@andromda.hibernate.inheritance should not be ignored.  What modeling tool
are you using?  If you're using magic draw, we changed the
@andromda.hibernate.inheritance TV to use an enumeration as its value.

So, my questions are:

- Will the inheritance tag be re-introduced to the project? Any idea when?
Would the M3 
HibernateEntity.vsl file work with RC1? Why was it removed?

- Or is there a good workaround someone can suggest for the implementation
of enums in our 
model using M3?

Thanks





-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Andromda-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/andromda-user
Chris Sterling
[EMAIL PROTECTED]
Software Architect
Codesic Consulting
http://www.codesic.com/
[EMAIL PROTECTED]

Reply via email to