In yesterday's blog entry I wondered aloud why a Wicket user would want to use a 'heavy' application server like Glassfish. Partly my answer was provided in the comments to that blog entry?there Davy De Durpel writes that he's been happily using EJB for persistence with Wicket over Glassfish. Personally, I'm a lot more comfortable with web services than with EJBs (although, now that EJBs are going to be incredibly simplified, maybe I should give them a chance). So, I reimplemented this NetBeans tutorial, replacing JAX-RPC with JAX-WS and servlets/JSPs with Wicket's Java classes and HTML files. And here's the result?a Wicket application that consumes CDYNE's SpellChecker web service:
Post comment (0)