There is one con with embedding HTML within jars: if you're not using an exploded deployment, you have to redeploy in order to make changes in HTML. For larger project, this can be a waste of time. However, exploded deployments should negate this drawback.
On 7/30/07, Gwyn Evans <[EMAIL PROTECTED]> wrote: > > On Monday, July 30, 2007, 8:02:29 PM, Sean <[EMAIL PROTECTED]> wrote: > > > Matt Raible gave a presentation at OSCON last week. The topic was > > "Comparing Java Web Frameworks". > > Wicket is one of the frameworks in the comparison. Matt's slides are > online > > at: > > http://raibledesigns.com/rd/entry/oscon_2007_comparing_java_web > > Certainly worth looking at, but note that like many (all?) > comparisons, it has a certain number of personal view-points built in. > > For instance, Matt says "Wicket's EL in templates is very limited and > doesn't allow calling methods with parameters, nor doing conditional > logic". We agree on that, it's just that while he sees it as a negative > point, the Wicket 'team's view is that that's one of the positive > features of Wicket! :-) > > In the same way, we differ regarding the default placing of HTML next > to the Java code - certainly initially that feels strange, but as > people explore what can be done with Wicket, e.g. with regards to > creating and reusing components, etc, the advantages of the default > approach become clearer. > > /Gwyn > >
