Remy Maucherat wrote: > Costin Manolache wrote: >> Remy Maucherat wrote: >> >> >> >>>>No, just return HTML in the first place. >>> >>>Feel free to revert to the previous version. >>> >>>-1 from me for server side XSL (we're doing a monitor servlet, not a >>>bring-ther-server-to-its-knees monitor servlet). >>> >>> >>>>I just don't understand - when you can just display HTML, why do you >>>>want to go through XML and then XSLT ??? >>> >>>Don't ask me. You didn't reply, and I didn't care, so I applied the >>>patch (partially) ;-) >> >> >> I couldn't reply - it didn't work for me :-) I just got it to work today. >> I was working with the "embed" version, with no "servlet-XXX.jar". >> >> BTW - is there anything specific to tomcat5 in this app ? From what I >> see, it should work with 1.4 just fine ( well, except that it won't load >> if o.a.catalina package is used without backporting the fix from >> ServletWrapper ) > > Let's say the servlet doesn't have any obvious couplings with 5.0. > However, it needs the updated modeler (without introspection, it won't > work), as well as the JMX enabled Coyote. > > I don't want to port back that right now.
No need to back port it. I was just thinking that the manager and most of the other webapps are now relatively independent of the tomcat internals - and with JMX they can have almost no direct dependency ( except the naming scheme and semantics, of course ). Even webdav - it shouldn't be hard to either replace it with slide or make it depend only on JNDI ( and get the JNDI context via JMX ). Don't worry - I'm not going to touch any of those until the core is stable. The low coupling and relatively independent components are very good. Costin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
