> There were PSVI methods named isXXX(). The component API uses getIsXXX() in > this case, to make it possible to have IDL definition for the interfaces in > the future (by making IsXXX an attribute). To follow the same fashion, > isXXX methods are changed to getIsXXX().
The DOM's solution was to say that the IDL attribute's name was XXX, and that the Java binding for retrieving boolean attributes was isXXX rather than getXXX to follow Java Bean conventions. See, for example Attr.specified, which in Java is bound to the accessor isSpecified. This avoids the ugly getIsXXX syntax. But that's abstract IDL which is styled, rather than directly compiled, to produce the bindings. (Actually, XML source is styled to generate both.) I don't know enough about IDL to say what's possible/reasonable in IDL itself. ______________________________________ Joe Kesselman / IBM Research --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
