Michiel Meeuwissen wrote:
But I think we need a default editor, that's useable for a normal simple user. We can't afford to have to tell users, sorry, but the default editors aren't working for you, you have to use the other editors, or write some editwizards or turn scan back on.......Johannes Verelst <[EMAIL PROTECTED]> wrote:On Tue, 2002-10-22 at 11:09, Pierre van Rooden wrote:I agree it is a vague phrase, but let's define it as being free fromJohannes Verelst wrote:Can you specify how you like to determine production quality (asside from being bug-free)?I vote [+1] if and only if the JSP editors are production-quality for all supported application servers, and it doesn't negatively affect the time-schedule for the upcoming 1.6 release. Otherwise, I vote [-1].
bugs and performing reasonably.
I know that Tomcat 4.0 has performance problems with taglibs, but that is a Tomcat problem (it will not dissapear with another MMBase release).
Tomcat 4.1 performes much better from what I hear.
If we would drop 4.0 from the supported-appserver list, then there might indeed not be a problem. Unfortunately, 4.0 needs to be supported in 1.6 as noted in the thread following the 1.6 release call.As I pointed out earlier. The jsp-editors are only _a_ way to edit your data. It is still possible to turn scan on, use other jsp-editors or even editwizard, and if only that would prove to be necessary to use tomcat 4.0, it still could be with some right called 'supported'.
Gerard
