Deep into Java JAXenter - Java Development & Software Architecture Java 7 You are here: Home / Java 7 This page lists the proposed features in Java 7 and information about them. At this point, no Java 7 JSR has been created (although Danny Coward apparently is working on it). Note: I have absolutely no inside information on any of this and you should treat it all as unofficial. The official JDK 7 Development Home page has mailing lists, downloads, source, and more. My most recent summary article on Java 7 can be found on JavaWorld. Features Java 7 Discussion Details Project Jigsaw Project Description: This project is intended to modularize the JDK itself by breaking it into . Blogs: JSR 294 Improved Modularity Support (superpackages) JSR | Early Draft Review | Mailing list Description: This JSR is related to JSR 277. 277 deals with deployment and packaging. 294 focuses more on API modularity at development time. Example: superpackage example.bar.lib { // member packages member package example.bar.lib; // list of exported types export example.bar.lib.Table; Java Kernel Wiki
SOAP vs REST in the service layer for mobile applications With the surge in native mobile applications and the advent of players like Android, IPhone, Palm and other big players into this market, providing frameworks to develop applications native to the device, it is important for developers to understand performance implications for every operation that the application is going to perform. The service layer has always been a most important factor for any enterprise as that is where they have put all their money in. During the last ten years, organizations have made significant investments in SOAP-based infrastructure such as Enterprise Service Buses (ESBs) and Business Process Management (BPM) software based on WS-BPEL. The SOAP binding will allow organizations to leverage those investments in building interoperable content repositories. Within the enterprise and in B2B scenarios, SOAP is still very attractive. This is not to say that REST is not enterprise ready. Verdict: SOAP Verdict: ReST Verdict: SOAP/ReST Who uses ReST? Who uses SOAP?
The Coder's Breakfast AggregateOrientedDatabase database ยท noSQL tags: One of the first topics to spring to mind as we worked on Nosql Distilled was that NoSQL databases use different data models than the relational model. Most sources I've looked at mention at least four groups of data model: key-value, document, column-family, and graph. The rise of NoSQL databases has been driven primarily by the desire to store data effectively on large clusters - such as the setups used by Google and Amazon. An aggregate also makes a lot of sense to an application programmer. An aggregate makes for a much simpler mapping - which is why many early adopters of NoSQL databases report that it's an easier programming model. This synergy between the programming model and the distribution model is very valuable. There is a significant downside - the whole approach works really well when data access is aligned with the aggregates, but what if you want to look at the data in a different way?
JH Labs Java Stuff