[
https://issues.jboss.org/browse/FORGE-917?page=com.atlassian.jira.plugin....
]
Vineet Reynolds updated FORGE-917:
----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request:
https://github.com/forge/core/pull/324
These changes are introduced outside MetaWidget since the context is not available to
determine whether the inspected class is being scaffolded or not. Hence, the decision to
avoid scaffolding the class is taken well before inspection.
I've taken the decision to omit scaffolding such classes even through they may appear
in the search results, since they cannot be searched for, and neither can they be created
or updated without using their non-0-arg constructors. Using them otherwise leads to
PropertyNotWritableExceptions being thrown due to non-existent setters. Changing the class
to add setters is out of question since that would change their immutable property.
Faces scaffolding omits fields in the create/edit/search views when
they do not have setter methods
---------------------------------------------------------------------------------------------------
Key: FORGE-917
URL:
https://issues.jboss.org/browse/FORGE-917
Project: Forge
Issue Type: Bug
Components: Scaffold
Affects Versions: 1.0.5.Final, 1.3.0.Final
Reporter: Vineet Reynolds
Assignee: Vineet Reynolds
Fix For: 1.3.1.Final
This is from the TicketMonster model. The create,edit and search views for the
{{SectionAllocation}} and {{Ticket}} classes only list the current values of the entities.
Creating new entities or editing of existing entities of such classes with user-specified
values is not possible. Likewise, searching with a criteria is not possible.
Both these JPA entities have one thing in common, in that they do not have setters for
their fields.
--
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