[
https://issues.apache.org/jira/browse/CXF-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-5681.
------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
2.7.12
2.6.15
Assignee: Daniel Kulp
Added a warning log entry IF there is no CatalogManager and there are catalog
entries found. If there aren't any catalogs found on the classloader, we
don't worry about it.
> OASISCatalogManager silently swallows Exceptions in getResolver()
> -----------------------------------------------------------------
>
> Key: CXF-5681
> URL: https://issues.apache.org/jira/browse/CXF-5681
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 3.0.0
> Reporter: John O'Hara
> Assignee: Daniel Kulp
> Fix For: 2.6.15, 2.7.12, 3.0.0
>
>
> org.apache.cxf.catalog.OASISCatalogManager.getResolver() silently fails if
> any exceptions are thrown during the try{} block.
> https://github.com/apache/cxf/blob/master/core/src/main/java/org/apache/cxf/catalog/OASISCatalogManager.java#LC107
> This makes resolving issues difficult as Exceptions that contain important
> information are ignored.
> For example, if org.apache.xml.resolver.CatalogManager is not found on the
> classpath (as it is in an external library), a CNFE exception is swallowed
> and calls to loadCatalogs() will fail to load catalogs bundled with an
> application. As no errors/warnings are logged, it appears that the
> jax-ws-catalog.xml has been loaded correctly.
> IMHO, since there is already a logger defined in the OASISCatalogManager
> class, there should be at least an WARN message logged for exceptions within
> the try{} block to help resolve issues like CNFE exceptions.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
