[forge-issues] [JBoss JIRA] (FORGE-456) Support parent-child relationships
[
https://issues.jboss.org/browse/FORGE-456?page=com.atlassian.jira.plugin....
]
Richard Kennard commented on FORGE-456:
---------------------------------------
Okay please give it a try now (pull request 93).
It's not exactly what you asked for, but hopefully it will suffice? The differentiator
is whether or not the @OneToMany has a 'mappedBy' attribute. If it doesn't, we
put a dropdown and an 'Add' button (same as before). If it does, we allow the
child entity to be created 'in place'. This won't cover all fields, but after
adding you can click through for those? I'm hoping this works better in practice than
it sounds in theory!
Note until FORGE-398 is resolved, you'll need to make sure all your @OneToMany's
that have mappedBy *also* have CascadeType.ALL.
Support parent-child relationships
----------------------------------
Key: FORGE-456
URL: https://issues.jboss.org/browse/FORGE-456
Project: Forge
Issue Type: Feature Request
Components: Scaffold
Reporter: Pete Muir
Assignee: Richard Kennard
In some circumstances, an entity is only relevant as part of a parent-child relationship.
For example, a venue, such as a stadium, might have multiple layouts. The layouts are
entities in their own right, but should only be modified through the owning venue.
Note:
* The entity should not appear in the main menu on the left
* The view/create/edit for the child should be a separate screen
* Once a child has been viewed/created/edited, you should be returned to the parent
entity create/edit screen
* A bi-directional one-to-many/many-to-one relationship could be used as an indicator of
wanting this behavior
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira