I agree that this is an important feature that usually gets put on the back burner. It is
especially important for application configuration files because the documentation
on those files is usually weak and it's very difficult to find out what can go in a config file.


I think using the java.beans.XMLEncoder would be a great way to create the configuration
files. It would be very easy for an administration application and the j2ee server to stay in synch. Plus, ALL configuration options can be easily documented using Javadocs.


Mike

At 08:30 AM 8/8/2003 -0700, Chris Opacki wrote:
I could help out with this as well.

--- Erin Mulder <[EMAIL PROTECTED]> wrote:
> I'd like to see a subgroup dedicated to the overall
> user experience
> and would be happy to help out in that area.
>
> In particular:
>
> 0) A user web site that draws people in and makes it
> easy to get started
>
> 1) Friendly, comprehensive and -free- user
> documentation
> 2) Working examples of all J2EE and value-added
> features
> 3) An attractive web console that competes favorably
> with WebLogic/Websphere
> 4) Good command line tools for easy scripting
> 5) Lots of attention to the developer experience,
> e.g.:
>         - up-to-date DTDs with useful comments
>         - robust hot deploy
>         - useful error messages
>         - preservation of line numbering where
> possible for EJBs/JSPs
>
> Cheers,
> Erin Mulder
>


__________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com




Reply via email to