(How can one believe that it is possible to configure a whole enterprise from one file?)
The critique only means, that Jboss needs a configuration GUI (or at least some command line tool like j2eeadmin). Sun's intention was from the start, that nobody is going to look at the config files themselves. In this way you can design the config files as required by technology. Otherwise you keep running into the conflict between readability/ease of use for humans and usability from the software's perspective. Jboss is a really great product with many features I could not do without. But I cannot understand why the Jboss developers keep badmouthing gui-based solutions. (Don't get me wrong: I am not one of those, who have never seen a command line, just the opposite. VI and the command line have their limitations, though). I predict, that within the next year there will be Jboss-(G)UI, simply driven by public demand. (Look at the Veritas Volume Manager's Java/Swing GUI. Something like that would be great). Regards Georg -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Juha-P Lindfors Sent: Friday, April 26, 2002 08:05 To: [EMAIL PROTECTED] Subject: [JBoss-dev] [JL] Is it time for a new enterprise solution? Critique on JBoss configuration. http://www.javalobby.org/thread.jsp?forum=61&thread=3254 -- Juha _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
