axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Jordahl <t...@macromedia.com>
Subject RE: cvs commit: xml-axis/java/test/wsdl Wsdl2javaTestSuite.xml
Date Thu, 06 Dec 2001 20:47:15 GMT

I guess I would prefer to change the test to not include Java keywords
rather than take the whole thing out.  But failing that, the simplest thing
to do is to turn off the 'testcase' switch, so no client/server testing gets
done.  The important thing for this test is to verify that the code
generated from the WSDL will compile correctly (i.e. No bad Java things in
it) rather than to test round trip stuff.

I will make this change.

P.S.
Why did this test pass for me when I ran the tests before submitting?

--
Tom Jordahl


-----Original Message-----
From: butek@apache.org [mailto:butek@apache.org]
Sent: Thursday, December 06, 2001 3:09 PM
To: xml-axis-cvs@apache.org
Subject: cvs commit: xml-axis/java/test/wsdl Wsdl2javaTestSuite.xml


butek       01/12/06 12:08:40

  Modified:    java/test/wsdl Wsdl2javaTestSuite.xml
  Log:
  JavaNames breaks the build.
  
  Revision  Changes    Path
  1.37      +17 -0     xml-axis/java/test/wsdl/Wsdl2javaTestSuite.xml
  
  Index: Wsdl2javaTestSuite.xml
  ===================================================================
  RCS file: /home/cvs/xml-axis/java/test/wsdl/Wsdl2javaTestSuite.xml,v
  retrieving revision 1.36
  retrieving revision 1.37
  diff -u -r1.36 -r1.37
  --- Wsdl2javaTestSuite.xml	2001/12/06 18:03:08	1.36
  +++ Wsdl2javaTestSuite.xml	2001/12/06 20:08:40	1.37
  @@ -323,6 +323,22 @@
       </wsdl2java>
       
       <!-- Check to make sure we map XML names that are illegal Java
correctly -->
  +
  +    <!-- We have a problem.  The functional-tests fail.  This test
contains  -->
  +    <!-- operations "new" and "public".  These are Java keywords so the
-->
  +    <!-- method names become "_new" and "_public".  But "new"/"public"
are   -->
  +    <!-- sent over the wire and "new"/"public" are in deploy.wsdd.  When
the -->
  +    <!-- server-side is handed these we get a method not found error.  We
-->
  +    <!-- COULD send "_new"/"_public" over the wire and put them into
-->
  +    <!-- deploy.wsdd (this DOES work) but that's BAD.  If the server is
-->
  +    <!-- written in a language that doesn't have the keywords "new" and
-->
  +    <!-- "public", then it would not have prepended underscores onto its
-->
  +    <!-- method names.
-->
  +    <!--
-->
  +    <!-- What we need is some sort of method mapping, probably in
-->
  +    <!-- deploy.wsdd, that the server-side runtime can use.
-->
  +
  +    <!--
       <wsdl2java url="test/wsdl/names/JavaNames.wsdl"
                  output="build/work"
                  deployscope="none"
  @@ -332,6 +348,7 @@
                  testcase="yes">
           <mapping namespace="http://test.com/reference"
package="test.filegen"/>
       </wsdl2java>
  +    -->
   
       <!--
       <wsdl2java
url="http://www.lemurlabs.com/projects/soap/fortune/FortuneService.wsdl"
  
  
  

Mime
View raw message