incubator-yoko-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Murphy (JIRA)" <>
Subject [jira] Created: (YOKO-358) IDLToWSDL incorrectly maps all typedefs to restrictions.
Date Wed, 25 Apr 2007 14:07:15 GMT
IDLToWSDL incorrectly maps all typedefs to restrictions.

                 Key: YOKO-358
             Project: Yoko - CORBA Server
          Issue Type: Bug
          Components: Idl2Wsdl
    Affects Versions: v1.0-incubating-M1
         Environment: Tested on Windows, will probably be on all platforms.
            Reporter: Martin Murphy
            Priority: Critical

Consider IDL like :
  typedef string PropertyName;
  typedef string PropertyValue;
  struct Property {
    PropertyName name;
    PropertyValue value;
  typedef sequence <Property> PropertyList;
  typedef PropertyList MyProperties;

This will produce invalid WSDL like

      <xs:simpleType name="PropertyName">
        <xs:restriction base="xs:string">
      <xs:simpleType name="PropertyValue">
        <xs:restriction base="xs:string">
      <xs:complexType name="Property">
          <xs:element name="name" type="PropertyName">
          <xs:element name="value" type="PropertyValue">
      <xs:complexType name="PropertyList">
          <xs:element maxOccurs="unbounded" minOccurs="0" name="item" type="Property">
      <xs:simpleType name="MyProperties">
        <xs:restriction base="PropertyList">

The simpleType MyProperties is not valid schema as per
(section 3.14) : 
Schema Component Constraint: Derivation Valid (Restriction, Simple)
The appropriate case among the following must be true:
1 If the {variety} is atomic, then all of the following must be true:
   1.1 The {base type definition} must be an atomic simple type definition or a built-in primitive

This presents a bit of a problem. Should all typedefs be ignored, or should only typedefs
where the base is not a simple type or built-in primitive datatype be handled?
The IDLToWSDL tool also produces invalid code for a typedef on an any since you can't have
a restriction on a schema anyType.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message