cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CXF-6768) WS-Discovery missing schema when internet connection not present
Date Thu, 18 Feb 2016 13:23:18 GMT


ASF GitHub Bot commented on CXF-6768:

GitHub user nwbirnie opened a pull request:

    [CXF-6768] Add ws-addr schema to catalog for offline support in WS-Discovery

    This patch addresses the issue with the ws-addr schema not being available without an
internet connection.

You can merge this pull request into a Git repository by running:

    $ git pull cxf6768

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #108
commit 749cf41ce2a410526041018cbd8b485a0a488518
Author: Nick Birnie <>
Date:   2016-02-16T17:15:03Z

    [CXF-6768] Add ws-addr schema to catalog for offline support


> WS-Discovery missing schema when internet connection not present
> ----------------------------------------------------------------
>                 Key: CXF-6768
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 3.1.4
>            Reporter: Nick Birnie
> When running WS-Discovery without an internet connection, it would appear that a document
(ws-addr.xsd) referenced in the WS-D schema is not available.
> The WS-Discovery service is published based on a schema that is included in cxf-services-ws-discovery-api.jar
with the name wsdd-discovery-1.1-wsdl-os.xsd. This is located by
directly from the classpath. However, that schema fails to parse without an internet connection,
due to a missing miport on ws-addr.xsd, which can be found in in cxf-core.jar/schemas.wsdl.
However, I believe there's no reason to expect this to be available to the XML parser, since
it's never registered in a OASIS catalog.
> I did try compiling CXF and registering ws-addr.xsd via the META-INF/jax-ws-catalog.xml
format, but didn't get it to work.
> Can anyone confirm if this is expected behaviour or if I'm doing something wrong?

This message was sent by Atlassian JIRA

View raw message