Follow Us on Twitter

Devoxx 2009 – day 3

by Jos Nieuwenhuis on November 19, 2009 · 0 comments

Many sessions on the third day of Devoxx were about the new Java EE release.

Antonio Goncalves: Java EE 6 release

Java EE 6 will be released on December 10th 2009. It will contain many improvements:

  • JAX-RS – Annotation based API for REST web services. Very simple to use, just add the following annotations: @Path, @GET, @POST, etc.
  • BeanValidation – Also annotation based; similar to the annotations in Rails/Grails: @NotNull, @Size (max=40, message=”longer than {max} characters”). It is possible to add your own custom tags. The tags work with JPA and JSF.
  • Web Profile 1.0 – This is a subset of Java EE APIs only for webcontainer. Includes EJB Lite: a way to run EJBs in a web container.
  • CDI – Context Dependency Injection. Annotations to be used: @Inject, @Resource.
  • EJB 3.1 – A new component has been added: Singleton. It is now possible to make a method asynchronous using the annotation @Asynchronous.
  • Embedded Container – EJB Container to be used in Java SE for test purposes.
  • Portable JNDI Names – Naming rules are not vendor specific anymore.
  • Servlet 3.0 – Many improvements. The file web.xml is now optional. Instead annotations like @WebServlet and @WebFilter can be used.
  • Simplified packaging – For example, EJBs do not have to be in separate jar anymore.
  • etcetera.

I think Java EE 6 has some really great features. Java EE 6 is a huge improvement over Java EE 5.

Scott Ambler: Agile Mythbusters

Based on facts Scott Ambler makes some conclusions about what Agile people are really doing in practice. According to him:

  • Agile is not just for small teams.
  • Only 47% of all Agile teams practice TDD (Test Driven Development). (This is strange. Isn’t it a requirement to do TDD?)
  • Only 65% of all Agile teams do continuous integration.
  • Agile teams do not just start coding from the beginning of the project. On average it takes 4 weeks before they start programming.
  • Agile teams do not follow common development guidelines. Applying common guidelines can be a quick win to increase software quality.
  • Agile works really works better than traditional approaches. “Agile teams produce higher quality work, are quicker to deliver, are more likely to deliver the right functionality and likely to produce greater ROI than traditional teams.”

Interesting results?

Chris Richardson: Architecting Robust Applications for Amazon EC2

Amazon’s EC2 (Elastic Compute Cloud) is a virtualized computing environment which offers a way access computing resources via a web services API. Developing Java applications seems easy since it allows you to develop applications using standard software packages such as Tomcat and MySQL. However, some aspects of EC2 are very different than a physical computing environment. For example, you don’t know where your data is. A big advantage is that you are not responsible for the hardware. It is very easy to add and remove server instances.

Christophe Herreman: Spring ActionScript

Spring ActionScript is brings Independency Injection to the Flash Platform. The main focus is on Flex and AIR development. This framework can be used to build testable and maintainable Flex applications. The code examples looked quite clean. Maybe worth a try.

Gregor Hohpe: Distributed programming the Google way

Google runs one of the largest computer infrastructures in the world. Parts of this infrastructure have been made available as open source projects. Some design themes or patterns can be used in other contexts. Gregor Hohpe’s 8 rules:

  1. Use sharding. Partition your data.
  2. Less is more. Choose only the basic features.
  3. Expect failure. It is not a matter if, but when the failure will strike.
  4. Autonomy. Some processes should be able to continue without supervision.
  5. Empower the runtime. Flow freely instead of strict rules.
  6. Favor Stateless. Processes that keep state are more expensive than stateless operations.
  7. Precision versus Speed. Faster is better.
  8. It is all about trade-offs.

Interesting ideas. Some of them can also be useful for smaller scale projects.

Ratings:
VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

{ 0 comments… add one now }

Leave a Comment

 

Previous post:

Next post:

About Whitehorses
Company profile
Services
Technology

Whitehorses website

Home page
Whitebooks
Jobs

Follow us
Blog post RSS
Comment RSS
Twitter