[
https://issues.jboss.org/browse/FORGE-786?page=com.atlassian.jira.plugin....
]
Vineet Reynolds commented on FORGE-786:
---------------------------------------
John, could you please take a look at the new Scaffold-X API released in Forge 1.3.0. The
Scaffold Provider is no longer required to support only JPA entities, and this constraint
has been removed. However, no existing scaffold provider that we support has this feature
yet; the individual scaffold providers we support (Faces and AngularJS) require JPA
entities due to the nature of the classes they produce or rely on.
New scaffold providers can be written that do not have this constraint. If you consider
this API as sufficient we can close this.
Scaffolds shouldn't be so hard reliant on JPA Entities
------------------------------------------------------
Key: FORGE-786
URL:
https://issues.jboss.org/browse/FORGE-786
Project: Forge
Issue Type: Feature Request
Components: Builtin Plugins
Affects Versions: 1.2.0.Final
Reporter: John Ament
Fix For: 1.x Future
Scaffolds are really nice, however they all need to work against JPA entities. What if
you're not dealing with an entity, and instead have a data transformation layer that
occurs first? HTML5/CSS3 type frameworks use rest and as a result the underlying object
state may differ. Need to better support a scaffolding for non JPA entity classes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira