Java EE 7 and GlassFish Day at CloudBees

The launch of Java EE 7 today is a very important event for the Java EE community. Since Java is our DNA here at CloudBees, and as we try to anticipate our customers’ needs, we wanted to be part of this new episode of the Java EE adventure.

We are happy to announce today:

  • The availability of GlassFish 4 Web Profile to allow users to explore the new features of Java EE 7 Web Profile such as WebSocket, JAX-RS 2.0, non persistent EJB timers or async beans

  • Managed support of the GlassFish 3 Web Profile stack, after months maturing in our community incubator

For GlassFish v3 users, you now have the same kind of fully managed CloudBees experience that we’ve been providing for Tomcat and JBoss. And if you want to explore EE 7, understand its new features and how your applications will behave on it, it’s all waiting for you on CloudBees.

In addition to the traditional docs and demos we are delighted to demo Antonio Goncalves’ Petstore EE 7 app running on our GlassFish 4 Web Profile stack (source code and clickstart here on GitHub).

CloudBees GlassFish

Antonio Goncalves’ Petstore EE7 on CloudBees GlassFish 4

Our GlassFish3 docs, our GlassFish4 docs and demo ClickStarts:


Launch GlassFish3 ClickStart 

Launch GlassFish3 ClickStart

Launch GlassFish4 ClickStart

Launch ClassFish4 ClickStart

Note: please be patient when starting your app on GlassFish. The initial deployment often takes more than 30 seconds and during this time GlassFish temporarily displays its welcome page instead of your application’s homepage.

We hope that you will have a lot of fun using our GlassFish runtimes and exploring Java EE 7 on our platform!


— Cyrille Le Clerc
CloudBees, Inc.

Cyrille Le Clerc Architect CloudBees

Cyrille Le Clerc is an elite architect at CloudBees. He came to CloudBees from Xebia, where he was CTO and architect. Cyrille was an early adopter of the “You Build It, You Run It” model. He naturally embraced the DevOps culture, along with cloud computing. Cyrille is very active in the Java community as the creator of the embedded-jmxtrans open source project and as a speaker at conferences.


But you guys lie. For startes, there's only one way you can create a new "glassfish" supported configuration. And that is using your "click start" menu. You can choose Glassfish in the the list, but after having created the app, a drop down on the configuration says "Tomcat". If you enter an invalid URL, you'll also see that it is Tomcat that says the URL cannot be found. Moreover, you can only deploy WAR files. No EAR files. So I have all the reason in the world to call out your hoax. Please prove me wrong.

You can use the SDK to select glasfish runtime, clickstart is just a "simpler" (web user friendly) way to do. As claimed on blog post, this is about GlassFish 4 **Web Profile**, not full profile. We also have a full-profile partial implementation (

Hello Martin, As my colleague Nicolas mentioned, you can deploy on Glassfish runtimes with our Bees SDK (1) ; we are currently rewriting our Web Management Console and the ability to choose any ClickStack (runtime) through the GUI will come soon after our new web interface is released. The command to deploy is: bees app:deploy -a myapp -t glassfish4 path/to/my/app.war Regarding the support of EAR files, it is on our todo list but we did not have requests to implement it so far and we focused on other features. Last month, we added the support for Glassfish 4 Full Platform (2) and wired its JMS broker to a JDBC persistent store. Could you please give us more details on the reason why you want EAR? EJBs shared between in several WARs? Sharing data between several WARs? Using the same domain name for several WARs? Or just deploying several WAR at once? Moreover, can I ask you if you are thinking of migrating from Glassfish to Wildfly (3) after Oracle's announcement? Many of our Glassfish users already told us they are migrating. Cyrille (CloudBees) (1) (2) (3)

I am new to cloudbees and have an EE glassfish application developed with netbeans. I do not want to use clickstart. after I deployed the app, it only lead me to the glassfish server page. Is there a guide or tutorial on how to deploy a locally developed WAR to glassfish? Thanks

Hello James, Did you specify in glassfish-web.xml a "context-root" element with value "/" ? Moreover, you sometime need to refresh after 20s - 30s the page to let Glassfish deploy your app. More details at . Cyrille

Add new comment