For Red Hat, SwitchYard is the new ESB. Project SwitchYard is a significant, and arguably well-needed, retooling of the JBoss ESB. "JBoss ESB 4 is the existing ESB. SwitchYard is essentially JBoss ESB 5," says SwitchYard project leader Keith Babo. What will this new change mean for upcoming versions of the JBoss SOA Platform?
As observed in my earlier articles, the Java EE PaaS portfolio is gaining in strength each day, with support from major players such as IBM, Oracle, VMWare, Redhat , Google and Amazon. However unlike the Microsoft > .NET Framework > Azure PaaS equation where there is just one version of the framework from one vendor, the openness of Java EE led to several implementations of application server-specific implementations. As Java EE standards define a core set of API, frame works and features as part of its implementation, an application server is the container that executes these instructions and provides a development and runtime platform for Java EE applications.
Charlie Hunt explains what can be done to lower the latency introduced by the Java GC and JIT, including coding tips, and introducing tools for tuning the performance of Java applications. By Charlie Hunt
Rust is a systems programming language developed by Mozilla and targeted at high performance applications. This post contains an interview with Graydon Hoare, Rust's creator. By Abel Avram
Robert Winch explains how to secure a multi-tenant application with Spring Security and how to enable OAuth 2. By Robert Winch
This article provides a deep dive into various core Java collections and some core factors to consider while choosing your right collection class.
Rich Hickey and Justin Sheehy talk about scalability and transactionability of datastores. They explain tradeoffs for achieving read and/or write scalability on top of Datomic and Riak. By Rich Hickey and Justin Sheehy
The latest Android distribution stats from Google will do little to fan the flames from ardent fragmentation critics, with Ice Cream Sandwich numbers still flagging. They’ll probably try to pass it off as differentiation, but the figures are telling. Android 2.3, aka Gingerbread, still holds the lion’s share, running on 60.6% of total Android-running devices. Quite a lot further down the line, we have Ice Cream Sandwich with 15.9%. Although technically gaining some ground - this figure rising 5% in the past month - it’s nowhere near the level Google envisaged almost a year on from releasing the version. It had high hopes, but seemingly not enough manufacturers are placing their faith in version. So does the blame lie ? Google, for making it hard for mobile makers to upgrade to the latest flashy version, consequently delaying upgrades for customers? Or with handset manufacturers for just not showing enough interest? When you know there’s an update just round the corner, why bother with the effort? Jelly Bean, unveiled at the recent Google I/O developer conference, has amassed just 0.8% so far, though to be fair it’s only available to run on a few select smartphones like the Galaxy Nexus and tablet like Nexus 7. While only a minor update from ICS, this is much more encouraging to see after a short amount of time. Again, this raises the question, why both with ICS when Jelly Bean is here? Contrast this with the walled garden world of Apple, where they recently revealed at their Worldwide Developers Conference in June that 80% of their devices ran the latest iOS 5, and the disadvantages of Google’s open policy become clear. Android is in a rut - at least in attaining the numbers they want from Ice Cream Sandwich. New features are being developed, but not seen. Malware is becoming ever more rampant, despite best efforts. They clearly need to exert some pressure on mobile manufacturers to update archaic Android versions present on their phones, if developing for Android is going to continue to be lucrative. On a positive sidenote for Ice Cream Sandwich - the Razrdroid project, part of the Raspberry Pi foundation, have got the credit card sized computer to run Android 4.0, bar some sound barriers. We’ll be interested to see what this leads to. Although no code is available just yet, check out the soundless video below to see it in action.
I have spent the last 6 months on a project where Clojure was the main technology in use. I can't really say much about the project itself, except that it's a fairly complicated thing with lots of analytics and different kinds of data involved. We ended up with an environment that had a lot of Ruby and JavaScript/CoffeeScript as well as Clojure. We are using Neo4J for most of our data...
There appears to be a misconception that annotations are required on the model in order to use a JAXB (JSR-222) implementation. The truth is that JAXB is configuration by exception, so annotations are only required when you want to override default behaviour. In this example I'll demonstrate how to use JAXB without providing any metadata. Preview Text: ...
How much of category theory knowledge should a working programmer have ? I guess this depends on what kind of language the programmer uses in his daily life. Given the proliferation of functional languages today, specifically typed functional languages (Haskell, Scala etc.) that embeds the typed lambda calculus in some form or the other, the question looks relevant to me. Preview...
Who expected that to happen: Oracle is working on a public cloud offering and the signs of the approaching official launch are there. Nearly a year after the Preview Text: Wanna get started with OPC? Go pick up NetBeans 7.2RC1 Java EE, and then head back to this post for a step-by-step guide. Legacy Sponsored: ...
In java, writing equals and hashcode methods are perennial problems. Newbies and experts alike are confounded when things go haywire and troubleshooting problems can be extremely difficult. A common thing that a poor hashcode/equals implementation will cause are intermittent problems and/or mysterious out of memory errors. To help clear things up, I'll give a 10,000...
Yesterday we were working on setting up our first Hadoop cluster. Though there are many online documentation on this even then we faced a few challenges getting with it. In this post I am providing details on the faced problems and solutions: Passwordless login from NameNode to DataNode and vice versa: Though setting paswordless login from NameNode to DataNode was easy. We had to just follow...