Earlier this year I asked you to start thinking about attending and perhaps even speaking at AWS re:Invent, our first global customer and partner conference. The conference will be held from November 27-29 at the Venetian Hotel in Las Vegas....

Mark Reinhold has announced on his blog that the Java Jigsaw modularity proposal has been moved from inclusion in Java SE 8 and deferred into Java SE 9. This will allow Java SE 8 to be released on schedule in August 2013, whilst the modularity proposal can be refined with wider visibility for inclusion in August 2015's Java SE 9 release. By Alex Blewitt

The Amazon Simple Email Service (SES) gives you the power to send bulk and transactional emails, with a focus on ease of use and deliverability. After you sign up for Amazon SES, you simply verify your domain, request production access,...

A blog today by Mark Reinhold, the OpenJDK project lead at Oracle, might have come as a shock to many in the Java community: It looks like Project Jigsaw (a standard module system for Java SE) is lagging behind in development and probably won't make it into the Java 8 release next summer. Preview Text: For a while OpenJDK has had a prototype...

This video discusses the options for managing and monitoring applications that use Spring Integration. Topics covered include: using the Spring Integration plugin for Spring Insight to get a real-time view of your applications and its performance using the Integration MBean Exporter and the MBeans it registers for analyzing messaging endpoints and channels exporting the Integration MBean Exporter itself as an MBean, to gain access to its attributes and operations using the <control-bus /> to start and stop endpoints enabling and using Message History previewing the orderly shutdown mechanisms being built into Spring Integration 2.2 Be sure to thumbs up the presentation if you find it useful and subscribe to the SpringSourceDev channel to see other recordings and screencasts.

In this article I will provide you an effective and optimized approach of Factory Design Pattern in Java. As you know theFactory Method Pattern or popularly known as the Factory Design Pattern is one the design patterns under the category of "Creational Design Pattern". The basic principle behind the pattern is that at run time we get an object of similar type based upon the parameter we pass. There are many articles on this pattern and developers implement in various ways to achieve it. In this article I will show you how to create a better and most effective way of designing factory design pattern.

This article gives you an inner insight into the design of a better singleton design pattern. In this article you will be able to learn how break a singleton design if it not designed properly. It will help you to follow the best practices adopted in the industry. A few days ago when I was in my home town, one of my sub-juniors from my colleague attended an interview in an MNC and was severely injured in that interview process. I mean he could not qualify the interview because of the difficult questions fired by the interview panel. When I came back to Bangalore, he sharedthe embarrassing situation he confronted during the technical interview. Based upon his experience today I am writing this article on the Singleton Design Pattern. By the way my junior colleague has nearly four years of experience in Java. One of the controversial questions he faced was "What is the Singleton Design Pattern and how will you write a robust singleton class? " However let me give you the basic and critical outlines of the Singleton Design Pattern frequently used at the time of project/product development.

TBD - Floyd By Abel Avram

Dave Ray introduces Seesaw, a user interface toolkit for Clojure built on top of Java Swing unifying various abstractions found in the Swing API for a more pleasant UI development. By Dave Ray

It can't have escaped your attention that the Subversion is old hat. Granted, it still has its uses, especially for older systems reliant upon that repository, but this is the year of Git. The new(er) kid on the block is capturing much more attention for its rethinking of software version control. The most high profile, or at least most talked about across Java in any case, is Eclipse's December deadline for all projects within the community to move across to the distributed control system. This shift of power has been talked about for some time (just by checking when the first 'Svn to Git' blogpost appeared, you can see how long), but only in the last 12 months have we seen a large number of enterprises make the switch, according to numerous surveys. Many larger enterprises face being left out in the cold if they don't follow suit, but with so much effort required to move hefty repositories, is it really worth the effort them? Or more importantly the outlay that comes with transferring. Fortunately, a new project has shored up offering the best of both worlds. SubGit is, as you would expect, a bridge between the two repositories. The software installs on the server side, holding two synchronised repositories for both Git and Subversion. So, when a user makes a change in one repository, this is automatically replicated in the other. And again, this idea isn't new either, SubGit was created as an alternative to Git-Svn but this time round, SubGit aims to become a guiding path for migration to Git in the longrun, by teaching the user the merits of Git. It also holds advantages over its competitor: rather than having every developer in your team learn the intracicies of migrating, SubGit gives power to the system adminstrator, who installs and configures. The rest learn Git at their own pace. Some might take to it like a duck to water, others might rely on Subversion as support - the learning curve is entirely set by the user. The convoluted process with Git-Svn is gone, with Git commits being pushed the Git repository, which are then translated to Subversion asynchronously when needed. Another benefit is the freedom of tools on offer, as you can use any tool you like, either integrate into the IDE or as standalone. Having just unleashed a first release candidate for v1.0, it'll be interesting to see where this project goes from here. Alongside the open source offering is a commercial pricing plan. You can support up to three repository users and up to three different repositories for free, but above that will set you back some serious cash. A license for 10 committers and 10 repositoris sets you back 850 euros a year, whilst it is 1600 euros for up to 25 developers and 25 repositories. That's without factoring in a year's worth of support if you need it. Anything higher requires negotiation. This begs the question - is this project really worth it? Is that outlay worth it to avoiding the pain of moving across to Git? Tell us below - do you see worth in SubGit?

ActiveState has delivered Komodo 7.1, the latest release of its integrated development environment that supports a variety of programming languages, including Python, PHP, Ruby and JavaScript, and supports cloud debugging among other things. - ActiveState, which supports dynamic language app development from code to cloud, has announced the release of Komodo IDE 7.1, the latest version of its polyglot programming integrated development environment. With the tag line as the ?worlds fiercest IDE,? Komodo is an integrated development en...

Those Hursley kids are something else, what with their 'Pi' in the sky ideas of doing crazy things like effectively running the WebSphere behemoth on a credit card sized computer with 256 megs of RAM and a 700Mhz processor. Like that would ever happen.

New details have emerged surrounding Java 8, namely the names of the companies set to participate in its development heading towards August 2013, but also some important news about JDK 8. Project Jigsaw, the implementation a standard module system for the Java SE Platform, and later the JDK, has been deferred until Java SE 9 - a proposal not taken lightly by Mark Reinhold, Chief Architect of the Java Platform Group at Oracle. He wrote in the mailing list about the technical challenges: Initial exploratory work toward these goals has been going on in Project Jigsaw in the OpenJDK Community [2]. Steady progress is being made but some significant technical challenges remain, and there is considerable risk that these will not be resolved in time for the proposed Final Release of Java SE 8 in August 2013. There is, more importantly, not enough time left for the broad evaluation, review, and feedback which such a profound change to the Platform demands, both via this JSR (337) and, primarily, a forthcoming JSR to define a standard Java Platform Module System. I therefore propose to defer the addition of a module system and the modularization of the Platform to Java SE 9. This is by no means a pleasant choice, but I think it's preferable to delaying Java SE 8 until the modularity work is complete. The reasons make sense - radicalising or to some reinvigorating Java with a modularised approach is badly needed, but time should be taken to make sure it is as close as possible to being correct. But many developers were banking on Project Jigsaw to be the cornerstone of Java SE 8 and moving forward. Where does this leave the language now? Surely it causes a knock-on effect to other areas of the Java ecosystem. As Reinhold details in his blog about his proposal, the balancing act of features vs schedules is a tough one. This decision isn't a surprising one, given a perceived lack of progress/silence from some. Stability is key though, hence this choice. The scope of Java 8 is big, for sure, but it's a big loss. Earlier, Reinhold also announced the arrival of the primary page for JSR 337 (or Java SE 8 Platform Umbrella), as in accordance of the Java Community Process (JCP). Alongside Reinhold representing Oracle, are Red Hat's Andrew Haley, IBM's Steve Poole and Google's To Be Determined. The internet giant have yet to put forward a candidate to aid Java 8's development, but have, according to Reinhold, committed privately to the project. This didn't stop some to speculate some sort of mystery was afoot on Twitter, only for Reinhold to promptly put them in their place with the following tweet: 'jcp.org is database-driven, and won’t show Google until they actually nominate a representative. #noConspiracy'. So that's cleared up then. Google ought to get on with it. A schedule for Java SE 8 has also appeared, under the guise of OpenJDK, with an Early Draft Review expected in September. This will then be followed by a Public Review phase in January 2013,a Final Draft in June 2013 before the home stretch towards August's release date. Two mailing lists have been set up too - Experts for EG members to post/subscribe to (archives are public) and Observers for the minions to monitor and even offer opinion on progress being made. It may seem a while away yet, but the plans for Java 8 have just become slightly clearer for the next year. That date will come round in no time at all. The omission of Project Jigsaw is understood but it was a big draw for the major update next year - now it's gone, will Java 8 really be a gamechanger? We're not so sure now. More pressure on Lambdas then...

One of the brightest open source projects around now has a public face for their community efforts, after the team behind the RESTful search server, ElasticSearch launched their own company of the same name. Steven Schuurman, CEO of ElasticSearch announced through a blogpost, that he and the creator of the project, Shay Banon, were amongst those part of this new endeavour. ElasticSearch has been knocking around for two years now, since its first release with Banon at the helm in February 2010. Numerous releases arrived after, updating the Java-written RESful search server with new features every time. ElasticSearch is an ambitious project based on Apache Lucene, the high performance indexing and search library created by Doug Cutting. ElasticSearch is effectively a spinoff of Banon's earlier project Compass, after realising the need to start afresh to create a distributed, scalable solution. Thus ElasticSearch was born - choosing JSON over HTTP to create a near real-time search server, offering multi-tenancy support. ElasticSearch attempts to make the majority of its features available through the JSON and Java API and also has the 'Gateway' feature for persistence long-term. Its schema free nature makes it ideal as a NoSQL solution to source documents. Schuurman spoke of how pivotal this day was for the project. Today is the day we launch the company behind elasticsearch! In practice, this means that as of today, users and potential users of elasticsearch have a definitive source for support, education and guidance with respect to developing, deploying and running elasticsearch in production environments. He added later that this doesn't mean the end of contributions to the larger Apache Lucene project which is great to hear. This mirrors the trajectory of other similar open source projects, making sure they got the initial project right before ploughing cash into an commercial hub of operations. They won't be shying away from open source at all, merely making sure those wanting the highest level of enterprise support get it. As many will know, there's a competitor in the space in the shape of Solr (which is also built on Lucene) and the pro and cons should be weighed up before selecting which search server for your needs. One of ElasticSearch's main stumbling blocks was the fact that Banon was a one-man band on the project for some time. Now that ElasticSearch is truly making an enterprise charge, that major negative for businesses is no longer valid with the foundations in place to offer more cohesive enterprise support. ElasticSearch is currently in use at StumbleUpon, Mozilla, Sony and Klout - a decent industry cross-section to to have on your side, but with this move, the project is set to grab more. The plan ahead for ElasticSearch appears to be to refocus their efforts and get more developers onboard. Having one of the leaders of the Apache Lucene project, Simon Willnauer, as another co-founder of the company, as well as technology leader helps somewhat. New horizons lay ahead with a new team. The Big Data analytics field just got that more interesting - Solr or ElasticSearch, which do you pick?

You can suspend a Java application (e.g. a JUnit execution) with a modal dialog. The most convenient way is to use the following one-liner: javax.swing.JOptionPane.showConfirmDialog(null, "Something happened:…"); This trick will usually cause on the application server the following exception: java.awt.HeadlessException, but works perfectly in unit, integration tests on the client side etc. Hint: setting a breakpoint may be even faster :-) Real World Java EE Bootstrap and Effective Java EE Bootstrap Workshops [Airport Munich]

MongoDB is a scalable, high-performance, open source NoSQL database. Instead of storing data in tables as is done in a "classical" relational database, it stores structured data as JSON-like documents with dynamic schemas. This post contains steps to create a sample application using MongoDB and Spring Data for MongoDB. Spring Data for MongoDB Preview Text: ...

Eclipse has recently announced the release of Eclipse Juno which brings new features such as Detecting resource leaks for both Java7 and Java6 etc. Previous Plugins to Install I firstly install all my plugins from previous eclipse version. The process is quite simple Preview Text: Eclipse has recently announced the release of Eclipse Juno...

I was playing around with latest Mojarra and in order not to replace any existing versions at a server module level I tried to package it with my apps. I shouldn't have done that. Here is a short story. Preview Text: I was playing around with latest Mojarra and in order not to replace any existing versions at a server module level I tried to...