Hello,

I have recently begun using the Tapestry 5 framework a few months ago and
have been very satisfied with it (actually am very impressed with it).

I am working with another open source project called Sakai which is an LMS
for Higher Ed. which uses a conglomeration of Java web frameworks like:

Velocity
JSF
Wicket
JSP

I would like to add Tapestry to the list.

Sakai has a filter (sakai.request) that wraps access to all its tools and is
responsible for maintaining session, it is configured in the following way:

Sakai RequestFilter:
       <filter>
               <filter-name>sakai.request</filter-name>

 <filter-class>org.sakaiproject.util.RequestFilter</filter-class>
       </filter>
       <filter-mapping>
               <filter-name>sakai.request</filter-name>
               <servlet-name>sakai.profile2</servlet-name>
               <dispatcher>REQUEST</dispatcher>
               <dispatcher>FORWARD</dispatcher>
               <dispatcher>INCLUDE</dispatcher>
       </filter-mapping>

Here is a Sample Sakai tool that uses wicket with Spring integration:
     <servlet>
            <servlet-name>sakai.profile2</servlet-name>

<servlet-class>org.apache.wicket.protocol.http.WicketServlet</servlet-class>

            <init-param>
                <param-name>applicationFactoryClassName</param-name>

<param-value>org.apache.wicket.spring.SpringWebApplicationFactory</param-value>
            </init-param>
            <init-param>
                        <param-name>applicationBean</param-name>
                        <param-value>profileApplication</param-value>
                </init-param>
        </servlet>

       <servlet-mapping>
                <servlet-name>sakai.profile2</servlet-name>
                <url-pattern>/sakai-profile2/*</url-pattern>
        </servlet-mapping>

The problem is that sakai expects to work with a servlet and tries to access
a RequestDispatcher from the servlet context and then forwards the call to
the right tool.

Does tapestry uses a web filter instead of a servlet?
If so it looks like support may have to be added to handle tool registration
for those of a type filter.

Comments are most welcome.

Earle

Reply via email to