> From: Leif Mortenson [mailto:[EMAIL PROTECTED]] > > What is the coding standard for Avalon code? Are cases like this > considered a problem in the Avalon class? Or are they only required to > not throw NullPointerExceptions etc if the contacts are followed exactly? > > I vote for making the Avalon classes as rugged as possible in cases like > this. Esp the classes which new users are most likely to be having to > access directly from their own containers.
Leif, we (on the list) have been through this before. For some background, check: http://marc.theaimsgroup.com/?l=avalon-dev&w=2&r=1&s=ComponentValidator&q=b You may want to know what's already been said if this issue comes up again (and it will). /LS -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
