[jboss-cvs] JBossAS SVN: r105623 - projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: misty at redhat.com
Date: 2010-06-03 03:10:32 -0400 (Thu, 03 Jun 2010)
New Revision: 105623

Modified:
   projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Wicket.xml
Log:
JBPAPP-4387

Modified: projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Wicket.xml
===================================================================
--- projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Wicket.xml	2010-06-03 07:08:00 UTC (rev 105622)
+++ projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Wicket.xml	2010-06-03 07:10:32 UTC (rev 105623)
@@ -24,7 +24,7 @@
 				A Seam-enabled Wicket application has full access to the all standard Seam contexts: <literal>EVENT</literal>, <literal>CONVERSATION</literal>, <literal>SESSION</literal>, <literal>APPLICATION</literal> and <literal>BUSINESS_PROCESS</literal>. To access a Seam component from Wicket, inject the component with <literal>@In</literal>:
 			</para>
 			 
-<programlisting role="JAVA"><![CDATA[@In(create=true) private HotelBooking hotelBooking;]]>
+<programlisting language="Java" role="JAVA">@In(create=true) private HotelBooking hotelBooking;
 </programlisting>
 			 <note>
 				<para>
@@ -35,7 +35,7 @@
 				You can also outject an object into the Seam contexts from a Wicket component:
 			</para>
 			 
-<programlisting role="JAVA"><![CDATA[@Out(scope=ScopeType.EVENT, required=false) private String verify;]]>
+<programlisting language="Java" role="JAVA">@Out(scope=ScopeType.EVENT, required=false) private String verify;
 </programlisting>
 			 <!-- #modify: <para> TODO Make this more use case driven </para> -->
 		</section>
@@ -46,7 +46,7 @@
 				Secure a Wicket component with the <literal>@Restrict</literal> annotation. This annotation restricts component access to logged in users. It can be placed on the outer component, or any inner components, and is automatically applied to nested classes.
 			</para>
 			 
-<programlisting role="JAVA"><![CDATA[@Restrict public class Main extends WebPage { ...]]>
+<programlisting language="Java" role="JAVA">@Restrict public class Main extends WebPage { ...
 </programlisting>
 			 <para>
 				You can specify a particular restriction with an EL expression in the <literal>value</literal> attribute. (For more detailed information, refer to <xref linkend="security" />.)
@@ -55,13 +55,13 @@
 				Conversations can be demarcated from within a Wicket component by using <literal>@Begin</literal> and <literal>@End</literal>. For example:
 			</para>
 			 
-<programlisting role="JAVA"><![CDATA[
+<programlisting language="Java" role="JAVA">
 item.add(new Link("viewHotel") { 
   @Override @Begin public void onClick() { 
     hotelBooking.selectHotel(hotel); 
     setResponsePage(org.jboss.seam.example.wicket.Hotel.class); 
   } 
-};]]>
+};
 </programlisting>
 			 <para>
 				The semantics here match those in a Seam component. Although the deprecated <literal>ifOutcome</literal> attribute is not supported, <literal>@Begin</literal> and <literal>@End</literal> can be placed on any method.
@@ -70,10 +70,10 @@
 				Your application may contain pages that can only be accessed if the user has a long-running conversation active. To enforce this, use the <literal>@NoConversationPage</literal> annotation:
 			</para>
 			 
-<programlisting><![CDATA[
+<programlisting language="Java" role="JAVA">
 @Restrict 
 @NoConversationPage(Main.class) 
-public class Hotel extends WebPage {...}]]>
+public class Hotel extends WebPage {...}
 </programlisting>
 			 <para>
 				If you want to decouple your application classes further, you can use Seam events. You can raise an event with <literal>Events.instance().raiseEvent("foo")</literal>, or annotate a method <literal>@RaiseEvent("foo")</literal> — if the method returns a non-null outcome without exception, the event will be raised.
@@ -92,7 +92,7 @@
 			To intercept your annotations, Seam must instrument the bytecode of your Wicket classes. There are two possible methods: either place your classes in <literal>WEB-INF/wicket</literal>, so that Seam finds and instruments them at startup, or instrument via the ant task provided in <filename>jboss-seam-wicket-ant.jar</filename> like so:
 		</para>
 		 
-<programlisting role="XML"><![CDATA[
+<programlisting language="XML" role="XML"><![CDATA[
 <taskdef name="instrumentWicket" 
          classname="org.jboss.seam.wicket.ioc.WicketInstrumentationTask"> 
   <classpath> 
@@ -124,13 +124,13 @@
 				You will also need to set the home page of the application with <literal>getHomePage()</literal>.
 			</para>
 			 
-<programlisting role="JAVA"><![CDATA[public class WicketBookingApplication extends SeamWebApplication { @Override public Class getHomePage() { return Home.class; } @Override protected Class getLoginPage() { return Home.class; } } ]]>
+<programlisting language="Java" role="JAVA">public class WicketBookingApplication extends SeamWebApplication { @Override public Class getHomePage() { return Home.class; } @Override protected Class getLoginPage() { return Home.class; } }
 </programlisting>
 			 <para>
 				Seam installs the Wicket filter automatically, but you need to tell Wicket which <literal>WebApplication</literal> class to use.
 			</para>
 			 
-<programlisting role="XML"><![CDATA[
+<programlisting language="XML" role="XML"><![CDATA[
 <components xmlns="http://jboss.com/products/seam/components" 
             xmlns:wicket="http://jboss.com/products/seam/wicket" 
             xsi:schemaLocation= 
@@ -144,7 +144,7 @@
 				If you plan to use JSF-based pages in the same application as Wicket pages, you will need to enable the JSF exception filter for JSF URLs:
 			</para>
 			 
-<programlisting role="XML"><![CDATA[
+<programlisting language="XML" role="XML"><![CDATA[
 <components xmlns="http://jboss.com/products/seam/components" 
             xmlns:web="http://jboss.com/products/seam/web" 
             xmlns:wicket="http://jboss.com/products/seam/wicket"