This change actually doesn't work.

Can someone (Rich?) who is familiar with how the WSDL
document we generate is created take a look and see why/how
we can get <types>  -->  <wsdl:types>

This was noted at the interop as 'weird', if not a bug.
All of our other definition elements are qualified with 'wsdl:'.

--
Tom Jordahl
Macromedia


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 28, 2002 1:50 PM
To: [EMAIL PROTECTED]
Subject: cvs commit: xml-axis/java/src/org/apache/axis/wsdl/fromJava
Types.java


tomj        02/02/28 10:50:13

  Modified:    java/src/org/apache/axis/wsdl/fromJava Types.java
  Log:
  Create the types element with the wsdl namespace prefix.
  
  Revision  Changes    Path
  1.18      +2 -1      xml-axis/java/src/org/apache/axis/wsdl/fromJava/Types.java
  
  Index: Types.java
  ===================================================================
  RCS file: /home/cvs/xml-axis/java/src/org/apache/axis/wsdl/fromJava/Types.java,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- Types.java        22 Feb 2002 23:11:34 -0000      1.17
  +++ Types.java        28 Feb 2002 18:50:13 -0000      1.18
  @@ -325,7 +325,8 @@
        */
       private void writeWsdlTypesElement() throws Exception {
           if (wsdlTypesElem == null) {
  -            wsdlTypesElem = docHolder.createElement("types");
  +            wsdlTypesElem = 
  +                    docHolder.createElementNS(Constants.NSPREFIX_WSDL, "types");
           }
       }
   
  
  
  

Reply via email to