On 06 Sep 2007 18:32:44 +0200 (CEST), Robo <[EMAIL PROTECTED]> wrote: > Yes I know Eelco. That is why there are so much troubles in Java programming > land. Misusing of basic concepts ... That is why one needs some sort of COC, > because there is lot`s of b.s. around ... J2EE 1.4 countained so much of it > that lots of developers refused to use it And it had to be rewriten ... > Apache Struts ... JSF ... Why did you started Wicket? Did`nt you wrote that > MVC is kind of missconceptin? And I ask you Who told that? Eelco Hilenius? > Yes and you were probably right. And in that time you with the tapestry was > alone against the JSF Struts community. So accpet pleace that someone else is > seeing miisconceptions and b.s. in other aspetcs of java programming and > habits. OK? :-)
Sure. You know, if you would just try to have a little bit more of a constructive tone... I'm sure we can patch wicket-velocity so that it avoids pulling in Velocity too early. And maybe the project tries to do too much upfront. Should be pretty easy to fix if you want to create a JIRA issue for it. About calling initializers (that's what triggers Velocity loading in this case), the feature is generally nice. We can use it to e.g. automatically register shared resources or like wicket-jmx does, register resources, so that to enable functionality in that lib is as easy as dropping in a jar. That's pretty cool functionality in my book. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
