[
https://issues.apache.org/jira/browse/CXF-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko updated CXF-5477:
------------------------------
Attachment: patch-extcos-discovery.txt
Hi Sergey,
Please provide your feedback on a classpath scanner implementation based on
Extcos (version 0.4b). As per our previous discussions, the "scan all packages"
feature is not supported yet (due to the library package-oriented design).
The resource scanning, by and large, is possible but looks not very good (read
- 'ugly') due to the library design: it uses some internal details of Extcos
implementation and relies on toString() method to get resource URL. It also
revealed that Extcos is not thread-safe and cannot be used reliably by more
than one thread (it uses global singleton objects to pass the classloaders etc.
through the callers).
Anyway, please don't hesitate to make "no go" decision for extcos, it might not
be mature enough at the moment but it looks promising. :-)
Thanks.
Andriy
> 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)
