[
https://issues.apache.org/jira/browse/CXF-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858710#comment-13858710
]
Sergey Beryozkin commented on CXF-5477:
---------------------------------------
Hi Andriy
Thanks for getting this done. IMHO the patch is good as it is now given that we
are really talking about making it simpler for JAX-RS (and possibly JAX-WS)
users to simplify the way they set up the endpoints in cases where only basic
service and/or provider beans are used (our main use case) or when many schema
resources (I can't think of other types right now) have to be listed - and as
such I don't mind against the hack there :-). I also don't mind making Extcos
related ClasspathScanner methods synchronized;
I think it is great that we will be able to say that Blueprint (Aries)
endpoints depending on CXF namespace handlers or plain Jetty-based endpoints
can optionally avail of this feature;
I could've asked you to investigate Reflections and other libraries but I think
it won't be fair to get you spending so much time on this issue, if you feel
like it then please try other options, but as far as I'm concerned I'm happy
with what we already have :-),
I'll wait for some more possible feedback and work on applying your patch
starting from mid January, as I'm on holidays the 2nd week of January.
Thanks, Sergey
> Optional support for non-Spring based auto-discovery
> -----------------------------------------------------
>
> Key: CXF-5477
> URL: https://issues.apache.org/jira/browse/CXF-5477
> Project: CXF
> Issue Type: Improvement
> Components: Core
> Reporter: Andriy Redko
> Priority: Minor
> Fix For: 3.0.0-milestone2
>
> Attachments: patch-extcos-discovery.txt
>
>
> It would be nice to have an alternative classpath auto-discovery
> implementation(s), not based on the ones from Spring framework.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
