[
https://issues.apache.org/jira/browse/CAY-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788748#action_12788748
]
Michael Gentry commented on CAY-1332:
-------------------------------------
Adding to Andrey's comment:
I just looked at my XML and saw:
<embedded-attribute name="myType" type="foo.bar.enums.MyType"/>
When it should look more like a normal attribute, such as:
<obj-attribute name="contractNumber" type="java.lang.String" lock="true"
db-attribute-path="CONTRACT_NUMBER"/>
You'll notice the custom type not only got changed to an embedded-attribute,
but even though I defined the DB attributes after the modeler blanked them out
(see CAY-1333), it didn't save them. It now seems to me this bug is also
related to 1333.
This is more of a blocker than I originally thought and I'll raise the priority.
> Embeddable validation error in CM on custom Java types
> ------------------------------------------------------
>
> Key: CAY-1332
> URL: https://issues.apache.org/jira/browse/CAY-1332
> Project: Cayenne
> Issue Type: Bug
> Components: CayenneModeler GUI
> Affects Versions: 3.0 beta 1
> Environment: All
> Reporter: Michael Gentry
> Assignee: Olga Tkacheva
> Priority: Minor
> Fix For: 3.0 beta 2
>
>
> Using Cayenne Modeler 3.0B1, I edited an ObjEntity's Java Type to be a custom
> enum (say, foo.bar.enums.MyType). When I save the project, I
> get an incorrect validation warning:
> Warning: EmbeddedAttribute has incorrect Embeddable.
> CM used to not work this way (never gave a warning for this) because custom
> Java Types are supported.
> You can still save the project, but the incorrect and misleading validation
> warning could confuse people.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
