mede
mede

Reputation: 81

wsimport don't generate client classes with geotoolkit

if I build a jax-ws web service including objects coming from geotoolkit library, when I run the wsimport tool to generate the client, I get this errors: [wsimport] [ERROR] undefined simple type 'actuate'

[wsimport] line 5 of http://localhost:8080/jaxws/myservice?xsd=1

[wsimport] [ERROR] undefined simple type 'show'

[wsimport] line 13 of http://localhost:8080/jaxws-myapp/myservice?xsd=1

[wsimport] [ERROR] undefined simple type 'type'

[wsimport] line 17 of http://localhost:8080/jaxws-myapp/myservice?xsd=1.

any workaround? I can't find a proper way to tell wsimport to read the xsd definition from a different url than the on-line one (the problem is that some namespaces specified by the wsdl refer to urls not available)

Upvotes: 0

Views: 637

Answers (1)

mede
mede

Reputation: 81

At the end I found how to write an OASIS XML catalog file to workaround the problem:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
 "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
 <system systemId="http://localhost:8080/jaxws-myapp/myservice?xsd=1" uri="file:///c:/myxsd"/>
</catalog>

This way wsimport overrides the in-line xsd with the local one, where i simplified the types (originally they were enumeration) to xs:string

Upvotes: 0

Related Questions