Jump to content

immo_we

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

1 Neutral

About immo_we

  • Rank
    Newbie
  1. Hi I have a tree leaf with several objects referring to a different list how to verify them ? The list of objects <myElementList> <myelement ip="10.0.3.21" slot="1" port="1" > <switchPort id="6" port="35" /> </myelement> <myelement ip="10.0.3.21" slot="1" port="2" > <switchPort id="6" port="36" /> </myelement> </myElementList> The list of allowed SwitchPorts <switchList> <switch id="1" ip="10.3.3.34" /> <switch id="2" ip="10.3.3.35" /> <switch id="3" ip="10.3.3.36" /> <switch id="4" ip="10.3.3.37" /> <switch id="5" ip="10.3.3.38" /> <switch id="6" ip="10.3.3.39" /> </switchList> So how to verify via xsd path that every switchPort in the objectList referes to a switch in the Switchlist (ID=KEY) Immo
  2. Hello, I try to extend a complexType/SimpleContent but the mixture of simple and complex seems to be a problem.Could you explain how I can create simple elements on one side with LOGIN_TYPE and extent this to to a complexType with subelements as HOST_TYPE <xs:element name="ipDevice"> <xs:complexType> <xs:sequence> <xs:element type="ivtb:HOST_TYPE" name="Comment" /> </xs:sequence> </xs:complexType> </xs:element> <xs:complexType name="LOGIN_TYPE"> <xs:simpleContent> <xs:extension base="xs:string"> <xs:attribute type="xs:string" name="login" use="required" /> <xs:attribute type="xs:string" name="password" use="required" /> </xs:extension> </xs:simpleContent> </xs:complexType> <xs:complexType name="HOST_TYPE"> <xs:complexContent> <xs:extension base="ivtb:LOGIN_TYPE" > <xs:all> <xs:element name="OS" type="xs:string" default="no specified"/> </xs:all> </xs:extension> </xs:complexContent> </xs:complexType>
  3. Hi is there any way to prevent via schema that the default namespace will be used vor a certain schema? currently I've defined this root element in the xml file: <rootEle name="Test4" schemaVersion="2.0" xmlns="http://www.example.org/testSchema"'>http://www.example.org/testSchema" xmlns:sch="http://www.example.org/testSchema"'>http://www.example.org/testSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.example.org/testSchema testSchema.xsd ">now I can use<sch:ele1> together with <ele1>both have the same meaning and this looks quite terrible for forming useful xpath queries.I would like to expect only elements in the form <sch:ele1> ... Immo
×
×
  • Create New...