commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <>
Subject RE: [configuration]More docs
Date Tue, 11 Nov 2003 16:04:21 GMT

Suggestion: add an Examples page (xdocs/examples.xml) to the nagivation
bar (xdocs/navigation.xml).  Write some examples there, starting with
very basic ones that seem trivial to you.  Maven will take care of
publishing it.  This is consistent with many other commons projects.  If
you need any help with the mechanical parts (writing xdocs, using maven
to publish the site, etc.) I'll be glad to help.  And as Senor Pugh
said, don't worry about your English ;)  Thanks,

Yoav Shapira
Millennium ChemInformatics

>-----Original Message-----
>From: Eric Pugh []
>Sent: Tuesday, November 11, 2003 10:50 AM
>To: 'Jakarta Commons Developers List'
>Subject: RE: [configuration]More docs
>I would say that your English is better then 90% of the english
>world, so don't feel hesitant writing docs.  I recommend using the xdoc
>format as that is native to Maven, and I would add maybe some "howto"
>Maybe  a: howto-configurationfactory.xml, howto-hierarchical.xml etc..
>The createXMLReader is an interesting idea..  However, I think that
>instead it would be better to have a ConfigurationXMLDocument that took
>Configuration object.  I am somewhat hesitant to add more methods to
>Configuration interface that arne't really directly related to
>configuration values.  Especially if it releies on each concrete class
>implementing it, as that starts to raise the bar more and more for
>the underlying concrete implmentations...
>> -----Original Message-----
>> From: Oliver Heger []
>> Sent: Tuesday, November 11, 2003 4:32 PM
>> To: Jakarta Commons Developer List
>> Subject: [configuration]More docs
>> Eric,
>> I am willing to produce some more docs about my changes. What is the
>> preferred way to do that? Changing the overview page? Of
>> course a native
>> speaker should review my results ;-)
>> Some other point: The last patch includes the feature that each
>> configuration object can be transformed in a XML document (or
>> at least
>> allows XML-like processing by firing SAXEvents) by using one of the
>> ConfigurationXMLReader classes. This is certainly something
>> that needs
>> to be documented in some more detail, too.
>> Do you think it would make sense to add a createXMLReader()
>> method (or
>> similar) to the Configuration interface? This method would be
>> implemented in the concrete classes by returning the proper
>> implementation of ConfigurationXMLReader. Then this feature could be
>> accessed directly through the interface.
>> Oli
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
>To unsubscribe, e-mail:
>For additional commands, e-mail:

This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message