Re: T4 - access hivemind registry from another servlet

2007-11-15 Thread Renat Zubairov
Another way to extend Application servlet from tapestry and with your implementation and then just replace ApplicationServlet declaration inside web.xml with your new class. Logic is more or less the same. On 15/11/2007, Jili Lv [EMAIL PROTECTED] wrote: 1. Add a filter class : package

Re: T4 - access hivemind registry from another servlet

2007-11-15 Thread Paul Stanton
ok thankyou, i've extended the servlet. Renat Zubairov wrote: Another way to extend Application servlet from tapestry and with your implementation and then just replace ApplicationServlet declaration inside web.xml with your new class. Logic is more or less the same. On 15/11/2007, Jili Lv

T4 - access hivemind registry from another servlet

2007-11-14 Thread Paul Stanton
Ok, so the tapestry servlet initializes and stores the hivemind registry for use within tapestry. My hivemind services and tapestry components and pages can find each other via injection or context method calls. That's fine, but now I've got separate servlet in which I need to have access to

Re: T4 - access hivemind registry from another servlet

2007-11-14 Thread Jili Lv
1. Add a filter class : package com.example; import java.io.IOException; import javax.servlet.Filter; import javax.servlet.FilterChain; import javax.servlet.FilterConfig; import javax.servlet.ServletException; import javax.servlet.ServletRequest; import javax.servlet.ServletResponse; import