Which servlet/filter handles which request is configured in web.xml.
Apparently, yours is set up in a way that a request which should go to
the WingS-Servlet is handled by the Tapestry filter, although it
shouldn't be.

Check the filter-mapping for the TapestryFilter, does it include
/application/  ? For your purpose, it shouldn't. If you can't resolve
it, you might want to post your web.xml, or the relevant sections of
it.

hth,

Lutz


On 7/3/07, Tina Umlandt <[EMAIL PROTECTED]> wrote:
Hello,

I have the following problem. I have a servlet which should be in the same 
context as the tapestry application but it is
built with a different framework named wings.

Wings is using another framework named dwr. dwr is sending request like "GET 
/application/dwr/engine.js".
Now I get the exception
"java.lang.IllegalArgumentException: Unable to resolve page 'dwr/engine' to a 
known page name. Available page names: ...
at 
org.apache.tapestry.internal.services.ComponentClassResolverImpl$8.invoke(ComponentClassResolverImpl.java:393)
        at 
org.apache.tapestry.internal.services.ComponentClassResolverImpl$8.invoke(ComponentClassResolverImpl.java:388)
        at 
org.apache.tapestry.ioc.internal.util.ConcurrentBarrier.withRead(ConcurrentBarrier.java:77)
        at
org.apache.tapestry.internal.services.ComponentClassResolverImpl.canonicalizePageName(ComponentClassResolverImpl.java:386)
..."

Is there a way to tell tapestry several request about which it should not care 
and just ignore?

Thx,
        Tina


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to