Okay, that's interesting, if I understand what you intend. Is the
idea that you install a feature on an endpoint (where the feature is
manifest as a bean), and under the covers, the feature assembles all
the pieces, in the correct order, etc? That's basically what I'm
after, but I need access to the endpoint, so that I can install
interceptors on that specific level of granularity. (Again, sort of
fumbling around in the dark here, as I am not omniscient vis a vis
CXF internals.)
I'm not sure how the XML config you posted in the email I'm
responding to is relevant, since I'm not trying to statically
configure an interceptor -- I want all that to be done under the
hood, by my FooFeature bean.
Thanks!
-Fred
On Mar 21, 2007, at 3:12 PM, Dan Diephouse wrote:
Also, I recently added an AbstractWSFeature class which I'd like to
support
the loading of a plugin for a particular scenario. The idea being
that you
can have a feature class - like a WSSecurityFeature - which
configures your
endpoint for something - like WS-Security. And it can just become
part of
the JAX-WS endpoint configuration. I posted some examples of how
this might
work in the client/EPR thread if you're interested. I'll be
answering some
of the questions that arose on that shortly...
