[
https://issues.apache.org/jira/browse/CXF-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844165#comment-13844165
]
Sergey Beryozkin commented on CXF-5439:
---------------------------------------
Hi All,
Let me clarify my intent a bit more.
JAX-RS endpoint namespace hander can now let users do not explicitly reference
simple JAX-RS root resources and providers, this is possible thanks to Andriy's
patch where the JAX-RS Path & Provider annotations are scanned for and checked,
we haven't reinvented the wheel there, we just reused Spring class-scanning
facility to simplify JAX-RS XML endpoints when possible; I'd like the same work
for Blueprint. This is in line with the expectations which users can have met
with Jersey & RestEasy. IMHO that would be handy for JAX-WS XML declarations,
but it is a minor issue, if you think it can work for JAX-WS I can type a
JAX-WS patch easily. Now that we have a way to say
{code:xml}
<jaxrs:server address="/" base-packages="mypackage"/>
{code}
asking users to do
{code:xml}
<jaxrs:server address="/" base-packages="mypackage">
<!-- no need to type JAX-RS roots & providers, but...-->
<jaxrs:inInterceptors>
<bean class="myAuthenticatingInterceptor"/>
</jaxrs:inInterceptors>
<jaxrs:outInterceptors>
<bean class="myOutInterceptor"/>
</jaxrs:outInterceptors>
</jaxrs:server>
{code}
is not ideal.
Having a single annotation marker is a good compromise in the end IMHO, it can
'scale' to be applicable to all sort of CXF extensions; Andriy, I don't favor
the idea of introducing 5 new markers any longer, I believe this is exactly
what Dan was against too; the existing InInterceptors/etc are 'collections'
meant to be applied directly to endpoint classes/root resources, we can indeed
use some conventions there or further extend all of them, but I thought it
would be marginally cleaner to have a marker to apply to individual CXF
extensions/providers as/if needed. Scope is another issue, it is useful because
we can also have client or server-only in or out interceptors, and sometimes
users hit the issue with the interceptors intended for the server use only
picked up by clients, this is solvable with multiple bus references but a scope
can offer another solution too.
Now, I don't want to spend a lot of time on this minor issue: I can drop this
issue immediately if no interest exists to introduce a marker
Sergey
> Introduce annotations for marking CXF interceptors and features to enable the
> auto-discovery
> --------------------------------------------------------------------------------------------
>
> Key: CXF-5439
> URL: https://issues.apache.org/jira/browse/CXF-5439
> Project: CXF
> Issue Type: Improvement
> Components: Core
> Reporter: Sergey Beryozkin
> Priority: Minor
> Fix For: 3.0.0-milestone2
>
>
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
