Welcome to the "trac"-ing site of soap4r!
[soap4r] [httpclient] [openpgp4u] [pkcs1] [logger] [csv] [vtr]

Ticket #413 (closed defect: fixed)

Opened 8 months ago

Last modified 8 months ago

what if the same name would be used in one XML namespace for an element and a complexType?

Reported by: nahi Assigned to: nahi
Priority: normal Milestone: 1.5.8
Component: wsdl4r Version: 1.5
Keywords: Cc:

Description

from soap4r-ml 

However, what if the same name would be used in one XML namespace for
an element and a complexType? In my case the element and complexType
are in different XML namespaces, but they could be in the same XML
namespace, couldn't they?

Change History

09/06/07 22:43:10 changed by nahi

  • milestone changed from undefined to 1.5.8.

09/06/07 22:52:28 changed by nahi

  • status changed from new to closed.
  • resolution set to fixed.

(In [1938]) * ignore xsd:element definition when the same qname is also defined as a xsd:complexType. closes the ticket now but could not be ignored in the future. closes #413.

09/08/07 23:25:56 changed by nahi

  • status changed from closed to reopened.
  • resolution deleted.

[1938] generates; 

class Foo
  class Bar
...
class Foo_
  class Bar_

but Foo_::Bar_ should be Foo_::Bar (without trailing '_') because it does not introduce name conflict.

09/10/07 10:28:28 changed by nahi

  • status changed from reopened to closed.
  • resolution set to fixed.

(In [1948]) * let ClassNameCreator? handle modulepath. Foo::Baz and Bar::Baz have the same name (Baz) but these are different qnames so there's no need for name crash avoidaidance. closes #413.