From seam-commits at lists.jboss.org Mon Apr 7 17:05:48 2008 Content-Type: multipart/mixed; boundary="===============2581397395207820873==" MIME-Version: 1.0 From: seam-commits at lists.jboss.org To: seam-commits at lists.jboss.org Subject: [seam-commits] Seam SVN: r7839 - trunk/examples/blog/resources. Date: Mon, 07 Apr 2008 17:05:48 -0400 Message-ID: --===============2581397395207820873== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: norman.richards(a)jboss.com Date: 2008-04-07 17:05:48 -0400 (Mon, 07 Apr 2008) New Revision: 7839 Modified: trunk/examples/blog/resources/import.sql Log: JBSEAM-2840 Modified: trunk/examples/blog/resources/import.sql =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/examples/blog/resources/import.sql 2008-04-07 20:56:49 UTC (rev 7= 838) +++ trunk/examples/blog/resources/import.sql 2008-04-07 21:05:48 UTC (rev 7= 839) @@ -2,4 +2,4 @@ insert into hitcount (blog_name, pageviews) values ('JBoss Seam Blog', 100= 0) insert into blogentry (blog_name, id, title, excerpt, body, date) values (= 'JBoss Seam Blog', 'seamtext', 'Introducing Seam Text', null, 'Seam Text is= a human-friendly language for formatting text in blogs, forums and wikis. = It''s easy to enter text in *emphasis*, |monospace|, ~deleted~ or ^superscr= ipt^; you can easily enter links, lists, quotes and code blocks.'+char(10)+= ''+char(10)+'[This is a link.=3D>http://hibernate.org]'+char(10)+''+char(10= )+'You can *not* enter HTML entities, even escaped: \& \< \> \&qu= ot; \ '+char(10)+''+char(10)+'And even emoticons: ;) :-) :-{ ;-)'+char= (10)+''+char(10)+'Here is an ordered list:'+char(10)+''+char(10)+'#JBoss'+c= har(10)+'#Seam'+char(10)+'#Hibernate'+char(10)+''+char(10)+'And this is an = unordered list:'+char(10)+''+char(10)+'=3DjBPM'+char(10)+'=3DDrools'+char(1= 0)+'=3DAjax4JSF'+char(10)+'=3DFacelets'+char(10)+''+char(10)+'"Here is a qu= ote from someone else"'+char(10)+''+char(10)+'`

Here is some code

`'+c= har(10)+''+char(10)+'And! some plain HTML (restricted subset):'+char(10)+''+char(10)+'
FooBar
', '20= 07-01-18 4:00') insert into blogentry (blog_name, id, title, excerpt, body, date) values (= 'JBoss Seam Blog', 'book', 'Seam book excerpt on InfoQ', null, 'Michael and= Thomas are writing [a book=3D>http://safari.oreilly.com/013241273X] about = Seam for [O''Reilly=3D>http://www.oreillynet.com/], which is apparently the= hottest selling item on Rough Cuts. InfoQ are running an [excerpt=3D>http:= //www.infoq.com/articles/jboss-seam] from the first chapter.'+char(10)+''+c= har(10)+'Meanwhile, Norman and I have been tearing our way through JIRA iss= ues, and so 1.1.1 will be ready to go when I get back from vacation :-)', '= 2006-12-19 19:00') -insert into blogentry (blog_name, id, title, excerpt, body, date) values (= 'JBoss Seam Blog', 'roadmap11', 'Seam Roadmap', 'The [1.1 release=3D>http:/= /blog.hibernate.org/cgi-bin/blosxom.cgi/2006/12/13#seam11-goes-ga] involved= a lot of hard work in the guts of Seam, refactoring and fixing bugs, and w= orking with \"tricky\" code that handles concerns like clustering and concu= rrency. Sure, there are many new features, but a lot of the real work is le= ss user-visible. Now that this hard stuff is out of the way, it lets us add= some interesting new stuff pretty quickly. Here''s a quick roadmap for the= next few months:', 'The [1.1 release=3D>http://blog.hibernate.org/cgi-bin/= blosxom.cgi/2006/12/13#seam11-goes-ga] involved a lot of hard work in the g= uts of Seam, refactoring and fixing bugs, and working with \"tricky\" code = that handles concerns like clustering and concurrency. Sure, there are many= new features, but a lot of the real work is less user\-visible. Now that t= his hard stuff is ! out of the way, it lets us add some interesting new stuff pretty quickly. = Here''s a quick roadmap for the next few months:'+char(10)+''+char(10)+'+++= +Spring integration package'+char(10)+''+char(10)+'We''re seeing regular re= quests from people who have existing DAOs and business logic written using = the Spring Framework and want a migration path to Seam that lets them re\-u= se this existing code unchanged. The planned Spring integration package wil= l provide:'+char(10)+''+char(10)+'=3Dinjection of Spring beans into Seam co= mponents, using |@In|'+char(10)+'=3Daccess to the Spring beans in the EL'+c= har(10)+'=3Dinjection of Seam components into Spring beans using Spring XML= '+char(10)+'=3Dintegration of the Spring DAO framework with Seam\-managed p= ersistence contexts'+char(10)+''+char(10)+'So, you''ll be able to easily ca= ll existing code written in Spring from your Seam component, JSF views, or = jBPM process definitions, and have that code be able to take advantage of S= eam''s conversation\-s! cope persistence contexts. For the first time, you can have Spring cod e that isn''t vulnerable to |LazyInitializationException|!'+char(10)+'We''l= l probably even go as far as:'+char(10)+''+char(10)+'=3DThe ability to trea= t a Spring bean as a Seam |STATELESS JAVA\_BEAN| component, with a full sta= ck of Seam interceptors'+char(10)+''+char(10)+'In which case a class can si= multaneously be a Seam component and a Spring bean, the same way a class ca= n simultaneously be a JSF managed beans, an EJB3 session bean, and a Seam c= omponent today.'+char(10)+''+char(10)+'++++Seam\/Security'+char(10)+''+char= (10)+'The most\-requested feature in the Seam forums is security. Unfortuna= tely, the security\-related specifications did not go through the same proc= ess of self\-examination and improvement in Java EE 5 that some other speci= fications (EJB) did, and so there is now a yawning hole, exactly where the = platform should strongest. (Today the most inadequate specifications in Jav= a are the portlet spec, the atrocious servlet spec, and any JSR relating to= security.) Seam! 1.1.5 will introduce Seam\/Security, an extension to Seam that provides:'= +char(10)+''+char(10)+'=3Da usable authentication layer'+char(10)+'=3Dan AC= L based permissioning model'+char(10)+'=3Dan optional (customizable) user\/= role model'+char(10)+'=3Da totally cool (at least we think so) authorizatio= n mechanism based upon EL and Drools'+char(10)+''+char(10)+'The permissioni= ng model lets you do \"row level\" security by writing rules that refer to = the actual object instance that we are checking permissions for.'+char(10)+= ''+char(10)+'A subsequent release will also provide a console for administr= ation of permissions, users\/roles and rules. OK, I''m sure that sounds pre= tty vague now, but stay tuned.'+char(10)+''+char(10)+'++++Seam and iText'+c= har(10)+'Generating PDF is amazingly unsexy, but also incredibly useful. Se= am 1.1.5 will provide a library of JSF controls for iText, letting you quic= kly create JSF templates that are capable of rendering PDF, Text and RTF. T= his will be as easy to! use as:'+char(10)+''+char(10)+'`'+char(10)+' Hello World!'+char(10)+= '`'+char(10)+''+char(10)+'++++Integration of seam\-gen with Hibern= ate Tools'+char(10)+''+char(10)+'Rails has made commandline tools popular f= or web development, and was the inspiration behind seam\-gen. But I''m one = of those recalcitrant IDE kinda guys, and I expect tooling to be properly i= ntegrated with Eclipse. We''ll be updating the GUI for Hibernate Tools to t= ake advantage of the new templates in Seam 1.1, which will let you do every= thing you can do today using seam\-gen, totally within Eclipse.'+char(10)+'= '+char(10)+'++++Seam\/WS'+char(10)+''+char(10)+'We''ve been promising for m= onths that Seam is the killer component model for SOA. Unfortunately, we go= t so bogged down in Seam 1.1 that we''re well behind on our original plan t= o deliver this in 2006.'+char(10)+''+char(10)+'Seam 1.2 will integrate Seam= with the Java E! E 5 Web Services layer and provide support for service conversations in it= s context model (I''ve not yet decided whether this calls for a new |SERVIC= E\_CONVERSATION| context, or whether it is just a different interpretation = of the existing |CONVERSATION| context for a WS invocation.) Eventually, Se= am\/WS will also support service orchestration and conversation recovery vi= a jBPM.'+char(10)+''+char(10)+'Actually, Seam\/WS will just be one piece of= a larger initiative to bring Seam to ESB and SOA environments, but at pres= ent this idea is mostly speculative.'+char(10)+''+char(10)+'Look for a beta= release of Seam 1.2 in Q1.', '2006-12-14 15:29') +insert into blogentry (blog_name, id, title, excerpt, body, date) values (= 'JBoss Seam Blog', 'roadmap11', 'Seam Roadmap', 'The [1.1 release=3D>http:/= /blog.hibernate.org/cgi-bin/blosxom.cgi/2006/12/13#seam11-goes-ga] involved= a lot of hard work in the guts of Seam, refactoring and fixing bugs, and w= orking with \"tricky\" code that handles concerns like clustering and concu= rrency. Sure, there are many new features, but a lot of the real work is le= ss user-visible. Now that this hard stuff is out of the way, it lets us add= some interesting new stuff pretty quickly. Here''s a quick roadmap for the= next few months:', 'The [1.1 release=3D>http://blog.hibernate.org/cgi-bin/= blosxom.cgi/2006/12/13#seam11-goes-ga] involved a lot of hard work in the g= uts of Seam, refactoring and fixing bugs, and working with \"tricky\" code = that handles concerns like clustering and concurrency. Sure, there are many= new features, but a lot of the real work is less user-visible. Now that th= is hard stuff is o! ut of the way, it lets us add some interesting new stuff pretty quickly. H= ere''s a quick roadmap for the next few months:'+char(10)+''+char(10)+'++++= Spring integration package'+char(10)+''+char(10)+'We''re seeing regular req= uests from people who have existing DAOs and business logic written using t= he Spring Framework and want a migration path to Seam that lets them re-use= this existing code unchanged. The planned Spring integration package will = provide:'+char(10)+''+char(10)+'=3Dinjection of Spring beans into Seam comp= onents, using |@In|'+char(10)+'=3Daccess to the Spring beans in the EL'+cha= r(10)+'=3Dinjection of Seam components into Spring beans using Spring XML'+= char(10)+'=3Dintegration of the Spring DAO framework with Seam-managed pers= istence contexts'+char(10)+''+char(10)+'So, you''ll be able to easily call = existing code written in Spring from your Seam component, JSF views, or jBP= M process definitions, and have that code be able to take advantage of Seam= ''s conversation-scope! persistence contexts. For the first time, you can have Spring code th at isn''t vulnerable to |LazyInitializationException|!'+char(10)+'We''ll pr= obably even go as far as:'+char(10)+''+char(10)+'=3DThe ability to treat a = Spring bean as a Seam |STATELESS JAVA\_BEAN| component, with a full stack o= f Seam interceptors'+char(10)+''+char(10)+'In which case a class can simult= aneously be a Seam component and a Spring bean, the same way a class can si= multaneously be a JSF managed beans, an EJB3 session bean, and a Seam compo= nent today.'+char(10)+''+char(10)+'++++Seam/Security'+char(10)+''+char(10)+= 'The most-requested feature in the Seam forums is security. Unfortunately, = the security-related specifications did not go through the same process of = self-examination and improvement in Java EE 5 that some other specification= s (EJB) did, and so there is now a yawning hole, exactly where the platform= should strongest. (Today the most inadequate specifications in Java are th= e portlet spec, the atrocious servlet spec, and any JSR relating to securit= y.) Seam 1.1.5 w! ill introduce Seam/Security, an extension to Seam that provides:'+char(10)= +''+char(10)+'=3Da usable authentication layer'+char(10)+'=3Dan ACL based p= ermissioning model'+char(10)+'=3Dan optional (customizable) user/role model= '+char(10)+'=3Da totally cool (at least we think so) authorization mechanis= m based upon EL and Drools'+char(10)+''+char(10)+'The permissioning model l= ets you do \"row level\" security by writing rules that refer to the actual= object instance that we are checking permissions for.'+char(10)+''+char(10= )+'A subsequent release will also provide a console for administration of p= ermissions, users/roles and rules. OK, I''m sure that sounds pretty vague n= ow, but stay tuned.'+char(10)+''+char(10)+'++++Seam and iText'+char(10)+'Ge= nerating PDF is amazingly unsexy, but also incredibly useful. Seam 1.1.5 wi= ll provide a library of JSF controls for iText, letting you quickly create = JSF templates that are capable of rendering PDF, Text and RTF. This will be= as easy to use as:'+c! har(10)+''+char(10)+'`'+ch= ar(10)+' Hello World!'+char(10)+'`= '+char(10)+''+char(10)+'++++Integration of seam-gen with Hibernate Tools'+c= har(10)+''+char(10)+'Rails has made commandline tools popular for web devel= opment, and was the inspiration behind seam-gen. But I''m one of those reca= lcitrant IDE kinda guys, and I expect tooling to be properly integrated wit= h Eclipse. We''ll be updating the GUI for Hibernate Tools to take advantage= of the new templates in Seam 1.1, which will let you do everything you can= do today using seam-gen, totally within Eclipse.'+char(10)+''+char(10)+'++= ++Seam/WS'+char(10)+''+char(10)+'We''ve been promising for months that Seam= is the killer component model for SOA. Unfortunately, we got so bogged dow= n in Seam 1.1 that we''re well behind on our original plan to deliver this = in 2006.'+char(10)+''+char(10)+'Seam 1.2 will integrate Seam with the Java = EE 5 Web Service! s layer and provide support for service conversations in its context model= (I''ve not yet decided whether this calls for a new |SERVICE\_CONVERSATION= | context, or whether it is just a different interpretation of the existing= |CONVERSATION| context for a WS invocation.) Eventually, Seam/WS will also= support service orchestration and conversation recovery via jBPM.'+char(10= )+''+char(10)+'Actually, Seam/WS will just be one piece of a larger initiat= ive to bring Seam to ESB and SOA environments, but at present this idea is = mostly speculative.'+char(10)+''+char(10)+'Look for a beta release of Seam = 1.2 in Q1.', '2006-12-14 15:29') --===============2581397395207820873==--