Databases
StackOverflow2013
Postsdbo
POUsing Dialogs for Edits in JSF apps - which component?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing Dialogs for Edits in JSF apps - which component?
    primarykey
    data
    text
    <p>I'm looking at changing the workflow of our edit screens to be dialogs. </p> <p>To get the general idea, we have a parent entity that has numerous children. Those are all in a data table component, with 'Edit' buttons beside each one. Clicking one causes the managed bean to load up that single record into a "currentlyEditing" variable, and returns null so it stays on the same view and ajax updates a previously hidden form area to show the selected record, pre-populated for edit. At the bottom of that new form is Save and Cancel buttons, which do what you expect. A single button below the child list ("Add") causes a blank object to be set into the "currentlyEditing" variable, and the view now shows a clean form. This is all pretty standard so far, right? </p> <p>What my business users have asked me to do is look at changing the edit workflow. Instead of clicking the button, and a previously-hidden area appearing below the list of children, they would like the button click to launch a dialog that contains the edit form and save/cancel buttons. All validation errors/messaging should stay in the dialog. It's currently undecided if a successful save should just auto-close the dialog, or if they should see a success message, and then have a button to close the dialog. Some have suggested having both a "Save" and "Save &amp; Close" button. </p> <p>We're using Primefaces 3.5 (and would consider moving to 4.0-SNAPSHOT because our go-live is fairly distant and we're not afraid of building from source in the meantime). I see that there's a current <code>&lt;p:dialog</code> component, but I also see there's an upcoming "Dialog Framework", but I'm just not sure what each of them is meant for. Is a full edit form with validation messaging and managedbean round-trips, possibly even with additional dialogs launched from within that dialog, just "too much" for what <code>&lt;p:dialog</code> was meant for? Is the Dialog Framework meant to address this/be used for such a use case? </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMikeCWpg
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload