[jboss-cvs] jboss-seam/examples/pdf/view ...

[Norman Richards]

  User: nrichards
  Date: 07/01/24 01:16:17

  Modified:    examples/pdf/view  whyseam.xhtml
  Log:
  woops - remove debugging
  
  Revision  Changes    Path
  1.7       +0 -5      jboss-seam/examples/pdf/view/whyseam.xhtml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: whyseam.xhtml
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-seam/examples/pdf/view/whyseam.xhtml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -b -r1.6 -r1.7
  --- whyseam.xhtml	22 Jan 2007 05:05:08 -0000	1.6
  +++ whyseam.xhtml	24 Jan 2007 06:16:17 -0000	1.7
  @@ -1,7 +1,6 @@
   <p:document xmlns:ui="http://java.sun.com/jsf/facelets"
               xmlns:h="http://java.sun.com/jsf/html"
               xmlns:p="http://jboss.com/products/seam/pdf"
  -            pageSize="459 594"
               title="Why Seam"
               keywords="mykeyword"
               subject="seam"
  @@ -15,10 +14,6 @@
       <p:image alignment="right" wrap="true" resource="/jboss.jpg" /> 
       <p:font size="24"><p:paragraph spacingAfter="50">Ten Good Reasons To Use Seam</p:paragraph></p:font>  
   
  -    <p:paragraph>
  -        <h:outputText value="hi!" />
  -    </p:paragraph>
  -
       <p:font size="18"><p:paragraph>It's the quickest way to get "rich"</p:paragraph></p:font>
   
       <p:paragraph alignment="justify">AJAX fundamentally changes the interaction model of the web. The synchronous, coarse-grained requests used by traditional web clients let many server-side applications get away with minimal caching and no session-level concurrency. The "stateless" architecture is in many cases a viable solution. But not anymore! AJAX clients hit the server with many asynchronous, concurrent, fine-grained requests, which could easily bring your database to its knees. When state is held in memory between requests, it is highly vulnerable to concurrency-related bugs, since the Java EE platform provides no constructs for dealing with session-level concurrency.</p:paragraph>