[XML-DEV Mailing List Archive Home]
[Reply To This Message]
Re: xs:complexType node element invalid inside another complex
- From: "Pete Cordell" <petexmldev@c...>
- To: "ilango" <ilangocal@y...>
- Date: Tue, 5 Feb 2008 20:03:38 -0000
Follow-on questions should really go to the list
rather than individuals. (The individual you ask may not be able to
answer the question, or they might not have time to look into it, which puts
them in a difficult position. Also, others on the list like to know
what has been exchanged - sometimes!)
In this case, if you make the suggested changes
(when you get them!) the elements should be members of input and
BTW - you should consider making aliasLookUpType a global type at the top level
(i.e. not nested within another element declaration). e.g. straight after
the xs:schema start tag do:
and where you want the elements,
Visit http://www.codalogic.com/lmx/ for XML
C++ data binding
----- Original Message -----
Sent: Tuesday, February 05, 2008 7:49
Subject: Re: xs:complexType
node element invalid inside another complexType?
Is it possible to redesign this new element so that it is part of the
<xs:element name="output"> respectively.
Pete Cordell <petexmldev@c...>
boldness seems to have been lost so it's not clear which is the element
in question. Also, what error messages are you getting?
the bit you've commented out, then the correct XML schema for that
your defining an element that is a complexType, not a complexType on
http://www.codalogic.com/lmx/ for XML C++ data binding
Sent: Tuesday, February 05, 2008 5:30
Subject: xs:complexType node element invalid inside another
> 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
> XForm that is composed of elements "name_last_lookup" (or
> preferred because it is already there),
"id_ssn_lookup" (id_ssn is
> 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
> avoid any
| [Thread Prev]
| [Thread Next]
| [Date Next]
| [Thread Index]
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format
Stylus Studio has published XML-DEV in RSS and ATOM formats,
enabling users to easily subcribe to the list from their preferred news reader application.
Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website.
they were not included by the author in the initial post. To view the content without the Sponsor Links please