I wrote an article on InfoQ recently about IoT. This was based upon a presentation I saw whilst at the JCP EC meeting in September from ARM. I found it fascinating, especially given the work we've been doing on things like Raspberry Pis. It was also interesting to hear how important ARM and others see Java in this space. So if you haven't read the article then take a look.

Mark Little


Posted by Mark Little Sep 24, 2013

We've been talking about PaaS for several years now. Whether it's outlining our intentions around Enterprise PaaS and then delivering with the first EE6 Platform as a Service, discussing how EAP, EE6 and Java are critical for mobile and cloud, or many presentations and announcements at Red Hat Summits (exercise left to the reader to check these out), I think it's safe to say that we've been leading the push for Cloud, PaaS and relationships with Java. Last week we announced another key presentation update on our PaaS strategy that would happen at JavaOne and I'm pleased to say that's now happened and I can talk publicly about the work that our teams have been doing over the last few months.


We're terming this xPaaS because it is meant to encompass much more than what PaaS has typically come to be associated with (ePaaS, or Enterprise PaaS, is a component of xPaaS). In many ways we've been talking about xPaaS for a couple of years and particularly how technologies and methodologies such as SOA or integration must play within the Cloud and between users of the Cloud. But with the advent of mobile, obvious problems to come such as that indicated by Shannon's Limit, and other changes in the way our industry, xPaaS has come to encompass much more.

Screen Shot 2013-09-21 at 16.30.18.png

Some of our recent acquisitions, such as Fuse (Fabric, Camel), Polymita and efforts like AeroGear, WildFly, embedded device work (e.g., Raspberry Pi) etc. have all contributed to xPaaS in one way or another. We demo-ed some of this during this year's Summit JBoss keynote, and with iPaaS (Integration PaaS) James has been previewing it for many months. The xPaaS announcement brings all of this together and pretty soon developers will be able to use these technologies themselves and provide us with feedback as well as help to evolve it.

Screen Shot 2013-09-21 at 16.53.29.png

Some important highlights for the iPaaS component of xPaaS include: code-less UI - drag/drop/configure deploy - anywhere - public/private cloud, bare metal etc., cloud and SaaS connectors (via Apache Camel), auto-scaling to meet demand - all managed from a central platform, and of course it works on OpenShift.


As I mentioned already, mobile is an important part of Cloud today. So another part of xPaaS is our Push Server which runs on OpenShift and has AeroGear at its heart. But some important things to note about this release is that we have integration with iOS (APNS), Android (GCM), and FFOS/Web (Mozilla SimplePush), with associated client SDKs. There are also sender SDKs for Java, with Node.js, and PHP in development.

Screen Shot 2013-09-21 at 17.02.34.png

And of course just as outside of the Cloud, once you start to create your applications from components and services, BPM (in the form of jBPM, for instance) and related technologies such as BAM, become a necessity. So of course BPM-as-a-Service is an integral part of xPaaS.


Screen Shot 2013-09-21 at 17.07.15.png

Of course I can only give you a taster of what we've just announced. You'll hear more from us over the next weeks and months as we roll out these xPaaS components so you can try them out. Our end goal is supported products and we'll be making other announcements later. For now check out the xPaaS announcement and watch this space. This is when PaaS really enters the enterprise domain!


And a big congratulations to everyone in the teams within Red Hat who have been involved in this announcement and the technologies it showcases! It's a great effort!

Mark Little


Posted by Mark Little Aug 7, 2013

We've been pretty busy lately so this is slightly delayed. However, I do want to announce that Red Hat has joined the Google Cloud Platform Partner Program as a Technology Partner. Through this program, Red Hat and Google will collaborate on an open source community project known as JBoss CapeDwarf that increases the portability of Java-based Google App Engine applications and expands the deployment choices beyond Google’s cloud.


The JBoss CapeDwarf community project is an implementation of the Google App Engine Application Programming Interface (API) that enables applications to be deployed on either Red Hat JBoss Enterprise Application Platform (EAP) or its upstream application server project, WildFly, without modification. Red Hat JBoss EAP uses many of its enterprise-grade services such as authorization, transactions, data grid, and messaging to fulfill the Google App Engine API functionality in a way that is transparent to developers, users and the application.


The Google Cloud Platform offers a broad set of APIs for application development, cloud storage, large-scale computing, and big data. CapeDwarf leverages the Google App Engine on top of Red Hat JBoss EAP, regardless of whether it is deployed on premises or in an IaaS environment. Through the Red Hat product portfolio, developers have a path to run Google App Engine applications on a full enterprise-grade stack, using Red Hat JBoss EAP or combining it with Red Hat Enterprise Linux, OpenShift Enterprise, Red Hat CloudForms, or Red Hat Enterprise Virtualization.


CapeDwarf implements all the APIs as defined by Google App Engine for Java. The implementation serves as an integration layer between GAE APIs and services offered by JBoss EAP either out of the box or added by CapeDwarf itself. All data related APIs as well as others (Tasks APIs, Logging API) rely heavily on Infinispan, Hibernate Search, JGroups and Lucene, while the Tasks API also uses the HornetQ messaging system. The User API and the OAuth API rely on the Picket- link library.


Now of course you might ask why? Well ...


  • No more lock-in: Move your app from the Google cloud to CapeDwarf and back any time.
  • Google AppEngine on-premises: Now you have the option of initially deploying your app in your own CapeDwarf-based private cloud. When your app outgrows it, you’ll be able to simply migrate the app to Google’s Appspot.
  • Simple to create cluster: JBoss EAP makes it easy to run a multiple instances in a cluster. CapeDwarf has been implemented to support clustered environments from the start.
  • Easy debugging and multi-node testing: While the development server provided by Google App Engine can only be run in a singleserver configuration, CapeDwarf allows you to test your app on multiple nodes prior to uploading it to Google Appspot. Through remote debugging, you can also find those elusive bugs that do not show up when running the application on a single server.
  • Pure Java: CapeDwarf is written in pure Java and is universally portable.
  • Opensource: The complete CapeDwarf codebase is fully open sourced, which means you can fix any bugs you may find yourself, without waiting for the vendor to fix them.


You can deploy and run your Java App Engine applications on your own private RedHat’s OpenShift cloud: https://www.openshift.com/quickstarts/capedwarf


So go and give it a try. You'll also find that CapeDwarf offers access to many standard EE6 APIs that aren't available in vanilla GAE.

I wanted to write up my experiences at JUDCon, CamelOne and Summit last week. Then I remembered that I'd taken one or two photos, so what better way than to illustrate with a picture?




Things got of to a great start on Sunday with the reception:




I haven't got the final figures, but we had over 500 attendees at JUDCon and CamelOne, with many of the sessions standing-room only:



On the first evening we had our usual dinner (pizza, salad and beer), podcast and lightning talks. However, this time we also were given the Best Application Server Award from ZeroTurnaround (thanks guys!):




Then of course there was the traditional JBoss keynote. The team practiced and finalised the demo throughout the previous two days and did a fantastic job!




We had over 1000 people in the room in the end, with many having to stand and watch, and almost as many people who couldn't get in (fire regulations):



But fortunately it went over fairly straighforwardly in the end!




And of course there was the traditional JBoss party, with the (becoming traditional) range of JBoss-themed drinks. I tried hard to sample each and every one of them on the night! I'm not sure if I accomplished this, because my only clear recollections are of discussion quantum mechanics and failure detection with James Strachan at the bar, using alcohol filled glasses to represent subatomic particles!





In conclusion, I think all of the events went very well! The sessions I managed to attend were great and very vibrant. The sessions I was speaking at also seemed to be well received. So overall I'd say it was a success! Onward to next year and San Francisco!

Mark Little

EE7 launch announcement

Posted by Mark Little Jun 4, 2013

Java Enterprise Edition (Java EE) is truly a bedrock technology, serving as the global standard for enterprise application development.


The next release of Java's Enterprise Edition 7 raises the bar even higher for enterprise Java computing. RedHat has played a key role in this release as an active member of the Java development community including taking the lead in developing two new JSRs. 


To learn more, register today for the upcoming virtual launch event, planned for June 12, 2013.


Screen Shot 2013-06-04 at 13.53.46.png


RedHat development leads will provide overviews of their new JSRs in short breakout sessions during the upcoming launch. Pete Muir will give an overview of CDI 1.1 (JSR 346). Emmanuel Bernard, who took the lead in developing Bean Validation 1.1 (JSR 349), will also host a breakout session.


Attendees will learn about new ways to support increasing enterprise requirements; HTML 5 and dynamic, scalable applications; and a continued focus on developer productivity and technology integration.


Register  for the launch event today. Then come and hear from the experts about EE7 and come to Summit to hear where we think EE8 and beyond should be going.

Mark Little

JBUG Scotland

Posted by Mark Little May 10, 2013

I had the pleasure of speaking at the Scotland JBUG earlier this week in Edinburgh. It was a great event and well attended.



I gave a presentation on our roadmaps for various products as well as some of the technical direction. There were a lot of good questions and the presentation should be uploaded soon.

Mark Little

EE7 is approved

Posted by Mark Little May 2, 2013

It's official, Java EE7 has been approved overwhelmingly. This is great news, particularly for the updates to various components such as CDI and JMS. I'm proud of our continued association with the JCP and glad to see that we could get this out relatively on time. Now it's on to EE8. Furthermore, given the WildFly announcement last week, we'll be looking to implement EE7 as soon as possible.


And now for the annoying and frustrating aspect: it seems like we have no vote recorded! Whether through a fault in the system (it's happened before), forgetfulness (it's happened before) or insanity (no comment!) we appear to have no vote associated with EE7 and some related JSRs. If this is our fault then it's my fault, since I had the token to vote. I'm chasing this with Oracle at the moment, because I'm sure we did vote! But according to the records that didn't happen. If it turns out we didn't vote then a big Mea Culpa to the team and our communities!


For the record: we would have/should have/did vote Yes/Approved to all of them.

Mark Little

And the winner is ...

Posted by Mark Little Apr 19, 2013

It's hard to believe that it was so many months ago that we announced the voting for the rename of JBossAS at Devoxx:



At the time we had hoped to announce the name, but we had simply far more suggestions for names from the community than we ever expected. If we had been able to announce the winner, I had hoped to stand up there with a series of envelopes in a very Oscar-like manner and say things like "And the nominations were ...", of course with suitable drum rolls etc. Well it didn't happen at Devoxx and so we announced the nominations (without drums or music) and that we would make the final publication of the new name in early 2013 at a suitable conference or workshop.


Once the voting was completed and we had a name, the search was on for such a suitable conference and workshop. We had several options, but it seemed only right that we make the announcement about our most significant community project at our most significant community conference: JUDCon. As fate would have it, JUDCon Brazil (the very first time we will be in Brazil with JUDCon) was the first such conference after the votes were tallied. Therefore, we now had our name and our event, which meant I could put all of this together into a suitable keynote presentation. If you were there (or are there, depending upon when you view this article), you'll know that the runners up were jBeret in 3rd place and BaseJump in 2nd place. But the overall winner was ... (imagine a drum roll please) ...



You'll see new domains, forums, JIRAs etc. associated with the project coming on line over the following hours and a presence on github imminently. I'd like to thank everyone who submitted names and voted. I'd also like to thank everyone who has helped to make this transition an overall positive thing for the community of users and developers. And finally I'd like to thank our design team for doing such a great job with the logo.


This announcement, along with the other one I made last month around free EAP binaries, are probably two of the most significant things to happen to the project in a long time. I expect to see us all build upon these changes and continue to ensure that WildFly remains the top open source application server for developers and deployers alike. We'll be making a lot of other announcements over the coming months around WildFly and several of our other projects and products, so watch out. You'll also start to see a few other changes around our community developer efforts and JBoss.org, but I won't spoil the surprise just yet!

Over the years as JBoss and then Red Hat, we've tried very hard to ensure that we work as an open organisation helping our communities. Whether you're a paying customer using the subscription to get great support, or an organisation/individual who doesn't need support (maybe because you can self support) you're all important to the wider success of JBoss and enterprise open source. Now prior to Red Hat, we at JBoss would support pretty much any combination of projects and their versions, as well as the cross-product combination. Of course that couldn't scale indefinitely and when we were acquired by Red Hat we moved to a more stable and scalable solution: the products would only be based on a very specific version of each project at a given point. I won't go into the details of how we take the projects and create the products but suffice it to say that there's a lot of work done by the development teams, QE, docs and of course productisation. This work goes into the up stream community projects but it can take a while for us to create new community binaries that benefit from it, due mainly to the effort we have to put in to supporting our customers, building other releases etc.


Now it should not come as a surprise that open source is core to everything we do and everyone we employ. It's in our blood and we will do a lot to ensure it continues to be a success. Sometimes we hear that the community is lagging behind the products, or that we're not as responsive as some might want us to be because of our product focus. What we really want to do is give the best possible experiences to our customers and our wider community, with the best Java middleware implementations around. Therefore, we've been thinking long and hard about the problem and how to resolve it. It's not easy and there are a number of ways to try to tackle it. However, there is one solution we've come up with that I think allows us to continue to provide the best products and support to our customers whilst at the same time ensuring that our communities are able to benefit too in a much more timely manner. It is this solution that I want to announce today.


What we are proposing to do is pretty simple: from the point where we start to productise the community project (e.g., AS7.1) we will release all product builds that we create as a result of this process into the community (e.g., EAP 6.0 Alpha 1, which is based on AS 7.1) so that all developers within our communities or with our customers can take advantage of them immediately. There will be no other community binaries for that major release of the community project after that point because the product builds are effectively a superset and we hope more beneficial to most developers. Of course community builds of the next major revision of the project will happen in parallel so you'll be able to contribute to and track those separately, so it's not a case of replacing community with product-only binaries. We're also changing the download processes and license for EAP so that it is as easy for developers to get hold of these bits as it is to get the community binaries. The net result is that everyone gets to experience the product whether or not they buy a full subscription with support. Now of course the value of the full subscription is much more than just the product binaries and support, and we all hope that people will want to migrate to a full subscription, but it's not going to be a requirement unless you want to put JBoss products into deployment. If you are a developer then you can use the same binaries as customers with this new subscription without having to worry about evaluation periods, or missing critical bug fixes.


I believe this is a great step in the evolution of JBoss/Red Hat and enterprise open source in general. We're continually breaking down barriers to adoption of open source and enterprise middleware, whether by making EE6 much more easily consumable via approaches such as AS7 and CDI, or pushing into new communities with efforts such as TorqueBox or Immutant. With this change that I have announced, we're now removing another barrier by ensuring that all of our communities can get access to our product releases!



Mark Little

A new JavaChampion

Posted by Mark Little Feb 5, 2013

Back in May 2012 I announced that Charlie Nutter and Thomas Enebo were moving over to Red Hat. Since that time they've worked flat out on JRuby and collaborating with the TorqueBox team. But I'm really pleased to see that Charlie has also been given the title of Java Champion:


Screen Shot 2013-02-05 at 13.15.37.png

Congratulations Charlie! Another high point for JBoss, Red Hat and the extended Java community.

Mark Little

Adventures in Pi Land

Posted by Mark Little Dec 31, 2012

Happy new year to those of you for whom the day has changed and of course to everyone else when it happens! I just wanted to cross-post a couple of articles I've written on some of the pet projects I've been working on over this festive holiday season. They're related to the Raspberry Pi, Fuse Fabric, Arjuna/JBossTS/Narayana, vert.x and MongoD. So if you're interested, check out part one and then part two. And once again, I hope everyone has/had a very happy new year!

Mark Little

Merry JBoss Christmas

Posted by Mark Little Dec 25, 2012

It's Christmas day and I know many of you will be busy opening presents, eating lunch or just sleeping off the night before! But I did want to take the opportunity to wish everyone a very merry Christmas and best wishes for 2013. It's been a great year for JBoss/Red Hat, what with the release of EAP 6, 3 JUDCons, a couple of acquisitions and a partridge in a pear tree! All of those things (with the one obvious exception!) in conjunction with EAP+OpenShift, our mobile work around AeroGear, a larger than ever JBossWorld/Summit, our continued invasion of JavaOne, hiring some of the key JRuby developers, and much much more go to show that not only do we have our mojo back but that we are breaking down some of those old perceptions that the JBoss brand is only associated with the application server. Our communities have grown, with the addition of new projects such as CapeDwarf, and others have just continued their expansion, like Arquillian. But at the heart of all of this success is one common component: you, our community. I cannot over state how important our communities are to me personally, but also to JBoss and Red Hat. You help to ground us in the realities of what users want now and in the future, shaping middleware not just in the Java space but across many other languages. Whether you provide code to a project, provide feedback, give use cases, or somehow give some other kind of input, you are members of the JBoss family. And for that, I thank you! Here's to 2013!

Mark Little

OpenShift goes on premise!

Posted by Mark Little Nov 28, 2012

I've been talking and presenting about cloud and PaaS for a number of years and each time I do, I say pretty much the same thing (and I paraphrase): "I think private (on premise) PaaS will be more important than public PaaS". I won't go into the reasons why, except to encourage anyone interested to check out some of the older posts. That's not to suggest that public Cloud isn't important or useful, which is why Red Hat has been making great strides with our OpenShift offerings, which we're proud to ensure remain open source. Over the last year or more, we've seen Java added to OpenShift, as well as JBossAS and EAP, and many other languages and frameworks are there too. The number of applications running on OpenShift has grown significantly since we officially released it last year and our community has increased much more.


However, although there is still a lot more we want to do on public OpenShift, the feedback we have been getting from community and customers has been the need for an on-premise offering. The intention with any on-premise PaaS has got to be that it's a cloud and not just a rebadged virtualisation offering and I'm really pleased to see that we've stuck to our principles with the announcement of OpenShift Enterprise. All of the things you've heard about OpenShift, such as its mission critical security (based on SELinux), flexibilty (multiple languages, frameworks etc.) and scalability (including, cloud bursting eventually) will be part of OpenShift Enterprise, the first enterprise PaaS. So what about JBoss? Well as I've said several times before, if you want an enterprise PaaS then you need an enterprise infrastructure (middleware), so it shouldn't come as a surprise that your favourite JBoss technologies and products will be coming to OpenShift Enterprise. In fact EAP and EWS (the production versions of the application server and Tomcat) are available already.


This is a very exciting time to be involved in middleware and the Cloud. I'm pleased that we can finally push forward on the larger vision we've been talking about for so long. And what next? Well maybe we'll be able to bring some of that ubiquitous computing cloud into the picture eventually



Mark Little

Devoxx 2012

Posted by Mark Little Nov 18, 2012

Devoxx has always been one of my favourite conferences. Back when JavaOne was more product (and Sun) oriented, it was a bastion of independence and what was going on in the wider Java community. Even today, with JavaOne improving, it is still an important conference. And that's even though I prefer it's old name of JavaPolis (what's that they say about trying to please all of the people all of the time?) This year was even bigger for Red Hat/JBoss. Not only did we have our usual healthy mix of sessions on things ranging from Arquillian to Polyglot, but we were a key sponsor. We payed for the party at Noxx, which was a very interesting venue. We also co-sponsored the Hackergarten, which was a great opportunity to meet like minded developers and community members.


Importantly, we also used Devoxx as part of our renaming exercise for JBossAS. However, we did have to change our original plans slightly. Back at JavaOne when we announced the rename, we thought that we'd have started and ended the name collection weeks ago and had a select number of names voted upon by Devoxx. In fact I worried about how we would choose the final number of names to put up for vote from those suggested by the community. How wrong I was. We received over 2000 names and from that there were almost as many unique entries. There were only a few names we obviously couldn't take forward and even less from people who suggested keeping the original name. However, then we ran into the reality of copyright and trademark law! For each name our legal team had to do an exhaustive search to ensure we would not be treading on some other company's name or product. And this search takes time - proportional to the number of names!


What this meant was we simply had no way to get the names ready for vote until just before Devoxx. So we decided to repurpose our Devoxx announcement (at the start of the keynote) to telling people the above story and announcing the names for vote. Now just as some people may not have liked the rename of JavaPolis to Devoxx, Marathon to Snickers, Borland to Inprise, or Coco Pops to Choco Krispies, some also don't like the rename of JBossAS or the selection of names we've ended up with. But from the feedback we've received, including during the Devoxx BOF (more below), it seems that the majority of people so far get it or don't see it as too much of a problem and can work with one or more of the names. Now that we've added more descriptions around the various names (thanks to the AS team expanding on those submitted originally) I hope people can see the potential with them and give it a chance. (If you feel otherwise, then feel free to email me as I value your feedback.)


After the keynote, Ray and I had a session where we tried to give an overview of all things JBoss related. We decided to reuse this years JBossWorld keynote, but without the audience participation in the demo. Ray did a great job of re-running the demo with bots playing the various roles and this was great too, since it shows how much we've simplified the testing and simulation of complex applications. And of course there was the BOF, which really could have run even longer if we'd had the room longer. There was a lot of good discussion and community involvement, as well as beer! And because we're good community members, we let our beer spill over into the adjacent BOFs


In conclusion, Devoxx was a great success. Our sessions went well. The community gave us a lot of great feedback. I got a chance to meet new people and friends. And the general vibrancy around the conference made a fitting conclusion to 4 months of travelling!

So Ray and I just finished our stint at the Devoxx keynote this morning to announce the names for voting. The video should be up soon but in case you don't get a good view of the Dilbert cartoon we used to explain the situation to the audience, here's the link. We were struggling with how best to let people know the difficulties in taking 1800+ submissions and getting them through the legal process, when Dilbert came to our rescue. I don't think we could have put it any more succinctly as this, so why bother?! Anyway, the voting process is now open and we'll be updating the pages on JBoss.org to try to add more flavour/meaning to the names that we eventually managed to get from the great submissions.


Thanks to everyone who submitted a name. There were many great names, but unfortunately we couldn't select the majority of them for reasons mentioned in the above cartoon. But the ones we have are good and I'm sure we can get behind whatever is eventually selected and make it a worthy successor to the JBossAS name! So get voting.



Filter Blog

By date:
By tag: