[seam-commits] Seam SVN: r15433 - branches/enterprise/WFK-2_1/distribution/src/main/assembly.

[seam-commits at lists.jboss.org]

Author: manaRH
Date: 2013-03-01 10:15:47 -0500 (Fri, 01 Mar 2013)
New Revision: 15433

Modified:
   branches/enterprise/WFK-2_1/distribution/src/main/assembly/seam23migration.txt
Log:
bz876969 replaced outstanding AS7 with EAP 6.x

Modified: branches/enterprise/WFK-2_1/distribution/src/main/assembly/seam23migration.txt
===================================================================
--- branches/enterprise/WFK-2_1/distribution/src/main/assembly/seam23migration.txt	2013-02-28 08:45:51 UTC (rev 15432)
+++ branches/enterprise/WFK-2_1/distribution/src/main/assembly/seam23migration.txt	2013-03-01 15:15:47 UTC (rev 15433)
@@ -87,13 +87,13 @@
 <your_application>/#{ejbName}/local to java:app/<application-module-name>/#{ejbName} like
  for instance in WEB-INF/components.xml change jndiPattern from: seam-mail/#{ejbName}/local to java:app/seam-mail-ejb/#{ejbName}
 
-JBoss AS 7.1 deployment
+EAP 6.x deployment
 --------------------------
 
-If you using for development or testing default datasource in JBoss AS 7.1, change jndi string in your persistence.xml
+If you using for development or testing default datasource in EAP 6.x, change jndi string in your persistence.xml
 from  java:/DefaultDS to java:jboss/datasources/ExampleDS.
 
-JBoss AS 7 has got refactored classloading and specific classloading of bundled or provided libraries can be managed in 
+EAP 6.x has got refactored classloading and specific classloading of bundled or provided libraries can be managed in 
 jboss-deployment-structure.xml, which should be placed in META-INF directory of your application. Minimal content for
 Seam 2.3 based application is:
 <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0">
@@ -112,8 +112,8 @@
 Dependency changes (Maven)
 --------------------------
 
-The "provided" platform is now JBoss AS 7.1.x, therefore all Java EE dependencies included
-in AS 7 are now marked as provided. Seam uses JBoss Java EE BOM files through Seam BOM file for declaring dependencies.
+The "provided" platform is now EAP 6.x, therefore all Java EE dependencies included
+in EAP 6.x are now marked as provided. Seam uses JBoss Java EE BOM files through Seam BOM file for declaring dependencies.
 You should add import of org.jboss.seam:bom only and then just use the dependency groupId:artifactId[:scope] wherever in
 your maven project. The following snippet uses version property ${seam.version}, which you can replace by real string
 version or define it as current latest available 2.3.x release.