X

NetBeans Podcast Episode #22 - Seam Framework

Guest Author



Episode #22 is special because it is all about one framework: Seam. I was joined by Brian Leonard to discuss the advantages of using this framework, how does it fit with the rest of Java EE, what kinds of problems it solves, if it's ready for commercial use and so forth.


NetBeans Podcast Episode #22 (27 min 28 sec, size: 19.7 MB)



Links:


Unfortunately I can't find the picture with ice fountain in Las Vegas...



Podcast feedback to: roman dot strobl at sun dot com.



To subscribe via iTunes or similar players, visit http://feeds.feedburner.com/netbeanspod.

Join the discussion

Comments ( 5 )
  • Ove Nordstrom Friday, January 19, 2007
    Really nice information about Seam!!!!!
    Thanks very much!!
    -ove
  • Roumen Friday, January 19, 2007
    You're welcome!
  • Karsten Silz Tuesday, January 23, 2007
    I think the podcast was pretty good - although biased towards JEE, but then again, this is a Sun Netbeans podcast, so that's ok.
    One of the unanswered questions in the podcast was where Seam will go next - Gavin King explains it here: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2006/12/14#roadmap I'm really excited about Spring integration because for the kind of projects I work on, I prefer the rather agile Spring + Tomcat over the full and rather slow moving JEE container (but hey, after 6.5 years persistence in JEE went from "plain broken" to "decent Hibernate copy and therefore usable" ;-). And as Roumen already suspected, tooling will probably show up first on Eclipse - as part of the Hibernate tools from JBoss. ;-)
  • Roumen Wednesday, January 24, 2007
    Next week we are organizing a presentation about Spring in Prague with my friend from HP at CZJUG. Wanna come? :)
  • Karsten Silz Wednesday, January 24, 2007
    Sorry, I can't - I'm located in Berlin. But the Spring documentation is pretty good... :-)
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.