June 2008 - seam-commits - Jboss List Archives

by seam-commits＠lists.jboss.org

Author: jbalunas(a)redhat.com Date: 2008-06-13 13:53:13 -0400 (Fri, 13 Jun 2008) New Revision: 8379 Modified: trunk/release-process.txt Log: update Modified: trunk/release-process.txt =================================================================== --- trunk/release-process.txt 2008-06-13 17:52:24 UTC (rev 8378) +++ trunk/release-process.txt 2008-06-13 17:53:13 UTC (rev 8379) @@ -94,6 +94,7 @@ changelog.txt doc examples + extras lgpl.txt lib readme.txt @@ -163,10 +164,11 @@ - ex. "rm -Rf ~/.m2" - <TODO document way to set local repo settings for clean build/> - Create a copy of the $DIST directory + - rename the copy with "*.orig" - the idea is the leave the original pristine for example testing. ** Source verification ** - - In the copy run "ant > ../releaselogs/x.x.x.XX.sourcebuild.txt" + - run "ant > ../releaselogs/x.x.x.XX.sourcebuild.txt" - diff the original and the built versions of the $DIST directories - only difference should be build related - <TODO: list expected differences/> @@ -175,8 +177,7 @@ - Should be no differences except version of ant and/or jdk versions ** Dependency report ** - - In the copy run: - - "ant dependencyReport > ../releaselogs/x.x.x.XX.dependencybuild.txt" + - "ant dependencyReport > ../releaselogs/x.x.x.XX.dependencybuild.txt" - run "cp ./dependency-report.txt ../releaselogs" - Review for snapshot dependencies - there should be none. @@ -184,15 +185,19 @@ - <TODO: A tool is needed to do this effectively/> ** Testsuite execution ** - - In the copy run : - - "ant -Dvalidate.xml=true cleanall testall testreport + - "ant -Dvalidate.xml=true cleanall testall testreport > ../releaselogs/x.x.x.XX.testallreport.txt" - check report/junit-noframes.html - There should be no failures or errors. - run "cp -R test-output ../releaselogs" - run "cp -R test-report ../releaselogs" + + ** Compare the original distribtion to the one used for the testing. + - Review changes in thirdparty jars, directories, and files. + - <TODO: generate list of acceptable difference> - - You can delete the dist copy + - Delete or rename to original dist. + - Rename the "*.orig" back to the original name Example verification -------------------- @@ -241,7 +246,6 @@ - seampay - seamspace - spring - - takeaway - todo (tutorial) - ui - wiki (not ready for testing until 2.1.X) @@ -267,7 +271,10 @@ JBDS and seam-gen verification ------------------------------ -These tests use a stable version of MySQL and the latest release of JBDS. +These tests use a stable version of MySQL and the latest release of JBDS. Be sure +to use the latest stable release of tools (2.1.1.GA at the time of writing), and +to also apply the JBoss tools provided WTP patch. <TODO: update is version changes +behavior> * export the following tables to MySQL: CREATE TABLE `Person` ( @@ -341,8 +348,7 @@ - Create "new Seam Action" and "new Seam Form" - Test generated pages (check hot deployment of Seam components, html) - Test running unit tests from Eclipse -* JBDS new EAR project - - <NOTE JBIDE-1862 will require changes to the generated project/> +* JBDS new EAR project - Reverse engineer entities from MySQL - Create "new Seam Action" and "new Seam Form" - Test generated pages (check hot deployment of Seam components, html) @@ -367,9 +373,11 @@ - user both text search and search button - change dates, and options in the booking - confirm, logout, login, verify confirmation, cancel confirmation + - <NOTE: can not confirm booking ATM> - Conversation handling - launch several hotels booking conv. from the search page - individually confirm and switch between conversations. + - <NOTE: Can not lauch into multiple conversations ATM> - <NOTE: logging in/out through the portlet, registering new users, and changing passwords do not work, and jiras have been entered for them to be removed as it is integrated with portal auth/> @@ -378,20 +386,12 @@ - edit the $PBR_SRC/examples/seam/booking/seamBookingPortlet/pom.xml file - adjust the seam version properties at the top of the file - build the example by running "mvn install" in the $PBR_SRC/examples dir - - <NOTE: You may need to remove the "javassist.jar" from both the EAR + - <NOTE: You need to remove the "javassist.jar" from both the EAR and WAR lib directories. This is related to PBR-2 - but for some reason the javassist.jar is still placed in both./> * Deploy a second version of the booking example as a separate portlet - - <TODO: this is not supported in the bridge yet - defer/> + - <TODO: DEFER - this is not supported in the bridge yet/> - <TODO: there may be a new chatroom seam portlet for this testing/> -* Build the seam identity extension with the booking example - - <TODO this seems to be done in the 1.0.0.B2 PBR release automatically - - verify/> - - <TODO add reference link to the instructions if needed/> - - Go to the booking demo seamBookingPortlet/pom.xml - - go to the bottom and uncomment the identity module. - - Build the booking demo and log in via the portal admin link. - - this should automatically logs you into the seam booking demo Document review --------------- @@ -416,8 +416,7 @@ - <QUESTION: do we want to create md5 files for the archives/> - <NOTE: not for 2.0.X/> - upload the .zip and .tar.gz and md5 files - - FTP "upload.sf.net/incoming" - - <NOTE: sf upload process may have changed - check during next release/> + - FTP to your SF users "/incoming" directory * Login to sourceforge.org and go to jboss.org project - Under admin tab click on "file releases" @@ -443,6 +442,7 @@ - Review and Commit the release changes to repository.jboss.org - simple script to add new files to SVN - svn status | grep "^\?" | awk '{print $2}' | xargs svn add + - note if you've added this to eclipse you may need to revert ".project" - they still need to be reviewed and commited. * Create draft of the documentation and download pages on seamframework.org @@ -462,6 +462,7 @@ * Login to sourceforge.org and modify the Seam release entry - Change the date to today - Change "Status" to active + - Provide the link to the SF download page for the release for announcements. * Update the documentation and download pages on seamframework.org with drafts. * Update Jira so that version shows as "released" * Announce the release

16 years, 6 months

1
0
0 / 0

Seam SVN: r8378 - branches/Seam_2_0.

by seam-commits＠lists.jboss.org

Author: jbalunas(a)redhat.com Date: 2008-06-13 13:52:24 -0400 (Fri, 13 Jun 2008) New Revision: 8378 Modified: branches/Seam_2_0/release-process.txt Log: updated Modified: branches/Seam_2_0/release-process.txt =================================================================== --- branches/Seam_2_0/release-process.txt 2008-06-13 14:36:30 UTC (rev 8377) +++ branches/Seam_2_0/release-process.txt 2008-06-13 17:52:24 UTC (rev 8378) @@ -92,6 +92,7 @@ changelog.txt doc examples + extras lgpl.txt lib readme.txt @@ -161,10 +162,11 @@ - ex. "rm -Rf ~/.m2" - <TODO document way to set local repo settings for clean build/> - Create a copy of the $DIST directory + - rename the copy with "*.orig" - the idea is the leave the original pristine for example testing. ** Source verification ** - - In the copy run "ant > ../releaselogs/x.x.x.XX.sourcebuild.txt" + - run "ant > ../releaselogs/x.x.x.XX.sourcebuild.txt" - diff the original and the built versions of the $DIST directories - only difference should be build related - <TODO: list expected differences/> @@ -173,8 +175,7 @@ - Should be no differences except version of ant and/or jdk versions ** Dependency report ** - - In the copy run: - - "ant dependencyReport > ../releaselogs/x.x.x.XX.dependencybuild.txt" + - "ant dependencyReport > ../releaselogs/x.x.x.XX.dependencybuild.txt" - run "cp ./dependency-report.txt ../releaselogs" - Review for snapshot dependencies - there should be none. @@ -182,15 +183,19 @@ - <TODO: A tool is needed to do this effectively/> ** Testsuite execution ** - - In the copy run : - - "ant -Dvalidate.xml=true cleanall testall testreport + - "ant -Dvalidate.xml=true cleanall testall testreport > ../releaselogs/x.x.x.XX.testallreport.txt" - check report/junit-noframes.html - There should be no failures or errors. - run "cp -R test-output ../releaselogs" - run "cp -R test-report ../releaselogs" + + ** Compare the original distribtion to the one used for the testing. + - Review changes in thirdparty jars, directories, and files. + - <TODO: generate list of acceptable difference> - - You can delete the dist copy + - Delete or rename to original dist. + - Rename the "*.orig" back to the original name Example verification -------------------- @@ -239,10 +244,8 @@ - seampay - seamspace - spring - - takeaway - todo (tutorial) - ui - - wiki (not ready for testing until 2.1.X) * Tomcat 6 examples - Note: use JBoss embedded unless specified differently - blog (tutorial) @@ -265,7 +268,10 @@ JBDS and seam-gen verification ------------------------------ -These tests use a stable version of MySQL and the latest release of JBDS. +These tests use a stable version of MySQL and the latest release of JBDS. Be sure +to use the latest stable release of tools (2.1.1.GA at the time of writing), and +to also apply the JBoss tools provided WTP patch. <TODO: update is version changes +behavior> * export the following tables to MySQL: CREATE TABLE `Person` ( @@ -339,8 +345,7 @@ - Create "new Seam Action" and "new Seam Form" - Test generated pages (check hot deployment of Seam components, html) - Test running unit tests from Eclipse -* JBDS new EAR project - - <NOTE JBIDE-1862 will require changes to the generated project/> +* JBDS new EAR project - Reverse engineer entities from MySQL - Create "new Seam Action" and "new Seam Form" - Test generated pages (check hot deployment of Seam components, html) @@ -365,9 +370,11 @@ - user both text search and search button - change dates, and options in the booking - confirm, logout, login, verify confirmation, cancel confirmation + - <NOTE: can not confirm booking ATM> - Conversation handling - launch several hotels booking conv. from the search page - individually confirm and switch between conversations. + - <NOTE: Can not lauch into multiple conversations ATM> - <NOTE: logging in/out through the portlet, registering new users, and changing passwords do not work, and jiras have been entered for them to be removed as it is integrated with portal auth/> @@ -376,20 +383,12 @@ - edit the $PBR_SRC/examples/seam/booking/seamBookingPortlet/pom.xml file - adjust the seam version properties at the top of the file - build the example by running "mvn install" in the $PBR_SRC/examples dir - - <NOTE: You may need to remove the "javassist.jar" from both the EAR + - <NOTE: You need to remove the "javassist.jar" from both the EAR and WAR lib directories. This is related to PBR-2 - but for some reason the javassist.jar is still placed in both./> * Deploy a second version of the booking example as a separate portlet - - <TODO: this is not supported in the bridge yet - defer/> + - <TODO: DEFER - this is not supported in the bridge yet/> - <TODO: there may be a new chatroom seam portlet for this testing/> -* Build the seam identity extension with the booking example - - <TODO this seems to be done in the 1.0.0.B2 PBR release automatically - - verify/> - - <TODO add reference link to the instructions if needed/> - - Go to the booking demo seamBookingPortlet/pom.xml - - go to the bottom and uncomment the identity module. - - Build the booking demo and log in via the portal admin link. - - this should automatically logs you into the seam booking demo Document review --------------- @@ -414,8 +413,7 @@ - <QUESTION: do we want to create md5 files for the archives/> - <NOTE: not for 2.0.X/> - upload the .zip and .tar.gz and md5 files - - FTP "upload.sf.net/incoming" - - <NOTE: sf upload process may have changed - check during next release/> + - FTP to your SF users "/incoming" directory * Login to sourceforge.org and go to jboss.org project - Under admin tab click on "file releases" @@ -441,6 +439,7 @@ - Review and Commit the release changes to repository.jboss.org - simple script to add new files to SVN - svn status | grep "^\?" | awk '{print $2}' | xargs svn add + - note if you've added this to eclipse you may need to revert ".project" - they still need to be reviewed and commited. * Create draft of the documentation and download pages on seamframework.org @@ -460,6 +459,7 @@ * Login to sourceforge.org and modify the Seam release entry - Change the date to today - Change "Status" to active + - Provide the link to the SF download page for the release for announcements. * Update the documentation and download pages on seamframework.org with drafts. * Update Jira so that version shows as "released" * Announce the release

16 years, 6 months

1
0
0 / 0

Seam SVN: r8377 - branches/Seam_2_0/build.

by seam-commits＠lists.jboss.org

Author: jbalunas(a)redhat.com Date: 2008-06-13 10:36:30 -0400 (Fri, 13 Jun 2008) New Revision: 8377 Modified: branches/Seam_2_0/build/build.xml Log: updated to deploy AS5 interop jar to repository. Modified: branches/Seam_2_0/build/build.xml =================================================================== --- branches/Seam_2_0/build/build.xml 2008-06-12 19:14:41 UTC (rev 8376) +++ branches/Seam_2_0/build/build.xml 2008-06-13 14:36:30 UTC (rev 8377) @@ -47,6 +47,7 @@ <deployWithSources pom="${pdf.pom}" jar="${lib.dir}/jboss-seam-pdf.jar" repositoryId="offline.repository.jboss.org" srcjar="${lib.dir}/src/jboss-seam-pdf-sources.jar"/> <deployWithSources pom="${remoting.pom}" jar="${lib.dir}/jboss-seam-remoting.jar" repositoryId="offline.repository.jboss.org" srcjar="${lib.dir}/src/jboss-seam-remoting-sources.jar"/> <deployWithSources pom="${ui.pom}" jar="${lib.dir}/jboss-seam-ui.jar" repositoryId="offline.repository.jboss.org" srcjar="${lib.dir}/src/jboss-seam-ui-sources.jar"/> + <deployWithSources pom="${jbas5.pom}" jar="${lib.dir}/interop/jboss-seam-jbas5.jar" repositoryId="offline.repository.jboss.org" srcjar="${lib.dir}/interop/src/jboss-seam-jbas5-sources.jar"/> <deployExample name="booking" repositoryId="offline.repository.jboss.org"/> <deployExampleNoDs name="numberguess" repositoryId="offline.repository.jboss.org"/> <deployExample name="dvd" path="${seam.dir}/examples/dvdstore" repositoryId="offline.repository.jboss.org"/>

16 years, 6 months

1
0
0 / 0

Seam SVN: r8376 - tags/JBoss_Seam_2_0_3_CR1/examples/blog/resources.

by seam-commits＠lists.jboss.org

Author: jbalunas(a)redhat.com Date: 2008-06-12 15:14:41 -0400 (Thu, 12 Jun 2008) New Revision: 8376 Added: tags/JBoss_Seam_2_0_3_CR1/examples/blog/resources/import.sql Log: copy fix for JBSEAM-3101 to JBoss_Seam_2_0_3_CR1 tag Copied: tags/JBoss_Seam_2_0_3_CR1/examples/blog/resources/import.sql (from rev 8375, branches/Seam_2_0/examples/blog/resources/import.sql) =================================================================== --- tags/JBoss_Seam_2_0_3_CR1/examples/blog/resources/import.sql (rev 0) +++ tags/JBoss_Seam_2_0_3_CR1/examples/blog/resources/import.sql 2008-06-12 19:14:41 UTC (rev 8376) @@ -0,0 +1,5 @@ +insert into blog (name, description, locale, timezone, password) values ('JBoss Seam Blog', 'An example of a RESTful Seam application', 'en_AU', 'PST', 'tokyo') +insert into hitcount (blog_name, pageviews) values ('JBoss Seam Blog', 1000) +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 ^superscript^; you can easily enter links, lists, quotes and code blocks.'+char(10)+''+char(10)+'[This is a link.=>http://hibernate.org]'+char(10)+''+char(10)+'You can *not* enter HTML entities, even escaped: \& \< \> \" \ '+char(10)+''+char(10)+'And even emoticons: ;) :-) :-{ ;-)'+char(10)+''+char(10)+'Here is an ordered list:'+char(10)+''+char(10)+'#JBoss'+char(10)+'#Seam'+char(10)+'#Hibernate'+char(10)+''+char(10)+'And this is an unordered list:'+char(10)+''+char(10)+'=jBPM'+char(10)+'=Drools'+char(10)+'=Ajax4JSF'+char(10)+'=Facelets'+char(10)+''+char(10)+'"Here is a quote from someone else"'+char(10)+''+char(10)+'`<p>Here is some code</p>`'+char(10)+''+char(10)+'And! some plain HTML (restricted subset):'+char(10)+''+char(10)+'<table><tr><td>Foo</td><td>Bar</td></tr></table>', '2007-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=>http://safari.oreilly.com/013241273X] about Seam for [O''Reilly=>http://www.oreillynet.com/], which is apparently the hottest selling item on Rough Cuts. InfoQ are running an [excerpt=>http://www.infoq.com/articles/jboss-seam] from the first chapter.'+char(10)+''+char(10)+'Meanwhile, Norman and I have been tearing our way through JIRA issues, 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=>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 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 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=>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 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 this hard stuff is o! ut 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 requests 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-use this existing code unchanged. The planned Spring integration package will provide:'+char(10)+''+char(10)+'=injection of Spring beans into Seam components, using |@In|'+char(10)+'=access to the Spring beans in the EL'+char(10)+'=injection of Seam components into Spring beans using Spring XML'+char(10)+'=integration of the Spring DAO framework with Seam-managed persistence 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 jBPM 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 probably even go as far as:'+char(10)+''+char(10)+'=The ability to treat a Spring bean as a Seam |STATELESS JAVA\_BEAN| component, with a full stack of Seam interceptors'+char(10)+''+char(10)+'In which case a class can simultaneously be a Seam component and a Spring bean, the same way a class can simultaneously be a JSF managed beans, an EJB3 session bean, and a Seam component 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 specifications (EJB) did, and so there is now a yawning hole, exactly where the platform should strongest. (Today the most inadequate specifications in Java are the portlet spec, the atrocious servlet spec, and any JSR relating to security.) Seam 1.1.5 w! ill introduce Seam/Security, an extension to Seam that provides:'+char(10)+''+char(10)+'=a usable authentication layer'+char(10)+'=an ACL based permissioning model'+char(10)+'=an optional (customizable) user/role model'+char(10)+'=a totally cool (at least we think so) authorization mechanism based upon EL and Drools'+char(10)+''+char(10)+'The permissioning 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 administration of permissions, users/roles and rules. OK, I''m sure that sounds pretty vague now, but stay tuned.'+char(10)+''+char(10)+'++++Seam and iText'+char(10)+'Generating PDF is amazingly unsexy, but also incredibly useful. Seam 1.1.5 will 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)+'`<it:document xmlns:f="http://java.sun.com/jsf/co re"'+char(10)+' xmlns:it="http://jboss.com/products/seam/pdf">'+char(10)+' <it:paragraph>Hello World!</it:paragraph>'+char(10)+'</f:view>`'+char(10)+''+char(10)+'++++Integration of seam-gen with Hibernate Tools'+char(10)+''+char(10)+'Rails has made commandline tools popular for 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 integrated with 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 down 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 initiative 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')

16 years, 6 months

1
0
0 / 0

Seam SVN: r8375 - tags/JBoss_Seam_2_0_3_CR1/examples/blog/resources.

by seam-commits＠lists.jboss.org

Author: jbalunas(a)redhat.com Date: 2008-06-12 15:14:29 -0400 (Thu, 12 Jun 2008) New Revision: 8375 Removed: tags/JBoss_Seam_2_0_3_CR1/examples/blog/resources/import.sql Log: remove original for JBSEAM-3101 Deleted: tags/JBoss_Seam_2_0_3_CR1/examples/blog/resources/import.sql =================================================================== --- tags/JBoss_Seam_2_0_3_CR1/examples/blog/resources/import.sql 2008-06-12 18:53:18 UTC (rev 8374) +++ tags/JBoss_Seam_2_0_3_CR1/examples/blog/resources/import.sql 2008-06-12 19:14:29 UTC (rev 8375) @@ -1,5 +0,0 @@ -insert into blog (name, description, locale, timezone, password) values ('JBoss Seam Blog', 'An example of a RESTful Seam application', 'en_AU', 'PST', 'tokyo') -insert into hitcount (blog_name, pageviews) values ('JBoss Seam Blog', 1000) -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 ^superscript^; you can easily enter links, lists, quotes and code blocks.'+char(10)+''+char(10)+'[This is a link.=>http://hibernate.org]'+char(10)+''+char(10)+'You can *not* enter HTML entities, even escaped: \& \< \> \" \ '+char(10)+''+char(10)+'And even emoticons: ;) :-) :-{ ;-)'+char(10)+''+char(10)+'Here is an ordered list:'+char(10)+''+char(10)+'#JBoss'+char(10)+'#Seam'+char(10)+'#Hibernate'+char(10)+''+char(10)+'And this is an unordered list:'+char(10)+''+char(10)+'=jBPM'+char(10)+'=Drools'+char(10)+'=Ajax4JSF'+char(10)+'=Facelets'+char(10)+''+char(10)+'"Here is a quote from someone else"'+char(10)+''+char(10)+'`<p>Here is some code</p>`'+char(10)+''+char(10)+'And! some plain HTML (restricted subset):'+char(10)+''+char(10)+'<table style="border:1px solid blue;"><tr><td>Foo</td><td>Bar</td></tr></table>', '2007-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=>http://safari.oreilly.com/013241273X] about Seam for [O''Reilly=>http://www.oreillynet.com/], which is apparently the hottest selling item on Rough Cuts. InfoQ are running an [excerpt=>http://www.infoq.com/articles/jboss-seam] from the first chapter.'+char(10)+''+char(10)+'Meanwhile, Norman and I have been tearing our way through JIRA issues, 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=>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 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 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=>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 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 this hard stuff is o! ut 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 requests 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-use this existing code unchanged. The planned Spring integration package will provide:'+char(10)+''+char(10)+'=injection of Spring beans into Seam components, using |@In|'+char(10)+'=access to the Spring beans in the EL'+char(10)+'=injection of Seam components into Spring beans using Spring XML'+char(10)+'=integration of the Spring DAO framework with Seam-managed persistence 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 jBPM 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 probably even go as far as:'+char(10)+''+char(10)+'=The ability to treat a Spring bean as a Seam |STATELESS JAVA\_BEAN| component, with a full stack of Seam interceptors'+char(10)+''+char(10)+'In which case a class can simultaneously be a Seam component and a Spring bean, the same way a class can simultaneously be a JSF managed beans, an EJB3 session bean, and a Seam component 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 specifications (EJB) did, and so there is now a yawning hole, exactly where the platform should strongest. (Today the most inadequate specifications in Java are the portlet spec, the atrocious servlet spec, and any JSR relating to security.) Seam 1.1.5 w! ill introduce Seam/Security, an extension to Seam that provides:'+char(10)+''+char(10)+'=a usable authentication layer'+char(10)+'=an ACL based permissioning model'+char(10)+'=an optional (customizable) user/role model'+char(10)+'=a totally cool (at least we think so) authorization mechanism based upon EL and Drools'+char(10)+''+char(10)+'The permissioning 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 administration of permissions, users/roles and rules. OK, I''m sure that sounds pretty vague now, but stay tuned.'+char(10)+''+char(10)+'++++Seam and iText'+char(10)+'Generating PDF is amazingly unsexy, but also incredibly useful. Seam 1.1.5 will 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)+'`<it:document xmlns:f="http://java.sun.com/jsf/co re"'+char(10)+' xmlns:it="http://jboss.com/products/seam/pdf">'+char(10)+' <it:paragraph>Hello World!</it:paragraph>'+char(10)+'</f:view>`'+char(10)+''+char(10)+'++++Integration of seam-gen with Hibernate Tools'+char(10)+''+char(10)+'Rails has made commandline tools popular for 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 integrated with 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 down 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 initiative 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')

16 years, 6 months

1
0
0 / 0

Seam SVN: r8374 - trunk/examples/blog/resources.

by seam-commits＠lists.jboss.org

Author: norman.richards(a)jboss.com Date: 2008-06-12 14:53:18 -0400 (Thu, 12 Jun 2008) New Revision: 8374 Modified: trunk/examples/blog/resources/import.sql Log: JBSEAM-3101 Modified: trunk/examples/blog/resources/import.sql =================================================================== --- trunk/examples/blog/resources/import.sql 2008-06-12 18:52:19 UTC (rev 8373) +++ trunk/examples/blog/resources/import.sql 2008-06-12 18:53:18 UTC (rev 8374) @@ -1,5 +1,5 @@ insert into blog (name, description, locale, timezone, password) values ('JBoss Seam Blog', 'An example of a RESTful Seam application', 'en_AU', 'PST', 'tokyo') insert into hitcount (blog_name, pageviews) values ('JBoss Seam Blog', 1000) -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 ^superscript^; you can easily enter links, lists, quotes and code blocks.'+char(10)+''+char(10)+'[This is a link.=>http://hibernate.org]'+char(10)+''+char(10)+'You can *not* enter HTML entities, even escaped: \& \< \> \" \ '+char(10)+''+char(10)+'And even emoticons: ;) :-) :-{ ;-)'+char(10)+''+char(10)+'Here is an ordered list:'+char(10)+''+char(10)+'#JBoss'+char(10)+'#Seam'+char(10)+'#Hibernate'+char(10)+''+char(10)+'And this is an unordered list:'+char(10)+''+char(10)+'=jBPM'+char(10)+'=Drools'+char(10)+'=Ajax4JSF'+char(10)+'=Facelets'+char(10)+''+char(10)+'"Here is a quote from someone else"'+char(10)+''+char(10)+'`<p>Here is some code</p>`'+char(10)+''+char(10)+'And! some plain HTML (restricted subset):'+char(10)+''+char(10)+'<table style="border:1px solid blue;"><tr><td>Foo</td><td>Bar</td></tr></table>', '2007-01-18 4:00') +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 ^superscript^; you can easily enter links, lists, quotes and code blocks.'+char(10)+''+char(10)+'[This is a link.=>http://hibernate.org]'+char(10)+''+char(10)+'You can *not* enter HTML entities, even escaped: \& \< \> \" \ '+char(10)+''+char(10)+'And even emoticons: ;) :-) :-{ ;-)'+char(10)+''+char(10)+'Here is an ordered list:'+char(10)+''+char(10)+'#JBoss'+char(10)+'#Seam'+char(10)+'#Hibernate'+char(10)+''+char(10)+'And this is an unordered list:'+char(10)+''+char(10)+'=jBPM'+char(10)+'=Drools'+char(10)+'=Ajax4JSF'+char(10)+'=Facelets'+char(10)+''+char(10)+'"Here is a quote from someone else"'+char(10)+''+char(10)+'`<p>Here is some code</p>`'+char(10)+''+char(10)+'And! some plain HTML (restricted subset):'+char(10)+''+char(10)+'<table><tr><td>Foo</td><td>Bar</td></tr></table>', '2007-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=>http://safari.oreilly.com/013241273X] about Seam for [O''Reilly=>http://www.oreillynet.com/], which is apparently the hottest selling item on Rough Cuts. InfoQ are running an [excerpt=>http://www.infoq.com/articles/jboss-seam] from the first chapter.'+char(10)+''+char(10)+'Meanwhile, Norman and I have been tearing our way through JIRA issues, 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=>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 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 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=>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 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 this hard stuff is o! ut 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 requests 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-use this existing code unchanged. The planned Spring integration package will provide:'+char(10)+''+char(10)+'=injection of Spring beans into Seam components, using |@In|'+char(10)+'=access to the Spring beans in the EL'+char(10)+'=injection of Seam components into Spring beans using Spring XML'+char(10)+'=integration of the Spring DAO framework with Seam-managed persistence 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 jBPM 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 probably even go as far as:'+char(10)+''+char(10)+'=The ability to treat a Spring bean as a Seam |STATELESS JAVA\_BEAN| component, with a full stack of Seam interceptors'+char(10)+''+char(10)+'In which case a class can simultaneously be a Seam component and a Spring bean, the same way a class can simultaneously be a JSF managed beans, an EJB3 session bean, and a Seam component 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 specifications (EJB) did, and so there is now a yawning hole, exactly where the platform should strongest. (Today the most inadequate specifications in Java are the portlet spec, the atrocious servlet spec, and any JSR relating to security.) Seam 1.1.5 w! ill introduce Seam/Security, an extension to Seam that provides:'+char(10)+''+char(10)+'=a usable authentication layer'+char(10)+'=an ACL based permissioning model'+char(10)+'=an optional (customizable) user/role model'+char(10)+'=a totally cool (at least we think so) authorization mechanism based upon EL and Drools'+char(10)+''+char(10)+'The permissioning 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 administration of permissions, users/roles and rules. OK, I''m sure that sounds pretty vague now, but stay tuned.'+char(10)+''+char(10)+'++++Seam and iText'+char(10)+'Generating PDF is amazingly unsexy, but also incredibly useful. Seam 1.1.5 will 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)+'`<it:document xmlns:f="http://java.sun.com/jsf/co re"'+char(10)+' xmlns:it="http://jboss.com/products/seam/pdf">'+char(10)+' <it:paragraph>Hello World!</it:paragraph>'+char(10)+'</f:view>`'+char(10)+''+char(10)+'++++Integration of seam-gen with Hibernate Tools'+char(10)+''+char(10)+'Rails has made commandline tools popular for 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 integrated with 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 down 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 initiative 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')

16 years, 6 months

1
0
0 / 0

Seam SVN: r8373 - branches/Seam_2_0/examples/blog/resources.

by seam-commits＠lists.jboss.org

Author: norman.richards(a)jboss.com Date: 2008-06-12 14:52:19 -0400 (Thu, 12 Jun 2008) New Revision: 8373 Modified: branches/Seam_2_0/examples/blog/resources/import.sql Log: JBSEAM-3101 Modified: branches/Seam_2_0/examples/blog/resources/import.sql =================================================================== --- branches/Seam_2_0/examples/blog/resources/import.sql 2008-06-11 20:33:29 UTC (rev 8372) +++ branches/Seam_2_0/examples/blog/resources/import.sql 2008-06-12 18:52:19 UTC (rev 8373) @@ -1,5 +1,5 @@ insert into blog (name, description, locale, timezone, password) values ('JBoss Seam Blog', 'An example of a RESTful Seam application', 'en_AU', 'PST', 'tokyo') insert into hitcount (blog_name, pageviews) values ('JBoss Seam Blog', 1000) -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 ^superscript^; you can easily enter links, lists, quotes and code blocks.'+char(10)+''+char(10)+'[This is a link.=>http://hibernate.org]'+char(10)+''+char(10)+'You can *not* enter HTML entities, even escaped: \& \< \> \" \ '+char(10)+''+char(10)+'And even emoticons: ;) :-) :-{ ;-)'+char(10)+''+char(10)+'Here is an ordered list:'+char(10)+''+char(10)+'#JBoss'+char(10)+'#Seam'+char(10)+'#Hibernate'+char(10)+''+char(10)+'And this is an unordered list:'+char(10)+''+char(10)+'=jBPM'+char(10)+'=Drools'+char(10)+'=Ajax4JSF'+char(10)+'=Facelets'+char(10)+''+char(10)+'"Here is a quote from someone else"'+char(10)+''+char(10)+'`<p>Here is some code</p>`'+char(10)+''+char(10)+'And! some plain HTML (restricted subset):'+char(10)+''+char(10)+'<table style="border:1px solid blue;"><tr><td>Foo</td><td>Bar</td></tr></table>', '2007-01-18 4:00') +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 ^superscript^; you can easily enter links, lists, quotes and code blocks.'+char(10)+''+char(10)+'[This is a link.=>http://hibernate.org]'+char(10)+''+char(10)+'You can *not* enter HTML entities, even escaped: \& \< \> \" \ '+char(10)+''+char(10)+'And even emoticons: ;) :-) :-{ ;-)'+char(10)+''+char(10)+'Here is an ordered list:'+char(10)+''+char(10)+'#JBoss'+char(10)+'#Seam'+char(10)+'#Hibernate'+char(10)+''+char(10)+'And this is an unordered list:'+char(10)+''+char(10)+'=jBPM'+char(10)+'=Drools'+char(10)+'=Ajax4JSF'+char(10)+'=Facelets'+char(10)+''+char(10)+'"Here is a quote from someone else"'+char(10)+''+char(10)+'`<p>Here is some code</p>`'+char(10)+''+char(10)+'And! some plain HTML (restricted subset):'+char(10)+''+char(10)+'<table><tr><td>Foo</td><td>Bar</td></tr></table>', '2007-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=>http://safari.oreilly.com/013241273X] about Seam for [O''Reilly=>http://www.oreillynet.com/], which is apparently the hottest selling item on Rough Cuts. InfoQ are running an [excerpt=>http://www.infoq.com/articles/jboss-seam] from the first chapter.'+char(10)+''+char(10)+'Meanwhile, Norman and I have been tearing our way through JIRA issues, 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=>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 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 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=>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 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 this hard stuff is o! ut 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 requests 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-use this existing code unchanged. The planned Spring integration package will provide:'+char(10)+''+char(10)+'=injection of Spring beans into Seam components, using |@In|'+char(10)+'=access to the Spring beans in the EL'+char(10)+'=injection of Seam components into Spring beans using Spring XML'+char(10)+'=integration of the Spring DAO framework with Seam-managed persistence 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 jBPM 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 probably even go as far as:'+char(10)+''+char(10)+'=The ability to treat a Spring bean as a Seam |STATELESS JAVA\_BEAN| component, with a full stack of Seam interceptors'+char(10)+''+char(10)+'In which case a class can simultaneously be a Seam component and a Spring bean, the same way a class can simultaneously be a JSF managed beans, an EJB3 session bean, and a Seam component 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 specifications (EJB) did, and so there is now a yawning hole, exactly where the platform should strongest. (Today the most inadequate specifications in Java are the portlet spec, the atrocious servlet spec, and any JSR relating to security.) Seam 1.1.5 w! ill introduce Seam/Security, an extension to Seam that provides:'+char(10)+''+char(10)+'=a usable authentication layer'+char(10)+'=an ACL based permissioning model'+char(10)+'=an optional (customizable) user/role model'+char(10)+'=a totally cool (at least we think so) authorization mechanism based upon EL and Drools'+char(10)+''+char(10)+'The permissioning 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 administration of permissions, users/roles and rules. OK, I''m sure that sounds pretty vague now, but stay tuned.'+char(10)+''+char(10)+'++++Seam and iText'+char(10)+'Generating PDF is amazingly unsexy, but also incredibly useful. Seam 1.1.5 will 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)+'`<it:document xmlns:f="http://java.sun.com/jsf/co re"'+char(10)+' xmlns:it="http://jboss.com/products/seam/pdf">'+char(10)+' <it:paragraph>Hello World!</it:paragraph>'+char(10)+'</f:view>`'+char(10)+''+char(10)+'++++Integration of seam-gen with Hibernate Tools'+char(10)+''+char(10)+'Rails has made commandline tools popular for 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 integrated with 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 down 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 initiative 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')

16 years, 6 months

1
0
0 / 0

Seam SVN: r8372 - trunk/src/main/org/jboss/seam/persistence.

by seam-commits＠lists.jboss.org

Author: norman.richards(a)jboss.com Date: 2008-06-11 16:33:29 -0400 (Wed, 11 Jun 2008) New Revision: 8372 Modified: trunk/src/main/org/jboss/seam/persistence/ManagedPersistenceContext.java Log: JBSEAM-3094 Modified: trunk/src/main/org/jboss/seam/persistence/ManagedPersistenceContext.java =================================================================== --- trunk/src/main/org/jboss/seam/persistence/ManagedPersistenceContext.java 2008-06-11 20:27:39 UTC (rev 8371) +++ trunk/src/main/org/jboss/seam/persistence/ManagedPersistenceContext.java 2008-06-11 20:33:29 UTC (rev 8372) @@ -140,27 +140,12 @@ { throw new IllegalStateException("cannot passivate persistence context with active transaction"); } - //need to create a context, because this can get called - //outside the JSF request, and we want to use the - //PersistenceProvider object - boolean createContext = !Contexts.isApplicationContextActive(); - if (createContext) Lifecycle.beginCall(); - try - { - if ( entityManager!=null && !PersistenceProvider.instance().isDirty(entityManager) ) - { - entityManager.close(); - entityManager = null; - } - } - finally - { - if (createContext) Lifecycle.endCall(); - } } //we can't use @PostActivate because it is intercept NEVER - public void sessionDidActivate(HttpSessionEvent event) {} + public void sessionDidActivate(HttpSessionEvent event) { + entityManager = null; + } @Destroy public void destroy()

16 years, 6 months

1
0
0 / 0

Seam SVN: r8371 - branches/Seam_2_0/src/main/org/jboss/seam/persistence.

by seam-commits＠lists.jboss.org

Author: norman.richards(a)jboss.com Date: 2008-06-11 16:27:39 -0400 (Wed, 11 Jun 2008) New Revision: 8371 Modified: branches/Seam_2_0/src/main/org/jboss/seam/persistence/ManagedPersistenceContext.java Log: JBSEAM-3094 Modified: branches/Seam_2_0/src/main/org/jboss/seam/persistence/ManagedPersistenceContext.java =================================================================== --- branches/Seam_2_0/src/main/org/jboss/seam/persistence/ManagedPersistenceContext.java 2008-06-11 13:05:05 UTC (rev 8370) +++ branches/Seam_2_0/src/main/org/jboss/seam/persistence/ManagedPersistenceContext.java 2008-06-11 20:27:39 UTC (rev 8371) @@ -134,34 +134,18 @@ } //we can't use @PrePassivate because it is intercept NEVER - public void sessionWillPassivate(HttpSessionEvent event) - { - if (synchronizationRegistered) - { - throw new IllegalStateException("cannot passivate persistence context with active transaction"); - } - //need to create a context, because this can get called - //outside the JSF request, and we want to use the - //PersistenceProvider object - boolean createContext = !Contexts.isApplicationContextActive(); - if (createContext) Lifecycle.beginCall(); - try - { - if ( entityManager!=null && !PersistenceProvider.instance().isDirty(entityManager) ) - { - entityManager.close(); - entityManager = null; - } - } - finally - { - if (createContext) Lifecycle.endCall(); - } - } + public void sessionWillPassivate(HttpSessionEvent event) + { + if (synchronizationRegistered) { + throw new IllegalStateException("cannot passivate persistence context with active transaction"); + } + } - //we can't use @PostActivate because it is intercept NEVER - public void sessionDidActivate(HttpSessionEvent event) {} - + //we can't use @PostActivate because it is intercept NEVER + public void sessionDidActivate(HttpSessionEvent event) { + entityManager = null; + } + @Destroy public void destroy() {

16 years, 6 months

1
0
0 / 0

Seam SVN: r8370 - branches/Seam_2_0_FP/build.

by seam-commits＠lists.jboss.org

Author: manaRH Date: 2008-06-11 09:05:05 -0400 (Wed, 11 Jun 2008) New Revision: 8370 Modified: branches/Seam_2_0_FP/build/root.pom.xml Log: added repository for latest version of jsf 1.2 Modified: branches/Seam_2_0_FP/build/root.pom.xml =================================================================== --- branches/Seam_2_0_FP/build/root.pom.xml 2008-06-10 20:34:56 UTC (rev 8369) +++ branches/Seam_2_0_FP/build/root.pom.xml 2008-06-11 13:05:05 UTC (rev 8370) @@ -34,6 +34,11 @@ <name>JBoss Snapshot Repository</name> <url>http://snapshots.jboss.org/maven2</url> </repository> + <repository> + <id>java.net</id> + <url>http://download.java.net/maven/1</url> + <layout>legacy</layout> + </repository> </repositories>  @@ -192,13 +197,13 @@ <dependency> <groupId>javax.faces</groupId> <artifactId>jsf-api</artifactId> - <version>1.2_04-p02</version> + <version>1.2_08</version> </dependency> <dependency> <groupId>javax.faces</groupId> <artifactId>jsf-impl</artifactId> - <version>1.2_04-p02</version> + <version>1.2_08</version> <exclusions> <exclusion> <groupId>commons-collections</groupId>

16 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

seam-commits June 2008