Types in wsdl not imported. Any news??

Any news about it? ....



when importin a wsdl, the next comment is add to .pas:

 // ************************************************************************
//
  // The following types, referred to in the WSDL document are not being
represented
  // in this file. They are either aliases[@] of other types represented or
were referred
  // to but never[!] declared in the document. The types from the latter
category
  // typically map to predefined/known XML or Borland types; however, they
could also
  // indicate incorrect WSDL documents that failed to declare or import a
schema type.
  //
************************************************************************ //
  // !:MessageHeader   -
"http://www.ebxml.org/namespaces/messageHeader"
  // !:Security        -
"http://schemas.xmlsoap.org/ws/2002/12/secext"
  // !:SessionCreateRQ - "http://www.opentravel.org/OTA/2002/11"
  // !:SessionCreateRS - "http://www.opentravel.org/OTA/2002/11"

and project has error when compiled.

any help?

[]'s

Agostinho

when importin a wsdl, the next comment is add to .pas:

 // ************************************************************************
//
  // The following types, referred to in the WSDL document are not being
represented
  // in this file. They are either aliases[@] of other types represented or
were referred
  // to but never[!] declared in the document. The types from the latter
category
  // typically map to predefined/known XML or Borland types; however, they
could also
  // indicate incorrect WSDL documents that failed to declare or import a
schema type.
  //
************************************************************************ //
  // !:MessageHeader   -
"http://www.ebxml.org/namespaces/messageHeader"
  // !:Security        -
"http://schemas.xmlsoap.org/ws/2002/12/secext"
  // !:SessionCreateRQ - "http://www.opentravel.org/OTA/2002/11"
  // !:SessionCreateRS - "http://www.opentravel.org/OTA/2002/11"

and project has error when compiled.

any help?

[]'s

Agostinho

Hello Agostinho,

Thank you for the reminder. I finally had some time to return to my
newsgroup issues today. I apologize for the delay but the impending release
of C++Builder has taken all of my office time (and much more) lately.

I'll try to resume the work on this (once I finish catching up with the
newsgroup) later tonight and hope I can relay my findings tomorrow.

Cheers,

Bruneau.

Hello,

As mentioned in the other thread, I resumed work on SOAP on Monday and have
started work on a solution for this issue [it's related to the fact that we
did not handle global <element..> that defined a complextype (or
simpletype)
inline].

Once more, I have to apologize for the delay: my manager kindly gave me
(well, the whole team) a few days of rest given the weekends/late-nights we
worked recently. So, I'm currently at home, keeping up with email/newsgroup
but not doing much work. I'll be back in the office on Friday and will
resume work on this issue.

Cheers,

Bruneau

OK ... ;-)

[]'s

Agostinho




"Jean-Marie Babet" <bbabet@borland.com> escreveu na mensagem
news:4666fb44$1@newsgroups.borland.com...
> Hello,
>
> As mentioned in the other thread, I resumed work on SOAP on Monday and
have
> started work on a solution for this issue [it's related to the fact that
we
> did not handle global <element..> that defined a complextype (or
simpletype)
> inline].
>
> Once more, I have to apologize for the delay: my manager kindly gave me
> (well, the whole team) a few days of rest given the weekends/late-nights
we
> worked recently. So, I'm currently at home, keeping up with
email/newsgroup
> but not doing much work. I'll be back in the office on Friday and will
> resume work on this issue.
>
> Cheers,
>
> Bruneau
>
>

Hello,

I spent some time on this yesterday and it's quite puzzling: every importer
I tried has something to complain about.

Besides the mis-handling of global element with inline complex type (I
mentioned in the other post), the Delphi importer is failing to detect that
'MessageHeader' (and 'Security' too although the type 'Security', unlike
MessageHeader, is emitted in the .pas file) is a header of the operation. It
does detect that there are headers but it does not make the connection that
the first two parameters are indeed the headers:

   // Headers: header:pInOut, header2:pInOut
    function  SessionCreateRQ(var header: MessageHeader; var header2:
Security; const body: SessionCreateRQ): SessionCreateRS; stdcall;
  end;


I opted to switch to a different importer as each one has abilities to
detect certain errors that the others may miss. So, I tried the .NET
importer. It gave me:

Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 2.0.50727.42]
Copyright (C) Microsoft Corporation. All rights reserved.
Error: Unable to import binding 'SessionCreateSoapBinding' from namespace
'https
://webservices.sabre.com/websvc'.
  - Unable to import operation 'SessionCreateRQ'.
  - The element
'http://www.ebxml.org/namespaces/messageHeader:MessageHeader' is
 missing.


There's a common theme here: somehow 'MessageHeader' is problematic.

Next I opted to try Axis' importer. It gave me:


c:\dev\axis-1_4\lib\wsdl2java.bat SessionCreateRQ.wsdl

WSDLException (at /definitions/types/xsd:schema/schema):
faultCode=OTHER_ERROR:
An error occurred trying to resolve schema referenced at 'env.xsd', relative
to
'file:envelope.xsd'.: This file was not found: file:env.xsd:
java.io.FileNotFoundException: This file was not found: file:env.xsd


Ah ah... Indeed, envelope.xsd contains the following statement:

    <include schemaLocation="env.xsd" />

But I don't have a copy of env.xsd.


Interestingly though I don't think that not having env.xsd is the problem
(although the importer should have reported that it could not find an
importer schema). The ultimate issue, it seems, is why 'MessageHeader's it
not being properly read. So while delving into msg-header_2-0.xsd, I noticed
that it imports 4 other schema files: xmlsig-core-schema.xsd, xlink.xsd,
envelope.xsd and xml.xsd.

At this point I'd like to propose a different approach:

#1. If the WSDL is stable, I can hand-edit the 'SessionCreateRQ1.pas'
produced now to
(a) Add the MessageHeader header
(b) Remove the two extra parameters on the 'SessionCreateRQ' operation

#2 If you have copies of the additional .xsd I mentioned above, please send
me a copy and, if time allows, please open a QC report for this issue. It
will more time to investigate and me doing this on the side won't work. Once
a QC is in I can request and hopefully be allocated proper time to
investigate this more.

Let me know if you'd like a hand-edited version of the file.

Cheers,

Bruneau.