beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Tam (JIRA)" <>
Subject [jira] Commented: (BEEHIVE-1159) Create more robust way to order (prioritize) interceptor behavior
Date Tue, 27 Mar 2007 00:55:32 GMT


Kenneth Tam commented on BEEHIVE-1159:

Note that if an end user is using interceptors from different providers, it's likely that
the appropriate ordering between those interceptors can't be known a priori by any given provider,
and hence the easiest answer is to leave the ordering up to the end user.  I.e:  given interceptors
A & B packaged by Provider 1, and interceptors C & D packaged by Provider 2, the user
needs to provide a controls-interceptors.config in front of both those packages that specifies
how A & B are ordered wrt C & D.  That said, right now that user also needs to manually
replicate the prioritization provided for A wrt B and C wrt D, so +1 on reading multiple config
files and merging/resolving the priority rules together.  Anyone running into this in practice?

> Create more robust way to order (prioritize) interceptor behavior
> -----------------------------------------------------------------
>                 Key: BEEHIVE-1159
>                 URL:
>             Project: Beehive
>          Issue Type: Improvement
>          Components: Controls
>            Reporter: Andrew McCulloch
> Currently to prioritize which interceptors fire first a single file controls-interceptors.config
is used to order the interceptor classes.  This approach works for most cases.  However, If
I write 3 interceptors and package them in interceptor1.jar with a controls-interceptor.config
file and have 3 different interceptors and config file in interceptor2.jar then only the interceptors
that appear first on the classpath will maintain thier ordering as only 1 config file is resource

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message