Hi again,
there are some problems I found in the progress of migration:
1.) named query generation:
assumed an modelled entity (argouml, uml14) like this:
+-----------------------------------------------+
| <<Entity>> |
| MyEntity |
+-----------------------------------------------+
| |
+-----------------------------------------------+
|<<FinderMethod>> find(String):Collection |
|<<FinderMethod>> find(int,int):Collection |
+-----------------------------------------------+
this would generate the following named queries:
@Entity
@NamedQuery
({
@NamedQuery(name="MyEntity.find", query="someQuery"),
@NamedQuery(name="MyEntity.find", query="someOtherQuery")
})
A workaround is, to rename those finder methods instead of having different method signatures.
2.) Modelling precission of BigDecimal Attributes
With 3.2 it was possible to tag such an attribute with length=precission, scale to get the a DECIMAL(precission,scale) generated.
The current version would generate something like this:
@Column(... ..., length=12,4)
which is invalid syntax. Tried to use @andromda.persistence.column.precision/scale instead, but this is not detected by the generator
3.) Some other tagging doesn't have effect like:
@andromda.persistence.temporalType, which has to be generated for Date fields like @Temporal(javax.persistence.TemporalType.DATE)
Maybe someone can give some hints how to fix this. The first point seems to require a design decission.
regards Uwe
------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
