[forge-issues] [JBoss JIRA] (FORGE-1398) Being able to create embeddables

Matej Briskar (JIRA) issues at jboss.org
Thu Jun 26 06:21:24 EDT 2014


    [ https://issues.jboss.org/browse/FORGE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979619#comment-12979619 ] 

Matej Briskar commented on FORGE-1398:
--------------------------------------

Already implemented the command + relationshipType.
What about restricting user to select @Embedded relationshipType for not an @Embeddable object and vice versa? E.g not showing these relationTypes as suggestions?

> Being able to create embeddables
> --------------------------------
>
>                 Key: FORGE-1398
>                 URL: https://issues.jboss.org/browse/FORGE-1398
>             Project: Forge
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: UI - Shell
>    Affects Versions: 2.0.0.CR2
>            Reporter: Antonio Goncalves
>            Assignee: Matej Briskar
>             Fix For: 2.x Future
>
>
> As per [FORGE-797] it would be good to have a new command to create an embeddable :
> {code} 
> jpa-new-embeddable --named Address ;
> jpa-new-field --named street1 --length 50 ;
> jpa-new-field --named street2 ;
> jpa-new-field --named city --length 50 ;
> jpa-new-field --named state ;
> {code} 
> Then, how do we embed it into a entity ? We could have a new {{--relationshipType}} :
> {code}
> jpa-new-entity --named Customer ;
> jpa-new-field --named address --entity org.agoncal.application.petstore.model.Address --relationshipType Embedded ;
> {code}
> Except {{Address}} is not an entity. So having {{--entity}} pointing to an embeddable looks strange



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


More information about the forge-issues mailing list