Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-672

JBossWS WSDL not creating type for Array Object during deployment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • jbossws-1.0RC2
    • jbossws-1.0RC1
    • tools-jaxrpc
    • None

      JBossWS is not generating the type information for Array Type Object. The type information for class Result is missing in WSDL.

      If you look at the class below, the "Hacked" Result class will generate WSDL correctly.

      Definitely it's a bug.

      Code:

      class MyObject
      {
      protected String name;
      MyObject() {};
      String getName()

      { return "myName"; }

      void setName(String value)

      { name = value; }

      }

      /** Normal Result Class */

      class Result
      {
      Result() {}
      protected long id;
      protected MyObject[] myObjects;

      long getId()

      { return id; }
      void getId(long value) { id = value; }

      MyObject[] getMyObjects() { return myObjects; }
      void setMyObjects(MyObject[] values) { myObjects = values; }
      }

      /** Hacked Result Class */

      class Result
      {
      Result() {}
      protected long id;
      protected MyObject[] myObjects;

      long getId() { return id; }

      void getId(long value)

      { id = value; }

      /** A hack to fool JBossWS to generate the type information */
      MyObject getMyObject()

      { return myObject; }

      void setMyObject(MyObject value)

      { myObject = value; }

      MyObject[] getMyObjects()

      { return myObjects; }

      void setMyObjects(MyObject[] values)

      { myObjects = values; }

      }

      WS SEI:

      Result getResult()

      { return result; }

            Unassigned Unassigned
            julianhtun_jira Julian Htun (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: