Skip to content
This repository has been archived by the owner on Jan 30, 2019. It is now read-only.

wsdl import incorrectly not changing namespace #1659

Open
glassfishrobot opened this issue Nov 12, 2012 · 3 comments
Open

wsdl import incorrectly not changing namespace #1659

glassfishrobot opened this issue Nov 12, 2012 · 3 comments

Comments

@glassfishrobot
Copy link
Contributor

Hi, for the following wsit-client.xml file here:
https://github.com/gmazza/blog-samples/blob/master/metro_sts_tutorial/client/src/main/resources/wsit-client.xml

The namespace attributes are (as far as I can tell) incorrectly not overwriting the namespaces declared within the original file, i.e., regardless of what I place there the client will run successfully so long as the target namespaces within the two imported files are correct. For example, the "http://tempuri.org/" reassignment of the namespace for the STS config file in wsit-client.xml should cause the client to fail to work, but it works fine.

OTOH, if I change the targetNamespace attribute directly in either or both of the imported .xml files: https://github.com/gmazza/blog-samples/tree/master/metro_sts_tutorial/client/src/main/resources, the client will correctly fail to run.

To test:

1.) Check out the blog-samples at https://github.com/gmazza/blog-samples/downloads and run mvn clean install from the root folder (necessary to install the parent-level pom file in your local repo).
2.) (Optional) Configure your Tomcat installation to be able to handle the Tomcat maven plugin (i.e., so mvn tomcat:redeploy works) as described here:
http://www.jroller.com/gmazza/entry/web_service_tutorial#maventomcat
3.) Navigate to the metro-sts-tutorial folder and run mvn tomcat:redeploy if you did #2 above, or manually copy the WSP and STS wars to your Tomcat deploy folder if you did not. Make sure you can see the STS and WSP WSDLs at http://localhost:8080/DoubleItSTS/STS?wsdl and http://localhost:8080/doubleit/services/doubleit?wsdl before continuing.
4.) Navigate to the metro_sts_tutorial/client folder and run mvn exec:exec — you'll see the client incorrectly run successfully. Testing subsequent edits to the wsit-client.xml and imported files can be done by running "mvn clean install exec:exec" from the client folder afterwards.

Environment

Metro 2.2.1-1; JDK 7 update 9 on Ubuntu OS.

Affected Versions

[2.2.1]

@glassfishrobot
Copy link
Contributor Author

Reported by gmazza

@glassfishrobot
Copy link
Contributor Author

Was assigned to snajper

@glassfishrobot
Copy link
Contributor Author

This issue was imported from java.net JIRA WSIT-1659

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant