Hi All,
We've been experimenting recently with registering custom namespace
handlers manually in a non-OSGI environment, with blueprint-web and
blueprint-noosgi components.
It works quite well but as soon as it started working it became obvious
it can be tricky for users to do the manual registration, and it would
be good to have some basic automation support around it.
At the moment Aries NamespaceHandler does have a way to tell what
namespaces it supports. I opened [1] to have a new annotation added for
namespace handler implementations optionally advertise the supported
namespaces.
I've updated a Blueprint Web listener locally that checks a context
property listing the required handler classes only, and the CXF test
that depends on the local updated snapshot is now looking very neat.
The other possible enhancement going forward, once Namespaces is in
blueprint-parsers, would be to ship an optional ServletContainerInitializer.
But the 1st step is to get the annotation shipped. Hope the above and
the comments at [1] makes sense
Thanks, Sergey
[1] https://issues.apache.org/jira/browse/ARIES-1322
