Skip to Content

Most of the following opensource projects are related atleast remotely to some of our recent endeavors although they might not be very well known. We developers can get some ideas from these projects and also the processes used in their development.


JBoss 3.x is a full framework for you to build your own applications. It is based on a Java microkernel (JMX) and service oriented architecture (SOA). JBoss 4.x is exploring aspect oriented middleware (AOM) and Java based middleware independent of J2EE.

WAS guys are we listening ?


Working with object-oriented software and a relational database can be cumbersome and time consuming in today’s enterprise environments. Hibernate is an object/relational mapping solution for Java environments. The term object/relational mapping (ORM) refers to the technique of mapping a data representation from an object model to a relational data model with a SQL-based schema.

Hibernate not only takes care of the mapping from Java classes to database tables (and from Java data types to SQL data types), but also provides data query and retrieval facilities and can significantly reduce development time otherwise spent with manual data handling in SQL and JDBC.

Is this stuff possible with our middleware ? Not sure…


Apache Avalon provides a complete platform for component programming including a core framework, utilities, tools, components and containers. By using key design patterns such as Inversion of Control (IoC) and Seperation of Concerns (SoC), Avalon achieves a number of advantages over traditional object oriented programming frameworks.

Component Development Gets Better Here


The features in JDNC are being driven by the functionality needs of enterprise clients and by what’s currently complex to construct using base J2SE APIs. We anticipate this feature list to grow substantially as developers use JDNC in real world app scenarios.

Webdynpros ???


Apache Cocoon is a web development framework built around the concepts of separation of concerns (making sure people can interact and collaborate on a project, without stepping on each other toes) and component-based web development.

Cocoon implements these concepts around the notion of ‘component pipelines’, each component on the pipeline specializing on a particular operation. This makes it possible to use a Lego(tm)-like approach in building web solutions, hooking together components into pipelines without any required programming.Cocoon is “web glue for your web application development needs”. It is a glue that keeps concerns separate and allows parallel evolution of the two sides, improving development pace and reducing the chance of conflicts.

This I beleive is related (atleast from what it says) to our good little XI.

What is important to look at is how the ideas have come up and then implemented successfully in the open source model. All of us know that this model has proved itself in the OS space, now I believe its doing good in the enterprise infrastructure area and next could be building enterprise software…so beware..;)

If you are still doubtful take a look at these projects:

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member
    Well, I would like to add at least a testing framework like JUnit to your list. Whilst available for the Java side (NW Developer Studio), the testing facilities in ABAP are really ugly. Don’t tell me something about CATT, it’s on a level far too high to begin with testing.



    1. Former Member Post author
      I do completely agree with you. But I think we also need to include the process of unit testing more seriously in our development life cycle.
    2. Former Member Post author
      I do completely agree with you. But I think we also need to include the process of unit testing more seriously in our development life cycle.
    3. Joerg Wegener
      Hi Klaus,

      in the new NetWeaver release ABAPUnit will be integrated into the language in a very elegant way. You can add test methods directly into your productive classes, marking them as “for testing”. When the software is shipped, the test methods are removed by the software factory. So, up until this point your tests are transported to every SAP system, allowing you to run them for example to see whether your MIT system is set up properly.

      On a related note, there is an ABAPUnit framework which has been developed in SAP Banking. I think there were plans to migrate it into the ABA. If you can find an include “ABAPUNIT” or a transaction “ABAPUNIT_GEN” (which will create most of the coding required for you) then you have it available.

      And the ABAP version of JUnit makes good use of ABAP facilities (doubleclick navigation to failed tests, automatic e-mail notification…). It compares well to non-ABAP Unit test frameworks.

      It might not be widely-known, but it is there, and it is pretty cool (well, both versions, actually).



Leave a Reply