A Seam enabled Wicket application has full access to the all the standard Seam contexts ( EVENT , CONVERSATION , SESSION , APPLICATION and BUSINESS_PROCESS ).

To access Seam component's from Wicket, you just need to inject it using @In :

@In(create=true)

private HotelBooking hotelBooking;

You can also outject an object into the Seam contexts from a Wicket component:

@Out(scope=ScopeType.EVENT, required=false)

private String verify;

TODO Make this more use case driven

You can secure a Wicket component by using the @Restrict annotation. This can be placed on the outer component or any inner components. If @Restrict is specified, the component will automatically be restricted to logged in users. You can optionally use an EL expression in the value attribute to specify a restriction to be applied. For more refer to the Chapter 16, Security .

For example:

@Restrict

public class Main extends WebPage

{

   ...

You can demarcate conversations from within a Wicket component through the use of @Begin and @End . The semantics for these annotations are the same as when used in a Seam component. You can place @Begin and @End on any method.

For example:

item.add(new Link("viewHotel") {


   @Override

   @Begin

   public void onClick() {

      hotelBooking.selectHotel(hotel);

      setResponsePage(org.jboss.seam.example.wicket.Hotel.class);

   }

};

You may have pages in your application which can only be accessed when the user has a long-running conversation active. To enforce this you can use the @NoConversationPage annotation:

@Restrict

@NoConversationPage(Main.class)

public class Hotel extends WebPage 

{

If you want to further decouple your application classes, you can use Seam events. Of course, you can raise an event using Events.instance().raiseEvent("foo") . Alternatively, you can annotate a method @RaiseEvent("foo") ; if the method returns a non-null outcome without exception, the event will be raised.

You can also control tasks and processes in Wicket classes through the use of @CreateProcess , @ResumeTask , @BeginTask , @EndTask , @StartTask and @Transition .

There are two ways to achieve runtime instrumentation. One relies on placing wicket components to be instrumented in a special folder in your WAR deployment. If this is not acceptable or possible, you can also use an instrumentation "agent," which you specify in the command line for launching your container.

Seam supports instrumentation at compile time through either Apache Ant or Apache Maven.

<taskdef name="instrumentWicket"
   classname="org.jboss.seam.wicket.ioc.WicketInstrumentationTask">
  <classpath>
    <pathelement location="lib/jboss-seam-wicket-ant.jar"/>
    <pathelement location="web/WEB-INF/lib/jboss-seam-wicket.jar"/>
    <pathelement location="lib/javassist.jar"/>
    <pathelement location="lib/jboss-seam.jar"/>
  </classpath>
</taskdef>

<instrumentWicket outputDirectory="${build.instrumented}" useAnnotations="true">
  <classpath refid="build.classpath"/>
  <fileset dir="${build.classes}" includes="**/*.class"/>
</instrumentWicket>

<build>
    <plugins>
         <plugin>
            <groupId>org.jboss.seam</groupId>
            <artifactId>seam-instrument-wicket</artifactId>
            <version>2.2.0</version>
            <configuration>
                <scanAnnotations>true</scanAnnotations>
                <includes>
                    <include>your.package.name</include>
                </includes>
            </configuration>
            <executions>
                <execution>
                    <id>instrument</id>
                    <phase>process-classes</phase>
                    <goals>
                        <goal>instrument</goal>
                    </goals>
                </execution>
            </executions>
        </plugin>
    </plugins>
</build>

Classes placed in WEB-INF/wicket will unconditionally be instrumented. The other instrumentation mechanisms all allow you to specify that instrumentation should only be applied to classes annotated with the @SeamWicketComponent annotation. This annotation is inherited, which means all subclasses of an annotated class will also be instrumented. An example usage is:

import org.jboss.seam.wicket.ioc.SeamWicketComponent;

@SeamWicketComponent
public class MyPage extends WebPage
{
 ...
}

A Wicket web application which uses Seam should use SeamWebApplication as the base class; this creates hooks into the Wicket lifecycle allowing Seam to automagically propagate the conversation as needed. It also adds status messages to the page.

For example:

The SeamAuthorizationStrategy delegates authorization to Seam Security, allowing the use of @Restrict on Wicket components. SeamWebApplication installs the authorization strategy for you. You can specify the login page by implementing the getLoginPage() method.

You'll also need to set the home page of the application by implementing the getHomePage() method.

public class WicketBookingApplication extends SeamWebApplication

{


   @Override

   public Class getHomePage() 

   {

      return Home.class;

   }


   @Override

   protected Class getLoginPage() 

   {

      return Home.class;

   }

}

Seam automatically installs the Wicket filter for you (ensuring that it is inserted in the correct place for you). But you still need to tell Wicket which WebApplication class to use.

<components xmlns="http://jboss.org/schema/seam/components"

 xmlns:wicket="http://jboss.org/schema/seam/wicket"

 xsi:schemaLocation=

  "http://jboss.org/schema/seam/wicket

   http://jboss.org/schema/seam/wicket-2.3.xsd">

   

  <wicket:web-application 

    application-class="org.jboss.seam.example.wicket.WicketBookingApplication" />

</components

In addition, if you plan to use JSF-based pages in the same application as wicket pages, you'll need to ensure that the jsf exception filter is only enabled for jsf urls:

<components xmlns="http://jboss.org/schema/seam/components"

 xmlns:web="http://jboss.org/schema/seam/web"

 xmlns:wicket="http://jboss.org/schema/seam/wicket"

 xsi:schemaLocation=

  "http://jboss.org/schema/seam/web

   http://jboss.org/schema/seam/web-2.3.xsd">

     

    <!-- Only map the seam jsf exception filter to jsf paths, which we identify with the *.seam path -->

    <web:exception-filter url-pattern="*.seam"/>

</components