Run Java Applications on Amazon EC2
My book
My RSS Feeds
I am the founder of Cloud Foundry, which provides automated, outsourced data center management for Java applications on Amazon EC2.
I am the founder of Cloud Tools, which is an open-source project for automating the deployment of Java and Grails applications on Amazon EC2.
I run a training and consulting company that helps organizations build better software faster and deploy it on the cloud.
We provide a variety of services including:
- Development - we can build your application for you
- Deployment - we can find a hosting partner or deploy your application on Amazon EC2
- Training classes for Spring, Hibernate and Acegi Security
- Jumpstarts to get your project off to the right start
- Reviews to improve your architecture, code and development process
For more information contact me.
What Can You Do With EJB3?
What You Can Do With EJB3 (part one)
As this article shows EJB 3.0 is definitely a major improvement over EJB 2.x. In particular the support for dependency injection is particularly valuable but does it extend to non-EJB classes?
I stopped writing monolithic session beans a long time ago. I would, for example, want to move the query to find the items into a repository class (see domain-driven design), e.g. ItemRepository.getItemSummaries() . The session bean would then be configured with the repository through dependency injection. I would also want to configure the ItemRepository with the EntityManager through dependency injection. I can do this today with JDO/Hibernate and Spring/PicoContainer. Can I do this with EJB 3.0?
Also, what about being able to test the persistent classes outside of the container as you can today with JDO or Hibernate? e.g with test cases that use Hsqldb and DbUnit?