Carl-Eric and Martin are right, Wicket just stays out of the way with respect to other frameworks. It's literally just the presentation engine and does an awesome job at it.
If you want something that is automatic in this regard, you might want to take a look at Brix (http://brixcms.org). Instead of pages being stored on the classpath, they are stored in a document-oriented database service, the interfaces to which (JCR) are used by over a dozen large-scale content management systems. In this way, your pages are easily modifiable by content authors without rebuilding the WAR, and it's also easier for Lucene to automatically index the content as it's changed. Your content database must obviously be maintained with as much integrity as your transactional database and there are some additional configurations required for components, but otherwise it's just a regular Wicket application. HTH, Brian On Jul 16, 2011, at 6:58 AM, Carl-Eric Menzel wrote: > On Sat, 16 Jul 2011 03:41:19 -0700 (PDT) > hariharansrc <[email protected]> wrote: > >> can anyone suggest the best search engine framework for wicket > > Wicket doesn't really care what other frameworks you use beside it. > Wicket does nothing but the UI layer, and for everything else you can > use whatever you want. Use Hibernate or IBatis or JPA or whatever for > your DB access. Use Spring or Guice or whatever for your wiring. Use > Hibernate Search or Lucene or whatever for your searching. > > Carl-Eric > www.wicketbuch.de > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
