• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

How do you see Seam and JSR 299 affecting EE6 and future versions of Java?

 
Author
Posts: 134
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Nice to have you here Michael Yuan & Jacob Orshalick. Obviously Seam and the new JSR 299 are making big waves in Java (some have put 299 in the same boat as what Spring has done for Java). What are you thoughts on how these two technologies are affecting Enterprise (and possibly SE) Java?
 
Author
Posts: 32
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Quite a loaded question, but I'll do my best to provide a succinct answer

Seam and JSR299 have taken huge strides in simplifying Java EE development especially within the context of web development. Many of the reasons people have strayed from the spec and flocked to frameworks like Spring are due to the complexities of developing applications using the standards. There were great improvements (many directly influenced by Spring and Hibernate) with EJB3 and JPA, but development of web applications has still been overly complex mainly due to the lack of a unified component model which these technologies directly address.

Java has been facing some serious competition from other technologies due to their simplicity and rapid development turnaround time. Seam and JSR299 have resolved many of the complaints surrounding Java EE development (especially in terms of a simplified programming model and rapid application development) and are bringing a lot of needed excitement back to the Java EE space. I'm a firm believer that by making it simple to develop an application using standard solutions we improve the Java community as a whole by creating a more competitive environment which in turn leads to greater innovation.
 
Jason Porter
Author
Posts: 134
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Great answer Jacob, thanks!
 
reply
    Bookmark Topic Watch Topic
  • New Topic