Dan,

The attached patch makes the error go away, though I can't guarantee it's still a valid test of whatever the test was supposed to test :)

Jim

On 17/12/2010 20:08, Jim Talbut wrote:
 Dan,

This particular fault isn't caused by a space in the build path ("C:\Work\cxf").

Jim

On 17/12/2010 14:46, Daniel Kulp wrote:
I actually  did start adding a Windows job to Hudson, but there are  a
bunch of test failues with it:

https://hudson.apache.org/hudson/view/A-F/view/CXF/job/CXF-trunk-windows/lastBuild/testReport/

The job was setup with putting the checkout location (and the .m2
repo) into a directory with spaces (to test that scenario since, for
some reason, windows people like spaces in dirs) so some of the
tests may be failing for that reason. I just haven't had time to really
look into any of them, especially since I don't even have a windows
machine.

At some point, I'd like to also get some hudson builds on Solaris
and also on Linux using the IBM JDK.   Right now, a bunch of
tests fail with the 1.6 IBM JDK as well.

If anyone is looking for some places to start contributing, there's
a couple good ones.   :-)

Dan



On Friday 17 December 2010 5:14:29 am Jim Talbut wrote:
   Hi,

On revision 1050333 building on Windows Vista 64bit, java version
1.6.0_21, Maven 2.2.1, I hit the following error:

17-Dec-2010 09:09:05
org.apache.cxf.tools.validator.internal.WSDLRefValidator
collectValidationPointsForBindings
SEVERE: {http://child/}Binding is not correct, please check that the
correct namespace is being used

WSDLToJava Error: Thrown by JAXB: A class/interface with the same name
"org.apache.cxf.testcase.cxf3105.LoginResponse" is already in use. Use a
class customization or the -autoNameResolution option to resolve this
conflict.

Tests run: 63, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 21.963
sec<<<  FAILURE!
testCXF3105(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)  Time
elapsed: 0.078 sec<<<  FAILURE!
java.lang.AssertionError:
          at org.junit.Assert.fail(Assert.java:91)
          at org.junit.Assert.assertTrue(Assert.java:43)
          at org.junit.Assert.assertTrue(Assert.java:54)
          at
org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest.testCXF3105(CodeGenBugTest .java:1148) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
9) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
l.java:25) at java.lang.reflect.Method.invoke(Method.java:597)



Looking at the wsdl I wonder if this is caused by a case insensitivity
issue on Windows?

Jim


# This patch file was generated by NetBeans IDE
# Following Index: paths are relative to: C:\Work\cxf\tools\wsdlto\test\src\test
# This patch can be applied using context Tools: Patch action on respective 
folder.
# It uses platform neutral UTF-8 encoding and \n newlines.
# Above lines and this line are ignored by the patching process.
Index: java/org/apache/cxf/tools/wsdlto/jaxws/CodeGenBugTest.java
--- java/org/apache/cxf/tools/wsdlto/jaxws/CodeGenBugTest.java Base (BASE)
+++ java/org/apache/cxf/tools/wsdlto/jaxws/CodeGenBugTest.java Locally Modified 
(Based On LOCAL)
@@ -1147,8 +1147,8 @@
         File f = new File(output, 
"org/apache/cxf/testcase/cxf3105/Login.java");
         assertTrue(f.exists());
         String contents = IOUtils.readStringFromStream(new FileInputStream(f));
-        assertTrue(contents.contains("Loginrequest loginRequest"));
-        assertTrue(contents.contains("<Loginresponse> loginResponse"));
+        assertTrue(contents.contains("Loginrequesttype loginRequest"));
+        assertTrue(contents.contains("<Loginresponsetype> loginResponse"));
     }
 
 }
Index: resources/wsdl2java_wsdl/cxf3105/cxf3105.wsdl
--- resources/wsdl2java_wsdl/cxf3105/cxf3105.wsdl Base (BASE)
+++ resources/wsdl2java_wsdl/cxf3105/cxf3105.wsdl Locally Modified (Based On 
LOCAL)
@@ -2,13 +2,13 @@
 <wsdl:definitions xmlns:fc="http://cxf.apache.org/testcase/cxf3105"; 
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; 
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; name="center" 
targetNamespace="http://cxf.apache.org/testcase/cxf3105";>
     <wsdl:types>
         <xsd:schema targetNamespace="http://cxf.apache.org/testcase/cxf3105";>
-            <xsd:complexType name="loginrequest">
+            <xsd:complexType name="loginrequesttype">
                 <xsd:sequence>
                     <xsd:element name="username" type="xsd:string"/>
                     <xsd:element name="password" type="xsd:string"/>
                 </xsd:sequence>
             </xsd:complexType>
-            <xsd:complexType name="loginresponse">
+            <xsd:complexType name="loginresponsetype">
                 <xsd:sequence>
                     <xsd:element name="userid" type="xsd:int"/>
                     <xsd:element name="groupid" type="xsd:int"/>
@@ -19,7 +19,7 @@
             <xsd:element name="login">
                 <xsd:complexType>
                     <xsd:sequence>
-                        <xsd:element name="login" type="fc:loginrequest"/>
+                        <xsd:element name="login" type="fc:loginrequesttype"/>
                         <xsd:element name="id" type="xsd:int" maxOccurs="1" 
minOccurs="0"/>
                     </xsd:sequence>
                 </xsd:complexType>
@@ -27,7 +27,7 @@
             <xsd:element name="loginResponse">
                 <xsd:complexType>
                     <xsd:sequence>
-                        <xsd:element name="login" type="fc:loginresponse"/>
\ No newline at end of file
+                        <xsd:element name="login" type="fc:loginresponsetype"/>
\ No newline at end of file
                         <xsd:element name="password_temp" type="xsd:string"/>
                     </xsd:sequence>
                 </xsd:complexType>

Reply via email to