Keynote am Montag (10.5.) 17 Uhr
One of the most challenging areas in J2EE development today is persistence. This presentation describes some of the challenges faced and what developers require to address those challenges. It uses the Oracle Application Server TopLink product to demonstrate why flexibility, performance, scalability, and ease of development of a persistence solution can be critical factors in J2EE applications.
Keynote: hier downloaden!

Keynote am Dienstag (11.5.) 8.30 Uhr (Eröffnung)
SAP stellt mit NetWeaver eine Service-orientierte Plattform zur Verfügung. Damit werden Service-basierte Lösungen im SAP-Umfeld nicht länger nur als Eigenentwicklung realisiert - eine neue Generation von Standard-Lösungen entsteht, sogenannte Cross Applications. Diese sind vorgefertigte, konfigurierbare Applikationen und nutzen vorwiegend Services, die bereits von bestehenden Lösungen im Unternehmen zur Verfügung gestellt werden. Wie wird J2EE als Basis für NetWeaver eingesetzt und welche Impulse gehen im Java Community Prozess von SAP aus, damit J2EE künftig besser die Bedürfnisse bei der Entwicklung und dem Betrieb von Business-Applikationen unterstützt? Diese und weitere Fragen werden in dem Vortrag behandelt.Keynote: hier downloaden!

Keynote am Dienstag (11.5.) 17.45 Uhr
Sun's Core J2EE Design Patterns are drawn from proven, prior experience. They are full of wisdom and things that work to make our lives easier. But, in the real world, you need more than reliable designs. This presentation will look beyond J2EE design patterns and will reveal an approach that will take you from a reliable design to a reliable implementation.
Keynote: hier downloaden!

Keynote am Mittwoch (12.5.), 11.45 Uhr
Software development has changed drastically since the Internet meltdown.What trends in methodology, process control and technology platforms haveemerged to complicate the task or enhance the software team’s ability tobring projects to market with higher quality in less time and with fewer resources? CMMI, Open Source software, Out-sourcing and Off-shoring all claim great benefits but could have hidden costs and pitfalls that can derail those projects with the best planning. Understanding change and howto properly respond to the human factors, economic conditions and increased time pressures can be a reliable predictor of a successful or unsuccessful software project.
Keynote: hier downloaden!

Keynote am Mittwoch (12.5.) 17.15 Uhr
The focus of Enterprise JavaBeans 3.0 is on the simplification of EJBfrom the developer's point of view. This task forces us to take alook back at the evolution of the EJB architecture; its essential features; its successes and shortcomings; and how it needs to evolve to meet both the goals of simplification and the future needs of developers. With this perspective in mind, we will discuss work in progress in the EJB 3.0 Expert Group. Specific technical topics we will address include the role of metadata annotations; POJO/POJI models for beans; and simplification of the model for container-managed persistence. We will also examine some of the consequences of these changes and implications for EJB beyond 3.0.

Keynote am Donnerstag (13.5.) 11.45 Uhr
Covering the recent introduction of the Portal Specification 1.0 (formerlyJSR 168) and its impact on portal development and the vendor market Eddie Budgen will: 1) explore the critical role that identity plays in securely delivering the right content and business processes to the right people inside and outsidethe enterprise. 2) discuss how SOA, and Web Services in particular, support the delivery of sophisticated business content to the portal. 3) see how Novell exteNd provides a platform to support this kind of modern portal development.
Keynote: hier downloaden!

Keynote am Donnerstag (13.5.) 12.30 Uhr
Software architecture is fundamental for a number of reasons: it is the key to understanding complex systems, it serves as a blueprint that drives implementation, and, perhaps most importantly, it determines a system’s ability to evolve in response to new requirements. In this talk, we first list the requirements for an architectural description language; that is, a language that can be used to specify software architectures. Next, we describe some recent developments in the Unified Modeling Language that allow it to be used both as an architectural description language and as an architectural enforcement facility. Enforcement is particularly significant because of "architectural decay" - the phenomenon of gradual but potentially dangerous deterioration of software due to low-level maintenance activity.