> some here like it and others dont like it, so wouldnt be an different > project like wicket-extension the part for this?
That's what I'm arguing. Though thinking about it a little bit longer, it should probably not even be a core project, but rather a wicket-stuff one. > couldn't this be > applied similar to the wicket-jmx plugin where you just dump the jar > into the classpath and have it registering and enabling itself? That would be ok only if it would apply to a whole different set of tags. Which is probably the best way to go about this anyway. Is there anything in anyone's way to implement this right now as a separate bunch of tags? Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
