Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Kostis Kapelonis on Nov 16, 2011
The Apache Wicket project has released version 1.5 of its open source, component oriented Java web application framework. The major changes include:
The list of changes covers several other topics such as unified component rendering, caching, and RequestCycle hookups.
There are also number of other, more minor changes, which developers need to be aware of:
The artifact name has changed from the artifact name from wicket to wicket-core. Including Wicket in a Maven based project should therefore now follow the new artifact naming:
<dependency>
<groupId>org.apache.wicket</ groupId>
<artifactId>wicket-core</ artifactId>
<version>1.5.3</version>
</dependency>
Continuing with the upgrade to Java 5 from Wicket 1.4, this version now requires a servlet container that supports at least 2.5 of the servlet-api specification. All functionality that was marked as deprecated in Wicket 1.4 has been removed. Wicket also depends on Junit 4.x from now on (4.8.2).
Information on the type of a request parameter (GET or POST) is now available, as follows:
//GET request StringValue parameterValue = RequestCycle.get().getRequest().getQueryParameters(). getParameterValue( parameterName); // POST request StringValue parameterValue = RequestCycle.get().getRequest( ).getPostParameters(). getParameterValue( parameterName);
Finally XML property files have been renamed from .xml to .properties.xml for better description of their content.
After more than 2 years in development, the depth of changes in the Wicket internals prevents mixing the old and new versions of the framework together. If you wish to upgrade, all your wicket libraries should be upgraded to 1.5.x versions.
Whilst development of the 1.5.x releases is ongoing, framework developers are already discussing the roadmap for the next major release.
For more information, visit the Wiki, Reference documentation, and Javadocs. Bugs and problems can be reported on the Wicket issue tracker.
Introducing SQLFire: a memory-optimized, high performance SQL database
The WebSphere Liberty Profile for Developers: An Introduction
Early Access! Download JBoss Developer Studio 5.0 now, with packages for Mac, Windows or Linux!
App Server Evolution: REST, Cloud, and DevOps Support in Resin 4
VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
2 comments
Watch Thread Reply