Hi Kent: Thank you for your kind comments! It's nice to see several months of work be useful to others.
I've heard the "why not Java instead of beanprops" comment before. I may even do something about it ;-). Seriously, that may be offered as an alternative to the beanprops file. I chose the beanprops file for simplicity. It is declarative rather than procedural (e.g., Java). I believe that the exceptions can be specified in a more concise form than if they were to be written in Java. Plus, WWB contexts/use cases can override the default context by just specifying what's different. In fact, that's the whole WWB philosophy - programming by exception. I guess it similar to why you don't specify localization in Java - you use property files. It also why in Wicket you don't code HTML tags in Java to be output to the browser - HTML itself is more concise and direct. I actually worked with an in-house web framework that made you code the HTML tags in Java. No HTML, no JSP, just Java. It wasn't pretty ;-). -Dan Syrstad http://wicketwebbeans.sourceforge.com On 9/12/07, Kent Tong <[EMAIL PROTECTED]> wrote: > > > Hi Dan, > > It looks very powerful! BTW, why chose to use a config file (beanprops) > instead of Java code? > I think doing in Java for everything other than the standard web stuff > (HTML/CSS/js) is a > basic principle of Wicket. > > -- > View this message in context: > http://www.nabble.com/Re%3A-Wicket-Web-Beans-1.0-rc1-Released-tf4431603.html#a12647439 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
