> > I subclassed org.apache.ecs.html.Html > > with my very own WML element, and output the > > mandatory header in a subclass of Layout. > > Gag. What is wrong with just defining your own Layout? Nothing wrong with defining my own Layout, but I don't like subclassing the org.apache.ecs.html.Html element with a my.package.Wml element. What I was pointing out was that org.apache.ecs.Document is output, with <html></html> tags, no matter what I do, and the subclassing was the only way I found to suppress it. > > ... the ability to specify a Login Screen in the request ... > > -1...this isn't needed you can code around these issues without > problems by defining your own Layout. > Correct, me stupid. > > don't hack things, but instead either replace the functionality by > overriding the existing default behavior of it. > OK, but what is a clean way of bypassing org.apache.ecs.Document completely, so that I can avoid the html-ness of that class, and do all the wml construction myself? ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/> Problems?: [EMAIL PROTECTED]
