Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Why do you need to evaluate the either/or situation in creating orders? There should simply be a button that says : <strong>New Order</strong> that launches a popup form and another, possibly from a datatable row that says "View Order Details". The design is fine. Just a few tweaks.</p> <ol> <li>You'll want to create and maintain a single session scoped object(call it <code>Visit</code>) in which you store all session related material. I'd advise you stick with the JSF session scoped bean that is dependent on the http session and can be effectively managed by the container. JSF Session Scoped beans are stored as simple objects in the http session and so can be easily manipulated outside the context of JSF. CDI Session Scoped beans however are trickier to handle outside of CDI.</li> <li>I'll also advise you break up your order creation process into a multi-step process using dynamically loaded page fragments <code>&lt;ui:include/&gt;</code> or the fine <strong>primefaces wizard</strong> component. With a multi-step creation, all you need to do is gather data along the steps and only commit a transaction when you've all the info you need from all the steps in a DTO. Keep the wizard DTO in the single session object so the container can cleanup in case of a timeout. If the user never saves or cancel or walks away from his desk, the session will die a natural death. And he can come back and continue his transaction if he makes it in time. Not sure what carlos has against <strong>stateless session beans but in my experience, they're a nice way of exposing business processes, in that they can expose their functionality in other ways like webservices and message targets</strong> (JEE5). <strong>Above all, it's very good design to keep as much business processing out of the managed beans as possible and into durable constructs like EJBs and Spring beans etc.</strong></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POEJB3 / JSF2: Design of JSF2 app with ConversationalScope and Stateful EJB
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USkolossus
    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. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COi dont understand your question with the either/or situation. On the order list view which is basically a datatable there is a New Order button on the right most columns header and a Edit Order button on the right most rows column. Just the order details view behind is the same... ad 1) And i am not sure how a session scoped bean can help. Thats why i want to use conversional scope. When i start to edit an order, new or existing, the conversion should start and when i finish, cancel or save, the conversion should end. Or is something conceptually wrong with it?
      singulars
      1. PO
      1. USJoysn
    2. COad 2) as this order creation is part of an bigger erp system and not only a simple web shop where a user needs to be guided through a wizard or the user will not do any other tasks besides the order creation i prefer the classical rich client design, where a user works with a central view and from it he opens "sub" views to perform some tasks and he then come back to the central view to save all his work. And i think the conversational scope and a stateful session bean is exactly meant to be the tooling for such things. Or i am wrong? And Carlos has concerns about stateful session beans...
      singulars
      1. PO
      1. USJoysn
 

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