Sat, 6 January 2007 Most of the attention around SOA has focused on its application to the
very largest enterprises. This focus is understandable - these
megacorps are the ones that have the most to gain or lose from a new
architecture (and also the biggest consulting budgets) - but it has
meant that the issues and requirements of smaller enterprises have
often been overlooked in SOA discussions. This is especially true in
areas such as governance, where the requirements of the largest
enterprises are very different from those of their smaller kindred.
Applying SOA guidelines based on requirements that aren't appropriate
for your business leads to governance bloat and bureaucracy. In this
presentation you'll see how to apply SOA in a more agile fashion to
allow small and mid-sized enterprises to gain the benefits of flexible
service components without the governance overhead often associated
with SOA. |
Sat, 6 January 2007 Web services are perceived as the ubiquitous solution to interoperable integration both within and across company boundaries. But despite their name, Web services don't build on the Web - on the contrary, to a large degree, they ignore the principles that have turned the Web into the world's most successful, scalable,distributed and loosely-coupled application. The presentation will introduce the principles of REST (REpresentational State Transfer), the Web's architecture, and address how to map advanced enterprise scenarios to an architecture that uses HTTP and the Web instead of abusing it. Comments[0] |
Fri, 5 January 2007 |
Fri, 5 January 2007 |
Fri, 5 January 2007 We have proposed to add Closures to the Java Programming Language. Closures simplify the use of APIs that rely on the use of anonymous class instances, such as the concurrency APIs and callbacks. More importantly, closures support control abstractions, which are APIs that act as programmer-defined control constructs. This JavaPolis talk describes the proposed language extension and its design rationale, and shows how it will affect existing and future APIs. |
Fri, 5 January 2007 |
Fri, 5 January 2007 |
Fri, 5 January 2007 The recently-released EJB 3.0 specification has perhaps been one of the most talked-about technologies that has emerged from JCP for some time. At the center of attention is the Java Persistence API, a lightweight persistence model that acts as a point of convergence for the dominant persistence products currently on the market. Standardization of persistence inside of the Java EE platform, as well as in the SE environment, will finally provide enterprise applications with the ability to write to one API and be able to run on the vendor of their choice. This talk covers the core concepts of the API and describe how it can be used in applications. |
Fri, 5 January 2007 Standardization of persistence inside of the Java EE platform, as well as in the SE environment, will finally provide enterprise applications with the ability to write to one API and be able to run on the vendor of their choice. This talk covers best practices and common usage patterns of the Java Persistence API in conjunction with a Java EE application server. |
Most of the attention around SOA has focused on its application to the
very largest enterprises. This focus is understandable - these
megacorps are the ones that have the most to gain or lose from a new
architecture (and also the biggest consulting budgets) - but it has
meant that the issues and requirements of smaller enterprises have
often been overlooked in SOA discussions. This is especially true in
areas such as governance, where the requirements of the largest
enterprises are very different from those of their smaller kindred.
Applying SOA guidelines based on requirements that aren't appropriate
for your business leads to governance bloat and bureaucracy. In this
presentation you'll see how to apply SOA in a more agile fashion to
allow small and mid-sized enterprises to gain the benefits of flexible
service components without the governance overhead often associated
with SOA.
