cocoon 3.0.0-beta-1-SNAPSHOT in wicket 6.9.0

I tried to integrate cocoon 3.0.0-beta-1-SNAPSHOT
in wicket  6.9.0
as I have done it in wicket 6.3.0-beta-1-SNAPSHOT and cocoon 3.0.0-alpha-3
But my proprietary Mapper-adaption doesn't work.
I try now to use the original Mapper bat no success.
Is my configuration ok?
<?xml version="1.0" encoding="UTF-8"?>
<beans
xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:context="http://www.springframework.org/schema/context"
xmlns:configurator="http://cocoon.apache.org/schema/configurator"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context.xsd
http://cocoon.apache.org/schema/configurator 
http://cocoon.apache.org/schema/configurator/cocoon-configurator-1.0.1.xsd"
        default-lazy-init="true">
<!--xmlns:configurator="http://cocoon.apache.org/schema/configurator"-->
<!-- 
http://cocoon.apache.org/schema/configurator/cocoon-configurator-1.0.1.xsd-->
     <!-- Activates scanning of @Autowired -->
     <context:annotation-config/>

     <!-- Activates scanning of @Repository and @Service -->
     <context:component-scan base-package="braunimmobilien"/>

     <!-- Add new DAOs here -->

     <!-- Add new Managers here -->


  <!-- Add Cocoon here -->

<configurator:settings/>
  <import 
resource="classpath:META-INF/cocoon/spring-optional/cocoon-optional-fop.xml" 
/>
  <import 
resource="classpath:META-INF/cocoon/spring-optional/cocoon-optional-serializers.xml" 
/>
<!-- <bean name="transformer:sql" 
class="braunimmobilien.cocoon.sax.component.SQLTransformer" 
scope="prototype" />-->
</beans>

and do I use the right mapper

package org.apache.wicket.examples.cocoonobjectapproach.common.web;
//import braunimmobilien.cocoon.wicket.mapper.CocoonSitemapMapper;
import org.apache.cocoon.wicket.request.CocoonSitemapRequestMapper;
import org.apache.wicket.Page;
import org.apache.wicket.examples.WicketExampleApplication;

/**
  * Application class for the dates example.
  */
public class CocoonObjectApproachApplication extends 
WicketExampleApplication
{
     /**
      * Constructor.
      */
     public CocoonObjectApproachApplication()
     {
     }
@Override
     public void init()
     {
         super.init();
      this.mount(new CocoonSitemapRequestMapper("/sitemap", 
"/sitemap.xmap.xml"));
     }
     /**
      * @see org.apache.wicket.Application#getHomePage()
      */
     @Override
     public Class< ? extends Page> getHomePage()
     {
         return CocoonObjectApproachPage.class;
     }
}


Am 04.07.2013 18:13, schrieb Thorsten Scherler:
> On 07/04/2013 05:47 PM, Piratenvisier wrote:
>> Because I wanted to reduce my software engagement I didn't look in the
>> source trunk.
>> I only used the official maven archetypes.
>> I checked the source trunk out.
>> I will evaluate its state.
> It is much better then the alpha and we are close to release. I highly
> recommend it over the alpha.
>
> However I meant the pom.xml the archetypes creates on your project, the
> one that declared the dependencies.
>
> salu2
>