Re: xs:complexType node element invalid inside another complex

----- Original Message -----

From: ilango

To: Pete Cordell

Sent: Tuesday, February 05, 2008 7:49 PM

Subject: Re: xs:complexType node element invalid inside another complexType?

hi

Is it possible to redesign this new element so that it is part of the

<xs:element name="input">

and

<xs:element name="output"> respectively.

 

thanks

ilango

 

 

Pete Cordell <petexmldev@c...> wrote:

Hi,

The boldness seems to have been lost so it's not clear which is the element
in question. Also, what error messages are you getting?

If it's the bit you've commented out, then the correct XML schema for that
is something like:











i.e. your defining an element that is a complexType, not a complexType on
its own.

HTH,

Pete Cordell
Codalogic
Visit http://www.codalogic.com/lmx/ for XML C++ data binding

----- Original Message -----
From: "XGuy"
To:
Sent: Tuesday, February 05, 2008 5:30 PM
Subject: xs:complexType node element invalid inside another
complexType?


>
> Hi
> I have the following schema. Recently I have introduced a new element (the
> one shown in bold) and I am getting errors. I am not sure how or where to
> introduce this element. I am trying to model a "repeat-structure" in an
> XForm that is composed of elements "name_last_lookup" (or "name_list" is
> preferred because it is already there), "id_ssn_lookup" (id_ssn is
> preferred
> because it is already defined), "arrestee_dob_lookup" (arrestee_dob" is
> preferred because it is already defined).
>
> Why are these errors being generated? How would I design this new element
> to
> avoid any errors?
>
>
> --------
>
>
> > xmlns:fe="http://www.i.com/bpms/workflow/xforms/MyForms/CComplaint"
>
> xmlns:CreateComplaint="http://www.i.com/bpms/workflow/xforms/MyForms/CComplaint"
> targetNamespace="http://www.i.com/bpms/workflow/xforms/MyForms/CComplaint"
> elementFormDefault="qualified">