Details

    • Type: New Feature New Feature
    • Status: Reopened
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: unspecified
    • Fix Version/s: TBD
    • Component/s: Compiler
    • Labels:
      None
    • Environment:
      n/a

      Description

      When a WSDL file is passed to schema compiler it should iterate any WSDL imports and compile the schemas from them.

      Since the WSDL file is importing another WSDL with a potential schema block, it is useful to generate the types from the imports since they are probably referenced in the WSDL (why else import them)....

      This could be an option to SchemaCompiler, a flag for turning this feature on and off for backward compatibility....

        Issue Links

          Activity

          Hide
          Gurpreet added a comment -

          Any tentative timeframe, by when this would be fixed?

          Show
          Gurpreet added a comment - Any tentative timeframe, by when this would be fixed?
          Hide
          Sumit Rastogi added a comment -

          This issue is same as the issue I have linked. The feature in which compiler should check all the wsdl imported using <wsdl:import> and this should be suported by all databinding tool supported by axis2.

          Show
          Sumit Rastogi added a comment - This issue is same as the issue I have linked. The feature in which compiler should check all the wsdl imported using <wsdl:import> and this should be suported by all databinding tool supported by axis2.
          Hide
          Radu Preotiuc-Pietro added a comment -

          Postponing for the next version.

          Show
          Radu Preotiuc-Pietro added a comment - Postponing for the next version.
          Hide
          Sal Campana added a comment -

          I'd love to get involved if you are seeking help from people who currently have non-committer status....

          if that is the case, let me know how you would like to proceed...

          thanks!

          Show
          Sal Campana added a comment - I'd love to get involved if you are seeking help from people who currently have non-committer status.... if that is the case, let me know how you would like to proceed... thanks!
          Hide
          Radu Preotiuc-Pietro added a comment -

          I agree that we should investigate this for the future. XMLBeans is really not about WSDL at all, but we have added the ability to load Schema documents from within WSDL as a "nicety" on the sides. Now we should take it one step further and also process imports. If anyone is interested in contributing to this area of XMLBeans, I volunteer to help, since I know that part of the code.

          Show
          Radu Preotiuc-Pietro added a comment - I agree that we should investigate this for the future. XMLBeans is really not about WSDL at all, but we have added the ability to load Schema documents from within WSDL as a "nicety" on the sides. Now we should take it one step further and also process imports. If anyone is interested in contributing to this area of XMLBeans, I volunteer to help, since I know that part of the code.
          Hide
          Jacob Danner added a comment -

          After a email thread with Sal, I understand what he intended. This is a feature we should investigate in a later version

          Show
          Jacob Danner added a comment - After a email thread with Sal, I understand what he intended. This is a feature we should investigate in a later version
          Hide
          Sal Campana added a comment -

          I think there is a misunderstanding here...

          I am talking about imported WSDL files...

          If you open the brokernotification wsdl you will see that it does a WSDL import of http://www.ibm.com/xmlns/stdwip/web-services/WS-ResourceProperties....

          I am suggesting that scomp iterate all of the WSDL IMPORTS and process thier schemas as well...

          In this case the schema block in the BrokerNotification also happens to import the xsd of ResourceProperties...But what about the schema defined in the ResourceProperties wsdl file???

          Show
          Sal Campana added a comment - I think there is a misunderstanding here... I am talking about imported WSDL files... If you open the brokernotification wsdl you will see that it does a WSDL import of http://www.ibm.com/xmlns/stdwip/web-services/WS-ResourceProperties .... I am suggesting that scomp iterate all of the WSDL IMPORTS and process thier schemas as well... In this case the schema block in the BrokerNotification also happens to import the xsd of ResourceProperties...But what about the schema defined in the ResourceProperties wsdl file???
          Hide
          Jacob Danner added a comment -

          only verified using versions noted above, but 1.03 should be okay as well.

          Show
          Jacob Danner added a comment - only verified using versions noted above, but 1.03 should be okay as well.
          Hide
          Jacob Danner added a comment -

          This appears to work. Using the WSDL reference below:
          http://devresource.hp.com/drc/specifications/wsrf/interfaces/WS-BrokeredNotification-1-0.wsdl

          command lines:
          1) scomp <without -dl>
          results in:
          H:\xml\xml-xmlbeans\v2\Jira_59\WS-BrokeredNotification-1-0.wsdl:124: error: src-
          resolve: element 'CreationTime@http://www.ibm.com/xmlns/stdwip/web-services/WS-B
          rokeredNotification' not found.

          2) scomp -dl
          results in:
          Time to build schema type system: 23.515 seconds
          Time to generate code: 2.157 seconds
          Time to compile code: 7.593 seconds
          Compiled types to: xmltypes.jar

          Show
          Jacob Danner added a comment - This appears to work. Using the WSDL reference below: http://devresource.hp.com/drc/specifications/wsrf/interfaces/WS-BrokeredNotification-1-0.wsdl command lines: 1) scomp <without -dl> results in: H:\xml\xml-xmlbeans\v2\Jira_59\WS-BrokeredNotification-1-0.wsdl:124: error: src- resolve: element 'CreationTime@ http://www.ibm.com/xmlns/stdwip/web-services/WS-B rokeredNotification' not found. 2) scomp -dl results in: Time to build schema type system: 23.515 seconds Time to generate code: 2.157 seconds Time to compile code: 7.593 seconds Compiled types to: xmltypes.jar
          Hide
          Dave Remy added a comment -

          Any chance you could investigate this? It seems like this should work if the download option is used.

          Show
          Dave Remy added a comment - Any chance you could investigate this? It seems like this should work if the download option is used.

            People

            • Assignee:
              Radu Preotiuc-Pietro
              Reporter:
              Sal Campana
            • Votes:
              3 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:

                Development