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

[Norman Richards]

  User: nrichards
  Date: 07/04/05 18:05:45

  Modified:    examples/itext/view  whyseam.xhtml
  Log:
  add jboss-el to application.xml, remove myfaces references
  
  Revision  Changes    Path
  1.3       +2 -2      jboss-seam/examples/itext/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/itext/view/whyseam.xhtml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -b -r1.2 -r1.3
  --- whyseam.xhtml	30 Mar 2007 23:10:40 -0000	1.2
  +++ whyseam.xhtml	5 Apr 2007 22:05:45 -0000	1.3
  @@ -14,9 +14,9 @@
       </f:facet>
       
       <p:image alignment="right" wrap="true" value="/jboss.jpg" /> 
  -    <p:font size="24"><p:paragraph spacingAfter="50">Ten Good Reasons To Use Seam</p:paragraph></p:font>  
  +    <p:font size="24"><p:paragraph backgroundColor="red" spacingAfter="50">Ten Good Reasons To Use Seam</p:paragraph></p:font>  
   
  -    <p:font size="18"><p:paragraph>It's the quickest way to get "rich"</p:paragraph></p:font>
  +    <p:font color="blue" 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>