<dependency> <groupId>javax</groupId> <artifactId>javaee-api</artifactId> <version>7.0</version> </dependency>
Further details here for specific EE7 technologies.
Previous post for Glassfish snapshot dependencies.
Articles, notes and random thoughts on Software Development and Technology
I find this somewhat hard to believe. 12 years ago, legal action by Sun Microsystems against Microsoft halted Microsoft’s development of their own flavor of Java, which was only partially compatible with Sun’s Test Computability Kit (TCK). In order to develop an implementation of Java and compatible JVM, the license requires the developed product to pass the TCK in order to maintain cross platform compatibility of different implementations of Java.
This week Microsoft announced that it has added support to host Oracle Weblogic and Oracle databases on it’s Azure cloud, allowing developers to host Java based solutions on Microsoft’s hosted platform.
How times have changed 🙂
Oracle are hosting live webcasts for the launch of EE7 on June 12 & 13 next week – more info here.
If you have an older Spring Roo project created from Spring Roo 1.1.x and you’re trying to imported it to a more recent STS version and/or trying to upgrade to a later 1.2.x version of Spring Roo, you may be seeing these errors:
RooEntity cannot be resolved to a type
@RooEntity was replaced in Spring Roo 1.2.x with @RooJpaActiveRecord. Replace this in all your Entity classes and you should be good to go.
This is discussed in this thread.
@RooJpaActiveRecord is covered in the docs here.