axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 11342] - invalid targetNamespace for dynamically generated WSDL's (targetNamespace is redundant)
Date Mon, 19 Aug 2002 23:48:15 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11342>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11342

invalid targetNamespace for dynamically generated WSDL's (targetNamespace is redundant)

tim_lewis@theprairie.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Normal                      |Major
         OS/Version|Windows NT/2K               |All
           Platform|PC                          |All
            Summary|targetNamespace for         |invalid targetNamespace for
                   |dynamically generated WSDL  |dynamically generated WSDL's
                   |is redundant                |(targetNamespace is
                   |                            |redundant)



------- Additional Comments From tim_lewis@theprairie.com  2002-08-19 23:48 -------
This bug causes invalid WSDL's to be generated.

For two good examples everyone should be able to see:
http://localhost:8080/axis/services/AdminService?WSDL
http://localhost:8080/axis/services/Version?WSDL

It was annoying to track down, but I found the offending line of code:
                      interfaceNamespace += urlURL.getFile();

which was added to /xml-
axis/java/src/org/apache/axis/providers/java/JavaProvider.java version 1.58, 
2002/06/09 02:01:10

you can view the diff here:

http://cvs.apache.org/viewcvs.cgi/xml-
axis/java/src/org/apache/axis/providers/java/JavaProvider.java.diff?
r1=1.57&r2=1.58&diff_format=h

Can that line of code be dropped entirely?

I'm guessing rineholt checked to see that it worked with the new MessageContext 
properties, but forgot to see how it affected services w/o those properties.

The reason it shows up now, is b/c targetNamespace = interfaceNamespace, if 
targetNamespace is null, which seems to be true if the service option 
OPTION_WSDL_TARGETNAMESPACE isn't set.

And for some reason the interface namespace is set using the targetNamespace. 
This doesn't make any sense to me.

...
emitter.setIntfNamespace(targetNamespace);

Mime
View raw message