search

javaee / metro-jaxws-commons

Metro has been contributed to Eclipse Foundation. This repository is for legacy review only. Please refer to the Eclipse EE4J Metro project for the very latest
https://eclipse-ee4j.github.io/metro-wsit/
Other
10 stars 9 forks source link

primaryWsdl does not resolve imported schemas #54

Open glassfishrobot opened 14 years ago

glassfishrobot commented 14 years ago

If you use wsdl first development, and configure as per https://jax-ws- commons.dev.java.net/spring/wsdl-first.html You can successfully have your own wsdl presented at http://server/app/services/service?wsdl

However, any schemas that the wsdl imported reference local paths, and so are unreachable by any clients. If you just let the wsdl be autogenerated, it will correctly refer to them as ?xsd=1 and ?xsd=2 and so on.

See also: http://forums1.java.net/jive/thread.jspa?threadID=29803

This happens (at least) with spring extension version 1.8 and jax-ws 2.1.7 running under tomcat6x/java6u12.

In my case at least, the wsdl and the schemas are in a jar on the classpath. The wsdl is happily found inside the jar at least.

Environment

Operating System: All Platform: All

Affected Versions

[current]

glassfishrobot commented 14 years ago

Reported by karljp@java.net

glassfishrobot commented 14 years ago

karljp@java.net said: Duplicate of #18. God the search in the issue tracker here is TERRRRIBLE.

https://jax-ws-commons.dev.java.net/issues/show_bug.cgi?id=18 if it doesn't know how to link properly.

Sorry, no permissions to resolve this in any way.

Workaround mentioned in 18 still applies.

glassfishrobot commented 14 years ago

Was assigned to kohsuke@java.net

glassfishrobot commented 7 years ago

This issue was imported from java.net JIRA JAX_WS_COMMONS-54