> One part that I just can't seem to figure out from reading Pro Wicket and > browsing through the apidocs is how to > make something like Tapestry "services".
Contrary to what some people say on The Server Side etc, Wicket and Tapestry are very different frameworks. This means that not everything can be mapped from one framework to the other. Tapestry's services seem to be pretty particular for that framework. The best way to go here is to forget about the facilities you had in Tapestry, but just focus on what you want to accomplish. It will be easier for us to help you out with specific use cases, or you might be able to figure it out yourself. FYI, I think we had a very short discussion on whether we should have the concept of services some 2 years ago, but if I remember correctly we decided against it as we thought it would distract from thinking in components. That was then though, and it is never to late to hear some compelling arguments ;) Eelco ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
