Early reports say yes: http://www.businessinsider.com/google-now-better-than-siri-2012-7
Rod Johnson, founder of the Spring Framework, leaves VMWare/SpringSource
When Rod Johnson started the Spring Framework back in the early 2000s, he showed J2EE developers that there are better ways to build enterprise Java apps, and he provided the framework to help you do it. Anyone having experienced the pain of developing EJB 2.x beans during this time with it’s clunky api and verbose deployment descriptors and then since worked with the Spring Framework can attest to the huge benefits of developing apps using Spring’s much simpler, lightweight approach. Spring’s success has arguably been a significant influence on the ‘ease of use’ focus for the simplifications and improvements made in EE5 and EE6 in recent years.
Rod recently announced that he’s leaving VMWare to pursue other interests – I wish him success in his future endeavors and thanks for the impact you’ve made to enterprise Java development in the past 10+ years.
Presenting at Red Hat Summit 2012 next week: Accenture & Red Hat collaboration to grow OpenShift skills
I’m presenting at the Red Hat Summit 2012 conference next week, Thursday June 28th @ 2:30pm at Campground 1 – I’m going to be talking about some work we recently did at Accenture in collaboration with Red Hat to grow OpenShift skills at Accenture.
Here’s the details of the session from the link above:
Growing OpenShift Skills within Accenture: The J-Prize Coding Contest
June 15th, 2012
by Accenture team
In Spring 2012, Accenture collaborated with Red Hat to run the “J-Prize Coding Contest” for Accenture Java developers. The focus of the contest was to design and develop a Java application and deploy it to OpenShift, Red Hat’s Platform as a Service (PaaS) offering.
“Cloud-related technologies are rapidly maturing and are increasingly being used by our clients to deliver real value,” said Kevin Hooke, Manager, Open Source Initiatives Lead for the Accenture Java Development Program. “The contest helped us grow our Java developers’ knowledge and experience with building and deploying applications to the cloud using PaaS offerings such as OpenShift.”
To learn more, attend the Red Hat campground session hosted by Kevin where he will discuss the success of the contest, the benefits gained for Accenture, and he will showcase the four winning applications.
Thursday, July 28 @ 2:30pm: Campground 1 (Room 301, Hynes)
Location of JPA persistence.xml to auto find entities
I’m working on some example code to show different configuration options and approaches for using Hibernate with JPA. I just noticed that the location of the /META-INF/persistence.xml file is critical to allow Hibernate to auto-locate your annotated entities.
In order for the auto location to work (to avoid having to explicitly list annotated entities in your persistence.xml or hibernate.cfg.xml files), the persistence.xml file must be bundled in the same jar as the entities. If you move the file elsewhere, then the entities are not found, even if they are in the classpath. To workaround this, if you do need to put the persistence.xml file in a different location, use the <mapping> element to explicitly declare the entities.