[
https://issues.apache.org/jira/browse/GERONIMO-4500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved GERONIMO-4500.
-----------------------------------
Resolution: Won't Fix
Assignee: Jarek Gawor
As Dan mentioned the catalog 1.1 dtd is not published at the OASIS web site.
There are a few easy work-arounds, 1) remove the DOCTYPE entry from the catalog
file or 2) change the url to point to some location that does have the 1.1 dtd,
or 3) change the url to point to the 1.0 dtd at the OASIS web site.
> Jetty/CXF fails to parse jax-ws-catalog.xml including a DOCTYPE declaration
> ---------------------------------------------------------------------------
>
> Key: GERONIMO-4500
> URL: https://issues.apache.org/jira/browse/GERONIMO-4500
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: webservices
> Affects Versions: 2.2
> Environment: Geronimo 2.2-SNAPSHOT, Jetty/CXF assembly
> Reporter: Janko Heilgeist
> Assignee: Jarek Gawor
> Attachments: geronimo-wsdllocation-jetty_cxf-1.0-SNAPSHOT.jar,
> geronimo-wsdllocation-jetty_cxf.tar.gz
>
>
> I've built an EJB-JAR packaging a web service. The JAR contains all classes,
> SEI and service stub generated from an existing WSDL (which is also inside
> this JAR). Additionally, it contains the actual EJB implementing the web
> service.
> I tried to annotate the web service implementation with
> {code:java}
> @WebService( ..., wsdlLocation="http://example.com/myservice.wsdl";)
> {code}
> and add a META-INF/jax-ws-catalog.xml:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE catalog PUBLIC "-//OASIS//DTD XML Catalogs V1.1//EN"
> "http://www.oasis-open.org/committees/entity/release/1.1/catalog.dtd";>
> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
> <system
> systemId="http://example.com/myservice.wsdl";
> uri="wsdl/myservice.wsdl"/>
> </catalog>
> {code}
> During deployment, the following exception is thrown:
> {noformat}
> 2009-01-07 17:33:53,087 WARN [OASISCatalogManager] Error loading
> META-INF/jax-ws-catalog.xml catalog files
> java.io.FileNotFoundException:
> http://www.oasis-open.org/committees/entity/release/1.1/catalog.dtd
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
> at
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:973)
> at
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:905)
> at
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(XMLEntityManager.java:872)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerImpl.java:282)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XMLDocumentScannerImpl.java:1021)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
> at
> org.apache.xml.resolver.readers.SAXCatalogReader.readCatalog(SAXCatalogReader.java:251)
> at org.apache.xml.resolver.Catalog.parseCatalog(Catalog.java:681)
> at
> org.apache.cxf.catalog.OASISCatalogManager.loadCatalogs(OASISCatalogManager.java:108)
> at
> org.apache.cxf.catalog.OASISCatalogManager.loadContextCatalogs(OASISCatalogManager.java:93)
> at
> org.apache.cxf.catalog.OASISCatalogManager.loadContextCatalogs(OASISCatalogManager.java:89)
> at
> org.apache.cxf.catalog.OASISCatalogManager.register(OASISCatalogManager.java:81)
> ...
> {noformat}
> As a workaround the DOCTYPE declaration can be removed. Without the
> declaration the exception is gone and the wsdlLocation URL is correctly
> resolved.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
