Frank, Since this is the mailing-list for all things, technical and non-technical, related to Wicket, from *a Wicket application developers perspective* what are the main benefits of introducing the complexity of Seam to a project in terms of development/maintenance/extensibility/support etc into a Wicket web-app project (bijcetion/conversations ...?) as opposed to the benefits of using Wicket on Seam projects (which is presumably the chance to use Wicket and its great component model in place of JSF as the view technology ??). I notice that the webbeans spec ( http://jcp.org/en/jsr/detail?id=299 JSR 299 ) is coming along now - presumably this spec looks quite a lot like the Seam mission-statement. Again, what are the implications (and pros/cons/opportunities, if any) for Wicket based projects?
Regards - Cemal http://jWeekend.co.uk http://jWeekend.co.uk Frank Martínez-3 wrote: > > Hi All, > I committed the seam-integration module to the wicket-stuff repository. > And published the example application in my blog until i change it to > maven 2. > > I Will add more documentation soon. > > Any comments are appreciated. > > Thanks, > Frank. > > -- > Frank D. Martínez M. > Asimov Technologies Ltda. > Blog: http://www.ibstaff.net/fmartinez/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Wicket-Seam-Integration-tf4840640.html#a13897704 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
