axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ronny Riedel (JIRA)" <axis-...@ws.apache.org>
Subject [jira] Created: (AXIS-2089) WSDL2Java -> wrapped: wrong code generation
Date Tue, 28 Jun 2005 11:25:07 GMT
WSDL2Java -> wrapped: wrong code generation
-------------------------------------------

         Key: AXIS-2089
         URL: http://issues.apache.org/jira/browse/AXIS-2089
     Project: Apache Axis
        Type: Bug
  Components: WSDL processing  
    Versions: 1.2RC2, 1.2.1    
 Environment: SuSE Linux Enterprise Server 9
-- 
Apache Tomcat/5.0.27 with Axis 1.2RC2 / 1.2.1
-- 
java version "1.4.2_03"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02)
Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode)
    Reporter: Ronny Riedel
 Attachments: DDTSService.wsdl

In reference to the added wsdl-file, there are some strange behaviors. all are in relation
to the type-definition section in the wsdl-document. I have marked them with "<!-- ############
-->". There are 2 choises for type-defintion at this 4 locations: "xsd:string" or "typ:myString".
following options / results:

(1) all 4 are "xsd:string" 
         -> doc/lit in the deploy.wsdd 
         -> classes are generated for all needed objects
         -> *BindingImpl.java returs objects
      ---> Ok, but i want "wrapped"
(2) all 4 are "typ:myString"
         -> wrapped in the deploy.wsdd 
         -> only class "FileEnclosure" are generated
         -> *BindingImpl.java returs void, data returned via holder-classes
         -> via TCPMonitor, the response from "getDefectInfo" looks like 

                    <getDefectInfoResponse xmlns="http://types.ngit.integration.tmobile.org/">
                       <Defect>strClass>IV98_defects</Defect>strClass>
                       <Defect>strProject>kundenpflege_d</Defect>strProject>
                       <Defect>strShowstopper xsi:nil="true"/>
                       [...]
                    </getDefectInfoResponse>

            and this doesn't look like "correct" xml :-)
      ---> WRONG, because of mystyrious Response
(3) the first 3 are "xsd:string, the last is "typ:myString"
         -> wrapped in the deploy.wsdd 
         -> only class "FileEnclosure" are generated
         -> *BindingImpl.java returs objects, which are NOT GENERATED (for example: the
*BindingImpl-Class returns "Defect", but these typ isn't generated)
      ---> WRONG, because of missing referenced types

in relation to points (2) and (3): There are no warnings/errors/hints. And i wonder, that
depending on a different choosen typ, such different code is generated.

regards
  rig

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message