xmlport multiple definition of element

BeliasBelias Member Posts: 2,998
edited 2012-11-14 in NAV Three Tier
Hi everyone, I'm back after some time of inactivity (due to heavy work :( )

I've an XMLPort that works in Classic client, but do not work if i try to expose it as webservice. Here's the error that the webservice returns (the error is returned even in the WSDL page that you can see in the browser).
Multiple definition of element 'OrderResponse:SpecialInstructions' causes the content model to become ambiguous. A content model must be formed such that during validation of an element information item sequence, the particle contained directly, indirectly or implicitly therein with which to attempt to validate each item in the sequence in turn can be uniquely determined without examining the content or attributes of that item, and without any information about the items in the remainder of the sequence
Here's the xmlport definition(it's very long, i post just a snippet)
SpecialInstructions
  InstructionTypeReferenceInformation
ReferenceInformation  
  ReferenceType
  DocumentReference
    DocumentIdentifier
    DateTime
    DateTimeQualifier
SpecialInstructions
  InstructionType
actually, the problem is obviously the double "SpecialInstructions" Element at the same indentation level. In my opinion, it's not correct, but as i said, the xmlport works fine in classic but does not work if exposed as webservice.
Do you know why and if there's a way to make it work as webservice, too?
Thanks in advance
-Mirko-
"Never memorize what you can easily find in a book".....Or Mibuso
My Blog

Comments

  • kinekine Member Posts: 12,562
    Hmm, for me it looks like it will not be possible to use it as WS. The 3tier architecture have changes in the XMLPort (allowing e.g. LAX etc.) and it means there are some additional checks.
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
Sign In or Register to comment.