[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: The DOM and the victim, the iconoclast and the believer

  • From: David Brownell <david-b@p...>
  • To: martind@n...
  • Date: Sun, 16 Jan 2000 10:30:02 -0800

multiple interface inheritance
Didier PH Martin wrote:
> David, you are right on this point. Some ORB just throw an exception when we
> access a non exiting member. I am actually checking where in the OMG specs
> it is explicitely mentionned. It discovered that it is not all ORB that has
> this behavior. Now the question is: Is this behavior (to throw an exception
> when a required member is not there) is a specified characteristic or simply
> because some ORB manufacturers are more clever than others.

CORBA 1.0 defined an exception for that purpose; I don't know why
any ORB wouldn't report that system exception when the client calls
a method that doesn't exist, other than a bug.  Certainly succeeding
by calling some other method is incorrect.

There's also Node.getOwnerDocument().getImplementation().hasFeature()...

> Yes memory menagement is problematic, I agree. But also to have a single
> binary signature convention may be against manufacturers interests since I
> am no longer the prisoner of a single ORB vendor.

That's another one of the issues.  But "inout" parameters were always
the cause of some major chaos.

> David said:
> That said ... I think I would agree that changing already-published
> interfaces was pretty much against the spirit of IDL.  It'd have been
> much more natural to define a new module (C++ namespace, Java package)
> that inherited the old interfaces and added new methods:  no change
> of current interfaces/contracts.  IDL has multiple interface inheritance
> to allow that style of evolution, among other reasons.
> Didier reply:
> Yes I agree on this, on several ORB that I made my test, inheritence is
> working well, so, as you said, if suffice to have the new interface to
> inherit from the old. That way, we know waht is part of the old contract and
> what is part of the new one.

Again, if it is NOT working in some ORB, it's got bugs that'd make me
avoid using it.  Multiple interface inheritance has again been part of
IDL since CORBA 1.0, and it's not like it's hard to get right.

- Dave

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ or CD-ROM/ISBN 981-02-3594-1
Please note: New list subscriptions now closed in preparation for transfer to OASIS.


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3

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 click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.