*sigh*... ignore the idiot in the corner. It *was* adding my handler
before this one... I just didn't realize there was another handler I
needed mine to be *after*. One extra constraint later, and all is
good. :-\
-will
On Feb 6, 2008, at 10:10 PM, Will Norris wrote:
I'm running into a problem where I am unable to properly order
contributions based on the order in which two modules are loaded. I
am using Robin Helgelin's Tapestry5-Acegi along with my own module
Tapesty-Shib which adds my own HttpServletRequestHandler. In my
module, I have the following...
public void
contributeHttpServletRequestHandler
(OrderedConfiguration<HttpServletRequestFilter> configuration,
@InjectService("ShibbolethProcessingFilter")
HttpServletRequestFilter shibbolethFilter) {
configuration.add("ShibbolethProcessingFilter", shibbolethFilter,
"before:acegiAnonymousProcessingFilter");
}
My handler never seems to be added before
"acegiAnonymousProcessingFilter". If I add the same method
(changing the configuration ID slightly), it works just fine. I've
kicked logging up to TRACE and verified that my module is indeed
being loaded before Tapestry5-Acegi. My understanding of
OrderedConfiguration is that this shouldn't matter... it should
respect constraints regardless of when contributions are loaded. Is
that right?
This is all with Tapestry 5.0.9. Thanks for any assistance.
-will norris
---------------------------------------------------------------------
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]
