gpoul's Out Of Memory Blog

WebSphere Application Server V8.0 has been announced and will eGA June 17, 2011, and GA July 22, 2011.

IBM will discontinue support for WebSphere Application Server V6.1 effective September 30, 2012. Please plan your migrations accordingly. You can find more details in the announcement letter.

Please be aware that the JDK shipped with IBM WebSphere Application Server Versions 7.0 through 7.0.0.13, 6.1 through 6.1.0.35, and 6.0 through 6.0.2.43, for Distributed, i5/OS and z/OS operating systems has a serious denial of service security exposure. When converting “2.2250738585072012e-308″ to a binary floating-point number this vulnerability can cause the Java Runtime Environment to go into a hang, infinite loop, and/or crash resulting in a denial of service exposure.

Information on how to obtain the APARs can be found in our flash alert TN1462019.

This vulnerability is also in Oracle’s JVM, so if you’re using a JVM not shipped by IBM, please refer to CVE-2010-4476.

Using the WS-BPEL 2.0 standard with WebSphere Integration Developer:

The IBM products WebSphere Integration Developer (hereafter called Integration Developer) and WebSphere Process Server (hereafter called Process Server) support the majority of the concepts of WS-BPEL 2.0. However, some of the WS-BPEL language elements in Integration Developer and Process Server Version 7 are still using the syntax defined in the preliminary BPEL4WS 1.1 specification. Many of the language differences are purely related to the WS-BPEL syntax, while the runtime semantics of the affected language elements is identical. For example, in the WS-BPEL 2.0 standard, the switch and terminate activities have been renamed to if/else and exit, respectively, while keeping their semantics exactly the same.

As a result, when business processes are modeled in compliance with the WS-BPEL 2.0 standard, manual rework is necessary before these processes are consumed by Integration Developer and Process Server. To substantially reduce this rework, this article describes an import tool that transforms the affected WS-BPEL 2.0 language elements into semantically equivalent language elements understood by Integration Developer and Process Server V7.

We’ll also have an IBM Software Experience event in Q1 this year. This time we chose to do a PoT on Batch Modernization with Java on February 17. In this one-day workshop you’ll get to know WebSphere Compute Grid and Java-based batch.

If you would like to attend, please complete our registration form on the IBM Software Experience page.

We plan on having additional PoTs throughout the year, so if you have suggestions for topics which might be of interest, please let us know!

On Monday we announced that IBM will join the OpenJDK project. If you’re interested in why this decision was taken and what this means, you definitely want to read Bob Sutor’s blog post on this change in direction.

One major part is the decision that “IBM will be shifting its development effort from the Apache Project Harmony to OpenJDK” and that there will be changes to the JCP “to make it more democratic, transparent, and open”, although it seems to be unclear what concrete steps will be taken.

Henrik Ståhl posted a few details about Oracle’s future plans on his blog, but apart from the fact that we’ll finally see a Java SE 7 and Java SE 8 JSR, there is not too much of substance to report. We’ll see whether that gets more concrete over the coming months.

It turns out that the JDK 7 development project is delayed quite a bit and the current estimated ship date is now Mid 2012. Given this delay Mark Reinhold is currently looking for feedback on a proposed Plan B, which would only include certain parts of Coin, NIO.2, InvokeDynamic (JSR 292), and “JSR 166y” (fork/join, etc.) in JDK 7 and delay everything else until JDK 8.

The estimated ship date for this Plan B would be Mid 2011 with JDK 8 being delayed an additional 6 months with a ship date in Late 2012.

I’m not a huge fan of releasing two major JDK releases within two years when the most current release is already almost 4 years old, but it seems like that’s what Oracle is currently leaning towards.

Comments on this post are closed, please post your feedback directly on Mark’s blog.

Update 9/21: Plan B is now the plan of record.

The WebSphere Application Server V8.0 Beta is now available.

Update 7/9: Andrew posted that the download is now fixed and he also included some helpful links to get started with trying the beta.

You learn something new every day. Looks like Lombardi uses GWT for Blueprint and the web portions (i.e. everything that’s not Eclipse-based) of Teamworks. There is a video on the GoogleDevelopers channel where Alex Moffat showcases Blueprint and describes why they chose GWT.

In addition they’ve also been demoing their solution as part of the Google I/O 2010 Sandbox this week.

btw: Lombardi is an IBM company.

A few recent WebSphere announcements we presented last week at Impact 2010:

• WebSphere DataPower XC10 caching appliance – also known as the eXtreme Scale with SSD in a purple box
• WebSphere CloudBurst Appliance 2.0 – now featuring WebSphere Process Server support, multi-image pattern support, dynamic system management to add/remove capacity, intelligence for the runtime / WebSphere Virtual Enterprise features packaged as WebSphere Application Server Hypervisor Edition Intelligent Management Pack for use with CloudBurst and Hypervisor Edition, and last but not least we now also support Red Hat Enterprise Linux in addition to SuSE Linux Enterprise Server
• CICS Transaction Server and WebSphere Application Server Feature Packs for Dynamic Scripting – Running WebSphere sMash with WebSphere Application Server V6.1/V7.0 or CICS Transaction Server for zOS V4.1.

Of course by reading it on this blog you’re at least a week late and you missed all the labs and presentations in Las Vegas, but there’s still enough time to prepare for Impact 2011 :-)