jax-ws
  1. jax-ws
  2. JAX_WS-823

JAXWS 2.2 wsgen does not generate the correct wsdl and schema files

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Incomplete
    • Affects Version/s: 2.2
    • Fix Version/s: 2.2.2
    • Component/s: wsgen
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      823

      Description

      Problem:

      When using metro 2 (with JAXWS 2.2) the wsgen process does not create the
      correct set of files (wsdl and *schema?.xsd files).

      The expected resulting set of files should include the wsdl file containing the
      service definition and the schema imports for: 1) the service operations and 2)
      any other classes residing in other namespaces different from the service target
      namespace.

      Instead, the resulting set only includes the wsdl file and a single schema1.xsd
      file with all service operations and classes mixed into the same weg service
      target namespace.

      This poses a big problem when trying to generate the correct service client
      classes using wsimport with the wsdl created by wsgen.

      However if the webservice is deployed, the wsdl generated dynamically by the app
      server (I'm using glassfish 2.1 and 3), is the correct one, meaning all ?xsd=1,
      ?xsd=2, ... return the correct objects in their corresponding namespaces.

      To illustrate this issue, I'm posting below a URL to a simple application using
      Netbeans 6.8 and glassfish 3. Please look at the files generated by wsgen @
      WEB-INF/wsdl/localhost_8080 and compare with the wsdl returned dynamically by
      the GF server after deployment
      (http://localhost:8080/WebApplication1/MyTestService?wsdl)

      http://forums.java.net/jive/servlet/JiveServlet/download/46-72656-381238-11220/WebApplication1.zip

      Thanks

      JC Ferrer

        Activity

        jcferrer created issue -
        Hide
        jitu added a comment -

        May be some schemas are getting overwritten. Need to investigate here.

        Show
        jitu added a comment - May be some schemas are getting overwritten. Need to investigate here.
        Hide
        jitu added a comment -

        I see all the schema files are generated properly. May be your issue is some
        configuration issue or netbeans issue. See below:

        -----------------------
        /WebApplication1/src/java$ javac test/jaxb/*.java test/services/MyTest.java

        /WebApplication1/src/java$ $JAXWS_HOME/bin/wsgen.sh -d tmp -wsdl -cp $CLASSPATH
        test.services.MyTest

        /WebApplication1/src/java$ ls tmp
        MyTestService_schema1.xsd MyTestService_schema2.xsd MyTestService.wsdl test
        ------------------------

        Show
        jitu added a comment - I see all the schema files are generated properly. May be your issue is some configuration issue or netbeans issue. See below: ----------------------- /WebApplication1/src/java$ javac test/jaxb/*.java test/services/MyTest.java /WebApplication1/src/java$ $JAXWS_HOME/bin/wsgen.sh -d tmp -wsdl -cp $CLASSPATH test.services.MyTest /WebApplication1/src/java$ ls tmp MyTestService_schema1.xsd MyTestService_schema2.xsd MyTestService.wsdl test ------------------------
        kenaiadmin made changes -
        Field Original Value New Value
        issue.field.bugzillaimportkey 823 12417

          People

          • Assignee:
            jitu
            Reporter:
            jcferrer
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: