cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CXF-440) OASIS catalog support
Date Wed, 28 Feb 2007 18:30:57 GMT

     [ https://issues.apache.org/jira/browse/CXF-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jarek Gawor updated CXF-440:
----------------------------

    Attachment: CXF-440.patch

> OASIS catalog support
> ---------------------
>
>                 Key: CXF-440
>                 URL: https://issues.apache.org/jira/browse/CXF-440
>             Project: CXF
>          Issue Type: New Feature
>          Components: JAX-WS Runtime
>            Reporter: Jarek Gawor
>         Attachments: CXF-440.patch
>
>
> The attached patch contains basic support for OASIS catalog resolution for WSDL and XSD
files as required by the JAX-WS spec. 
> The catalog resolution is done using the Apache Commons Resolver API. Special WSDLLocator
and XmlSchemaURIResolver implementations are provided to perform catalog-based resolution.
Also,  WSDLManagerImpl and WSDLServiceBuilder are updated to use the new resolvers. Various
test cases are also included. 
> By default, (as defined by the spec) the code loads all META-INF/jax-ws-catalog.xml catalogs
from the context classloader. The user can overwrite this default behavior by passing a Catalog
instance on the bus (as an extension). If there is a better way to pass custom Catalog instances
around please let me know.
> Also, there is one critical fix to common/common/src/main/java/org/apache/cxf/resource/URIResolver.java
class. The member variables must be reset after each resolve() call. Otherwise, if current
resolution fails, the previously resolved InputSource will be returned.
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message