New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multiple xs:group refs introduced via extension produces two arg1 #192

Closed
eed3si9n opened this Issue Feb 12, 2013 · 0 comments

Comments

Projects
None yet
1 participant
@eed3si9n
Owner

eed3si9n commented Feb 12, 2013

steps

  1. define a xs:complexType with a xs:group ref.
  2. define another xs:complexType extending the above type and add another xs:group ref.
  <xs:complexType name="SequenceGroupTest">
    <xs:sequence>
      <xs:group ref="gen:Group1" minOccurs="1" maxOccurs="1" />
    </xs:sequence>
  </xs:complexType>

  <xs:complexType name="ExtendedGrouprefTest">
    <xs:complexContent>
      <xs:extension base="gen:SequenceGroupTest">
        <xs:sequence>
          <xs:group ref="gen:Array" minOccurs="1" maxOccurs="1" />
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>

problem

both refs generate arg1, and can't be compiled.

case class ExtendedGrouprefTest(arg1: general.Group1Sequence,
  arg1: general.ArraySequence) extends SequenceGroupTestable

expectation

follow underlying compositor's naming.

@eed3si9n eed3si9n closed this in 3d55057 Feb 21, 2013

eed3si9n added a commit that referenced this issue Apr 14, 2013

eed3si9n added a commit that referenced this issue Apr 17, 2013

eed3si9n added a commit that referenced this issue May 20, 2013

eed3si9n added a commit that referenced this issue May 26, 2013

eed3si9n added a commit that referenced this issue Jul 18, 2013

eed3si9n added a commit that referenced this issue Jul 28, 2013

eed3si9n added a commit that referenced this issue Sep 12, 2013

eed3si9n added a commit that referenced this issue Nov 8, 2014

eed3si9n added a commit that referenced this issue Jul 7, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment