11:29 a.m.
[
https://issues.jboss.org/browse/FORGE-914?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on FORGE-914:
-----------------------------------------------
Vineet Reynolds <vpereira(a)redhat.com> made a comment on [bug
977956|https://bugzilla.redhat.com/show_bug.cgi?id=977956]
Description of problem:
The following issues were discovered in the generated administration section whenever 1:M
relationships were involved in the TicketMonster object model:
1. When adding/editing a venue, there is a blank row with "green plus" button
for adding the new section to the venue. If you click on "save" button, this
blank row is validated and it prevents you from editing/adding venue. Also, if the row is
populated with valid values and saved, the newly created venue loses the section.
2. Add/Edit show - there are two "green plus" buttons, if you click on 2nd one
(for Ticket Prices), the validation of Performance Date is triggered, that is wrong.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
For issue 1:
1. Click the 'Create New' button in the Venue screen.
2. Enter a name for the venue and click 'Save'.
3. Correct the validation errors triggered for the blank row in the Section
field/property.
4. Click 'Save' again and view the newly created Venue.
For issue 2:
1. Click the 'Create New' button in the Show screen.
2. Select an Event and a Venue.
3. Click the Plus button in the Ticket Prices section, to add a new Ticket Price.
Actual results:
For issue 1:
The Section when saved with valid values, disappears and is not visible in the View Venue
screen.
For issue 2:
An error message 'may not be null' is displayed against the Performance Date field
when adding a Ticket Price.
Expected results:
For issue 1:
The Section entered in the Create Venue screen should be saved and visible in the View
Venue screen.
For issue 2:
The validation of the Performance date should be done on Save and not when adding a new
Ticket Price.
Additional info:
This an underlying issue in JBoss Forge and not in the TicketMonster example .No
workaround for this issue is currently known.
Rework the handling of 1:M relationships by the Faces/RichFaces
scaffold
------------------------------------------------------------------------
Key: FORGE-914
URL: https://issues.jboss.org/browse/FORGE-914
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.x Future
The generated Faces scaffold for 1:M relationships does not handle certain usability
aspects.
For example, a new row is automatically added by default when displaying a 1:M
relationship upon create. However, unless the add button is clicked, the contents of the
row are not added to the underlying managed bean. If the add button is not clicked, the
contents of the row are not treated as a new item to be added. This is very confusing.
Also, if bean validation is performed on the entities (in the rows of the 1:M
relationship), and if it fails, then the contents need to be corrected, even though they
may not be persisted in the database. Again, this is confusing behavior.
Additionally, deletion of entities from the collection (1-side of the association) seems
to be broken.
--
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
4667
days inactive
4667
days old
0 comments
1 participants
participants (1)
-
RH Bugzilla Integration (JIRA)