Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have used Seam in an ongoing largish project with IceFaces. Seam certainly is far better than using plain JSF (refer the link posted by Damo a couple of answers above).</p> <p>However, some of the issues I remember:</p> <ul> <li>unit testing: getting SeamTest to work properly especially in a continuous integration build was hard, search the web for "SeamTest issues". Also see this: <a href="https://stackoverflow.com/questions/991992/has-anyone-successfully-run-integration-tests-with-jboss-embedded-seam-and-maven">Has anyone successfully run integration tests with Jboss embedded, Seam and Maven?</a></li> <li>Multiple ways for developers to do things and not too many best practices documented. So you have to spend time and figure out what is best for your project team. For example, when implementing forms, here are the potential tags (note that some of them overlap):</li> </ul> <p>Facelets &lt;ui:repeat&gt;</p> <p>JSTL &lt;c:forEach&gt;</p> <p>JSF &lt;h:form&gt;</p> <p>ICEFaces &lt;ice:selectOneMenu&gt;</p> <p>JSF &lt;f:selectitems&gt;</p> <p>Seam &lt;s:button&gt;</p> <ul> <li>performance is suspect, especially with IceFaces, <a href="http://ptrthomas.wordpress.com/2009/01/14/seam-jsf-vs-wicket-performance-comparison/" rel="nofollow noreferrer">here is a related article</a> Also, you need "guru level" knowledge of Seam in order to do the Right Thing, the default way lands you in trouble. See this article for details: <a href="http://jsfcentral.com/articles/speed_up_your_jsf_app_1.html" rel="nofollow noreferrer">Speed up your Data-Driven JSF/Seam Application by Two Orders of Magnitude - Part 1</a></li> <li>since Seam 3 is imminent, and supposed to make use of 2 new specs (JSF 2 and WebBeans) that leaves questions on what happens to projects on Seam 2 and how long it will take for things to get stable</li> <li>learning curve. IMHO seam tries to do too much, give you wrappers over things like iText, Quartz, JExcel, jBPM, etc. And the Seam integration with third party frameworks is expectedly a step behind the latest versions. For example we had to integrate jBPM directly because we needed some of the latest features.</li> <li>maybe because of the lack of criteria queries in JPA 1.X, the way you implement dynamic search screens (where user fills in a lot of filter options and you have to generate dynamic HQL) felt very in-elegant, and this is when using the recommended "Seam Application Framework" EntityQuery class, see the link below for a simple example, but you can get an idea of what to expect for complex filter criteria, handling nulls, order-by and all: <a href="https://stackoverflow.com/questions/977388/how-can-i-to-order-an-entityquery-query-in-a-seam-app">How can I to order an EntityQuery query in a seam app?</a></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POAre there any disadvantages to SEAM?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USPeter Thomas
    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. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    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