axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From axis-c-...@ws.apache.org
Subject [jira] Resolved: (AXISCPP-108) WSDL2WS unable to compile ComplexTypes
Date Mon, 13 Sep 2004 05:25:37 GMT
Message:

   The following issue has been resolved as WON'T FIX.

   Resolver: Samisa Abeysinghe
       Date: Sun, 12 Sep 2004 10:25 PM

The ordering of the JAR files is a problem at the moment with Axis C++ WSDL2Ws java tool using
the same package and class names as that of Axis Java. 
Fixing this requires refactoring the WSDL2Ws tool which would hopefully happen in a future
release.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-108

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-108
    Summary: WSDL2WS unable to compile ComplexTypes
       Type: Bug

     Status: Resolved
   Priority: Major
 Resolution: WON'T FIX

    Project: Axis-C++
 Components: 
             WSDL generation
   Fix Fors:
             1.3 Beta
   Versions:
             1.2 Beta

   Assignee: 
   Reporter: Marcus Tillmanns

    Created: Fri, 2 Jul 2004 4:54 AM
    Updated: Sun, 12 Sep 2004 10:25 PM
Environment: Windows 2000, Apache 2, java1.4_2

Description:
When trying to compile the example WSDL's that use own ComplexType Structs, the WSDL2WS tool
crashes with:

args =
args =
args =
1
############## the type found ={http://soapinterop.org/xsd}JobStruct
Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.axis.wsdl.sym
bolTable.ElementDecl.getMinOccrs()I
        at
org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.createTypeInfo(WSDL2Ws.java:600)

        at
org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.getTypeInfo(WSDL2Ws.java:377)
        at
org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.genarateWrappers(WSDL2Ws.java:40
2)
        at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.main(WSDL2Ws.java:684)

This happens in all WSDLs including my own I tried. Even a colleague of mine has the same
problems. You can use the MathOps example to test this behaviour



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message