[jdom-interest] XMLOutputter to the rescue (get/setText)

[Steven D. Keens]

Your right about the mission-critical app, but why is it so important to
keep the ambiguous method names? Is it to reduce typing, to have a
symmetrical API, or to avoid having to replace all your calls to setText()
with the new name?

--
Steven Keens                mailto:skeens at planetfred.com
Planetfred Inc.             http://www.planetfred.com
44 Byward Market, Suite 240, Ottawa, ON, K1N 7A2, Canada

The most exciting phrase in science, the one which heralds
new discoveries, is not "Eureka!", but "That's funny!"
                       -- Isaac Asimov


>-----Original Message-----
>From: Alex Rosen [mailto:arosen at silverstream.com]
>Sent: Thursday, July 12, 2001 11:24
>To: 'Steven D. Keens'; 'jdom-interest'
>Subject: RE: [jdom-interest] XMLOutputter to the rescue (get/setText)
>
>
>> If we want to use JDOM in a mission critical environment then we
>should be
>> worrying about preventing the unexpected and ambiguous at all costs.
>
>A mission-critical app should receive mission-critical testing. A
>mission-critical app that fails because of the programmer's
>misunderstanding of
>getText() and setText(), despite the documentation, will have lots of other
>problems too...
>
>Alex
>
>