Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member

Some of you have noticed that since this week you can download a Beta version of SDK 2.x for SAP NetWeaver Cloud platform from your FREE developer account. Perhaps most of you are curious what comes with this new major (Beta) version of our SDK? - In this blog, I will give more information about this.

What comes inside SDK-2.x.Beta?

With this release of the SDK, we have certified SAP NetWeaver Cloud platform as Java EE 6 Web Profile compatible.

Java EE 6 Web Profile is a subset of the Java Platform, Enterprise Edition specifically targeted at web applications. This makes it a perfect fit for cloud usages, which are typically rather lightweight. In details, the SDK 2.x Beta of SAP NetWeaver Cloud brings support for the following Java EE 6 technologies:


Supported Java EE 6 Technologies

Servlet 3.0

JavaServer Pages (JSP) 2.2

Expression Language (EL) 2.2

Debugging Support for Other Languages (JSR-45) 1.0

Standard Tag Library for JavaServer Pages (JSTL) 1.2

JavaServer Faces (JSF) 2.0

Common Annotations for the Java Platform (JSR-250) 1.1

Enterprise JavaBeans (EJB) 3.1 Lite

Java Transaction API (JTA) 1.1

Java Persistence API (JPA) 2.0

Bean Validation 1.0

Managed Beans 1.0

Interceptors 1.1

Context and Dependency Injection for the Java EE Platform 1.0

Dependency Injection for Java 1.0

Java Mail 1.4

You can find more details on the Java EE 6 Web Profile on the following page http://jcp.org/en/jsr/detail?id=316

What does it mean for the application developers?

In short, you can use standard Java EE technologies to build better applications. For example, with SDK-2.x.Beta it is possible to create an application which uses EJB Lite POJOs and JTA transactions while relying on container managed persistence. The UI layer will nicely accommodate JSF components, consuming the underlying model while the utilized resources and services are injected via annotations. Last but not least, all the SAP NetWeaver Cloud services can be leveraged, following the standard Java EE way of object discovery – using JNDI. Java EE is the dominant standard with the largest developer community, for developing enterprise applications in Java and we’re very happy to offer that standard to the SAP NetWeaver Cloud application developers.

In order to use these features, please make sure that your Eclipse-based Development Tools are upgraded at least to version 1.9.0. This version will enable the features you need in the Eclipse IDE to develop Java EE 6 Web Profile applications. As expected, the SDK-2.x.Beta can be configured in Eclipse IDE for Java EE Developers by using the way you already know.

Is it open source or proprietary?

The SAP NetWeaver Cloud application runtime container is a JVM-based environment, using standard Java VM which is running extended release of Eclipse Virgo server on top. Therefore, SAP is working very closely with different projects inside the Eclipse community to extend and evolve the technology to a state which is suitable for cloud scenarios.

Why beta?

We aim to establish Java EE 6 Web Profile as the default application programming model for SAP NetWeaver Cloud, yet we want to make sure that this meets your expectations. Therefore, we want to collect as much as possible feedback from you, and to learn more about the things you want to use and the way you want to use them. Therefore, at the moment with SDK-2.x.Beta you can deploy applications only in Beta and Trial accounts. We’re eager to find out what do you think about it! Please do not hesitate to share your experience and feedback in our Dev Center discussions forum.

What comes next?

In the coming months we will focus on enabling the Java EE 6 Web Profile for productive usage too. In the meantime, we will try to keep you blogged about technical capabilities and how-to guides - to keep you interested and to collect feedback on the application programming model features.