[ http://team.andromda.org:8080/jira/browse/CORE-32?page=history ]
Work on CORE-32 started by Chad Brandon
> Profile information should be externalized in XML mapping file(s).
> --
>
> Key: CORE-32
> URL:
improving exception recording with log4j
Key: CORE-34
URL: http://team.andromda.org:8080/jira/browse/CORE-34
Project: AndroMDA Core
Type: Improvement
Reporter: Chad Brandon
Assigned to: Chad Brandon
Need look into seei
[
http://team.andromda.org:8080/jira/browse/HIB-32?page=comments#action_10600 ]
Chad Brandon commented on HIB-32:
-
Sounds good
> Discriminator value should be configurable
> --
>
> Key: HIB-32
>
[
http://team.andromda.org:8080/jira/browse/HIB-32?page=comments#action_10599 ]
Martin West commented on HIB-32:
actually Ill make the "special" froms #column, #type, and #length to
distinguish them from real values.
> Discriminator value should be co
[
http://team.andromda.org:8080/jira/browse/HIB-32?page=comments#action_10598 ]
Martin West commented on HIB-32:
done.
> Discriminator value should be configurable
> --
>
> Key: HIB-32
> URL: ht
[
http://team.andromda.org:8080/jira/browse/HIB-32?page=comments#action_10597 ]
Chad Brandon commented on HIB-32:
-
How about:
column
"name"
type
"name"
length
"NN"
[
http://team.andromda.org:8080/jira/browse/HIB-32?page=comments#action_10596 ]
Martin West commented on HIB-32:
ok how about
from
to
then that would remove the need for the namespace proeprties columnNam, type
and length
[
http://team.andromda.org:8080/jira/browse/HIB-32?page=comments#action_10595 ]
Chad Brandon commented on HIB-32:
-
My only comment: don't use a properties file, use one of the AndroMDA mappings
files, otherwise sounds good.
> Discriminator value shoul
[
http://team.andromda.org:8080/jira/browse/HIB-32?page=comments#action_10594 ]
Martin West commented on HIB-32:
A one character field is ok but restrictive, I would prefer a strategy and/or
mapping base solution.
A mapping solution would have a names
Enumerations should really use the UML meta model type
--
Key: UMLMETA-11
URL: http://team.andromda.org:8080/jira/browse/UMLMETA-11
Project: UML Metafacades
Type: Bug
Reporter: Chad Brandon
Assigned to: Chad Br
andromda-profile should use enumerations for tagged values
--
Key: MISC-18
URL: http://team.andromda.org:8080/jira/browse/MISC-18
Project: Miscellaneous
Type: Improvement
Reporter: Chad Brandon
Assigned to:
[
http://team.andromda.org:8080/jira/browse/HIB-31?page=comments#action_10593 ]
Martin West commented on HIB-31:
thats what I like a problem with a fix. Thanks. Just testing a fix.
> Interface/Concrete inheritance hierarchy not possible?
>
[
http://team.andromda.org:8080/jira/browse/HIB-32?page=comments#action_10592 ]
Martin Vlcek commented on HIB-32:
-
Normally a one-character field or number in the database should be enough to
determine, what kind of class the object ist (e.g. 'P' for p
Aggregation shouldn't be enforced on one-to-one associations
Key: SPRING-15
URL: http://team.andromda.org:8080/jira/browse/SPRING-15
Project: Spring Cartridge
Type: Bug
Reporter: Chad Brandon
Assigned
[
http://team.andromda.org:8080/jira/browse/HIB-32?page=comments#action_10591 ]
Chad Brandon commented on HIB-32:
-
Just curious, but why would you want to determine it on a class level? It's
not a value you're gonna do anything with, hibernate just us
[
http://team.andromda.org:8080/jira/browse/HIB-31?page=comments#action_10590 ]
Martin Vlcek commented on HIB-31:
-
Yes, that should be generated and it works, if all super classes are concrete.
However, if the super class is interface, than the discrimi
[
http://team.andromda.org:8080/jira/browse/HIB-32?page=comments#action_10589 ]
Martin Vlcek commented on HIB-32:
-
Discriminator column name/type could be specified with namespace properties,
however, I would prefer, if one can override it on class lev
17 matches
Mail list logo
