Cloud Foundry Improves Java Support

Until now, users running Java applications requiring an application server typically relied on Apache Tomcat as the default container in the Cloud Foundry Java Buildpack.

Tomcat is a great light-weight option for many Java web applications supporting the Servlet specification, but there are also many applications that use some Java EE features such as

  • EAR – enterprise archive packaging
  • JMS – java messaging service
  • JDBC Data Sources
  • Cloud Foundry’s Loggregator – a unified log stream
  • Blue-green deployment – a release technique to reduce downtime and risk by running two identical production env.s called Blue and Green
    ( CF version 6 only )
  • plus other application server-specific features not available on Tomcat

The new Oracle WebLogic buildpack along with the recently announced JBoss buildpack, now enables new types of Java applications to run natively on Cloud Foundry.

More Java News on Cloud Foundry

http://blog.gopivotal.com/cloud-foundry-pivotal/products/cloud-foundry-expands-java-support-with-new-oracle-weblogic-buildpack

Build Pack Debugging

Do you need to debug build packs ? No, neither do i, but when i grow up and become a hacker, i’m gonna read this: https://github.com/cloudfoundry/java-buildpack/blob/master/docs/debugging-the-buildpack.md

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s