It is a good choice to use JSP with Wicket at long term? There is also another tool that allows to work with Wicket?
Thanks
+3
A:
This is a strange question. Wicket does not work with JSPs. JSPs work with action-oriented web frameworks (e.g. Struts or Spring MVC) or pure servlet development, Wicket is a component oriented framework which works with html and java only. There is no logic in templates in wicket (and hence no suport for JSPs). In my opinion that is the key feature of wicket.
seanizer
2010-10-24 19:22:28
@seanizer There are some articles about this (eg http://herebebeasties.com/2007-03-01/jsp-and-wicket-sitting-in-a-tree). But I'm not convinced if this is a good choice.
adelarsq
2010-10-24 20:09:20
@adelarsq IMHO it's an awful choice. Wicket's design is meant to avoid JSP hell, not incorporate it (although it's obviously possible to do it: wicket is plain java and as such cann call all other plain java technologies, including JSP)
seanizer
2010-10-24 20:21:19
@seanizer To know that this is a bad practice also answers my question. Thanks
adelarsq
2010-10-24 21:58:57
+1: While it is possible to use Wicket and JSP in the same app, I'd consider it only as a transition state while converting a JSP app to a Wicket one. And I'd never go the other way...
Don Roby
2010-10-25 11:41:22
Agreed. The clean HTML you get when using Wicket is a breath of fresh air compared to some JSP projects I've seen.
Jonik
2010-10-26 10:19:32