On the other hand, it's true that developers selected the Spring Framework, standards be damned, well before their managers or CIOs knew or had a say. Some subset of these developers are likely to try deploying their Spring applications on GAE/J simply to see what works and what doesn't. Of these developers, some will be able to convince their management that GAE/J represents a lower-cost deployment environment than the traditional data center for Java applications. The application's business criticality and, more important, the sensitivity of data required or generated by the application will have an impact on whether an enterprise IT decision maker will approve a GAE/J deployment.
Using GAE/J for development and testing, with the actual production deployment not on GAE/J, is another potential use case for Spring with GAE/J. For its part, VMware is positioning the Spring Framework as a path toward portable Java in "any" cloud platform, as my colleague Neil McAllister has written.
Where does your company fit on the de facto versus open standards spectrum? Will you give GAE/J another look now that Spring applications are supported?
This article, "VMware's role in Spring Framework could drive developers away," was originally published at InfoWorld.com. Read more of Rodrigues et al.'s Open Sources blog and follow the latest developments in open source and cloud computing at InfoWorld.com.