You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Tim Drury (JIRA)" <ji...@apache.org> on 2007/07/10 20:06:05 UTC
[jira] Created: (CXF-775) CXF tools don't appear to handle XML
catalogs; runtime handling is limited
CXF tools don't appear to handle XML catalogs; runtime handling is limited
--------------------------------------------------------------------------
Key: CXF-775
URL: https://issues.apache.org/jira/browse/CXF-775
Project: CXF
Issue Type: Bug
Components: Bus, Configuration, JAX-WS Runtime, Tooling
Affects Versions: 2.0
Reporter: Tim Drury
We have our own XML catalog conforming to the OASIS spec (http://www.oasis-open.org/committees/entity/spec-2001-08-06.html). We could potentially have a chain of them.
How do we get the CXF tools to use these catalogs when parsing our WSDL and/or reading schemas? I asked on irc.codehaus.org #cxf channel and was given the suggestion to file this issue here with the suggestion to provide a "-catalog <catalog_file>" to all the tools that need to read WSDL/schemas.
The CXF runtime apparently handles them but only if they are located in META-INF and named jax-ws-catalog.xml which is a bit limiting. Can we get a property added to whatever CXF uses for runtime configuration to allow specifying our own catalog names?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-775) CXF tools don't appear to handle XML
catalogs; runtime handling is limited
Posted by "Bozhong Lin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bozhong Lin reassigned CXF-775:
-------------------------------
Assignee: maomaode
James, can you confirm this fix and close the issue if so?
> CXF tools don't appear to handle XML catalogs; runtime handling is limited
> --------------------------------------------------------------------------
>
> Key: CXF-775
> URL: https://issues.apache.org/jira/browse/CXF-775
> Project: CXF
> Issue Type: Bug
> Components: Bus, Configuration, JAX-WS Runtime, Tooling
> Affects Versions: 2.0
> Reporter: Tim Drury
> Assignee: maomaode
>
> We have our own XML catalog conforming to the OASIS spec (http://www.oasis-open.org/committees/entity/spec-2001-08-06.html). We could potentially have a chain of them.
> How do we get the CXF tools to use these catalogs when parsing our WSDL and/or reading schemas? I asked on irc.codehaus.org #cxf channel and was given the suggestion to file this issue here with the suggestion to provide a "-catalog <catalog_file>" to all the tools that need to read WSDL/schemas.
> The CXF runtime apparently handles them but only if they are located in META-INF and named jax-ws-catalog.xml which is a bit limiting. Can we get a property added to whatever CXF uses for runtime configuration to allow specifying our own catalog names?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-775) CXF tools don't appear to handle XML
catalogs; runtime handling is limited
Posted by "Jeff Yu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515725 ]
Jeff Yu commented on CXF-775:
-----------------------------
I believe this issue was fixed by James Mao with: http://svn.apache.org/viewvc?view=rev&rev=555204
> CXF tools don't appear to handle XML catalogs; runtime handling is limited
> --------------------------------------------------------------------------
>
> Key: CXF-775
> URL: https://issues.apache.org/jira/browse/CXF-775
> Project: CXF
> Issue Type: Bug
> Components: Bus, Configuration, JAX-WS Runtime, Tooling
> Affects Versions: 2.0
> Reporter: Tim Drury
>
> We have our own XML catalog conforming to the OASIS spec (http://www.oasis-open.org/committees/entity/spec-2001-08-06.html). We could potentially have a chain of them.
> How do we get the CXF tools to use these catalogs when parsing our WSDL and/or reading schemas? I asked on irc.codehaus.org #cxf channel and was given the suggestion to file this issue here with the suggestion to provide a "-catalog <catalog_file>" to all the tools that need to read WSDL/schemas.
> The CXF runtime apparently handles them but only if they are located in META-INF and named jax-ws-catalog.xml which is a bit limiting. Can we get a property added to whatever CXF uses for runtime configuration to allow specifying our own catalog names?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-775) CXF tools don't appear to handle XML
catalogs; runtime handling is limited
Posted by "maomaode (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
maomaode resolved CXF-775.
--------------------------
Resolution: Fixed
As jeff said, this has been fixed
> CXF tools don't appear to handle XML catalogs; runtime handling is limited
> --------------------------------------------------------------------------
>
> Key: CXF-775
> URL: https://issues.apache.org/jira/browse/CXF-775
> Project: CXF
> Issue Type: Bug
> Components: Bus, Configuration, JAX-WS Runtime, Tooling
> Affects Versions: 2.0
> Reporter: Tim Drury
> Assignee: maomaode
>
> We have our own XML catalog conforming to the OASIS spec (http://www.oasis-open.org/committees/entity/spec-2001-08-06.html). We could potentially have a chain of them.
> How do we get the CXF tools to use these catalogs when parsing our WSDL and/or reading schemas? I asked on irc.codehaus.org #cxf channel and was given the suggestion to file this issue here with the suggestion to provide a "-catalog <catalog_file>" to all the tools that need to read WSDL/schemas.
> The CXF runtime apparently handles them but only if they are located in META-INF and named jax-ws-catalog.xml which is a bit limiting. Can we get a property added to whatever CXF uses for runtime configuration to allow specifying our own catalog names?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.