> Does threads are very nice, but also very tangled to understand "What > is the actual situation of Wicket & Portlet vs Currently > Those-Techs-Users"! > > Would you mind breafing, at least, what should we do to secure-test > and run our Wicket-Portleted application? I mean, should we move to > Wicket-1.3? Stay at Wicket-1.2? Leave away to Struts??? > > Our inputs are (the versions we are using): > JDK: 1.4.2 > Wicket API & Extensions: 1.2.6 > WebApplication completely migrated to PortletApplication and packaged in a > WAR.
As you're on Wicket 1.2.6, use the portlet support that comes with that. For 1.3 and onwards, you should be able to run any Wicket applications/ pages just as a portlets without further fuzzing around. At least, that's what Ate has been promoting. Eelco ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
