Date: 2004-04-18T11:21:29
Editor: HowardLewisShip <[EMAIL PROTECTED]>
Wiki: Jakarta HiveMind Wiki
Page: InterceptorOrderingProposal
URL: http://wiki.apache.org/jakarta-hivemind/InterceptorOrderingProposal
no comment
Change Log:
------------------------------------------------------------------------------
@@ -61,3 +61,13 @@
}}}
So, each interceptor has a {{{name}}} attribute (which is presumably unique),
and can specify which interceptors come before them (equivalent to lower order
numbers in the current system), and which come after (equivalent to higher
order numbers). In some cases, an interceptor may need to specify both
{{{before}}} and {{{after}}}. In some cases, a comma-seperated list is
appropriate. As in the example above, the occasional use of a wildcard is
appropriate.
+
+= Status =
+
+As of April 18 2004, Ordering Via Dependencies has been largely implemented.
The only piece was to add a {{{name}}} attribute to <interceptor>; currently,
the ordering is done using service-id. I think this is acceptible for the
meantime ... I think it will be rare to have more than two or
+three interceptors on a given service, and the ordering should generally be
straight forward.
+
+attachment:interceptor-dependencies.png
+
+Along the way, I changed some of the logging concerned with service creation
to use the logger for the service id. This seems like a good idea (enable
logging for com.myco.MyService and you will get logging of its creation as well
method invocations), and I expect to pursue this further.
+
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
