Parleys.com

Ed Burns, co-spec lead for JavaServer Faces, gets interviewed at JavaPolis by our JavaPosse friends Dick Wall and Carl Quinn. During this interview Ed takes the opportunity to talk about his new book and of course about.. euh ... JSF

During this historic JavaPolis '07 discussion panel, James Gosling, Joshua Bloch, Neal Gafter, Martin Odersky and moderator Carl Quinn discuss the future of (Java) Computing and lots more. 'Why is immutable not part of the Java language' and 'How should the Java platform evolve?' are questions discussed by this very relaxed panel.

As agile software development techniques and concepts cross the 'technology adoption chasm' we find that the concerns on the right-hand side of the chasm are much different than those on the left.

We are now facing critical issues which until now many within the agile community have preferred to avoid talking about. Activities such as modeling, documentation, exploratory testing, and database development must become more explicit within our methodologies. We need to find ways to fit into IT governance frameworks, process maturity frameworks, and regulatory guidelines.

Other issues such as certification, enterprise architecture, enterprise business modeling, and outsourcing must also be addressed. Finally, we must help the business take a more active role in development, reform IT financing, and in general manage their IT portfolio effectively.

In this Groovy interview the JavaPosse members talk with Guillaume LaForge about the new features of version 1.5. They ask what he thinks about the Closures controversy and how it fits in the Groovy language. How can you leverage Groovy in an enterprise Java project using Grails and what books should we Groovy newbies read ?

Today's SOA practitioners find their greatest architecture challenges addressing reliability and scalability for composite applications and processing large payloads. This session presents a breakthrough design for SOAs that deliver continuous availability and linear scalability for services and applications. With new approaches that include middle-tier data caching, load balancing and HA through service-level grid enablement, you can make your SOA bullet-proof.

Java API for XML Web Services (JAX-WS) 2.1 takes web services support in the Java platform to the next level. JAX-WS expands support for web services development in Java EE 5 and Java SE significantly. By aligning with Binding (JAXB) 2.x, JAX-WS provides complete support for document-oriented web services, the XML Schema standard, and MTOM/XOP.

In this session, the speaker covers some more advanced features of JAX-WS 2.1, JAXB 2.1 and the RI, and shows you how they simplify the task of developing web services. We will take you well beyond the basic introduction of JAX-WS, and show you how problems people often face when developing web services can be addressed using JAX-WS. Handling schema and service evolution, automating corporate design guidelines, and extending protocol support beyond HTTP are just some of the things that are now possible with JAX-WS.

In November of 2006 Sun announced that it would publish the JDK source code under the GNU General Public License and build a community around that code. This talk will review the progress of that effort so far, show the different ways in which developers can get involved, and discuss what's yet to come.

Enterprise JavaBeans is an architecture for the development and deployment of component-based business applications. Applications written using the Enterprise JavaBeans architecture are scalable, transactional, and multi-user secure.

The Enterprise JavaBeans 3.0 specification focused on bringing ease-of-use to the EJB API. The purpose of the Enterprise JavaBeans 3.1 specification is to further simplify the EJB architecture by reducing its complexity from the developer's point of view, while also adding new functionality in response to the needs of the community.

The focus will be on the core session bean and message-driven bean component models and their client API. Although the Java Persistence API was developed within EJB 3.0, it will evolve under a separate JSR rather than within EJB 3.1.

Aspects that should be considered by the Expert Group for inclusion in this work include, but are not limited to, the following:

• Removal of the requirement for a separate local business interface.
• Support for direct use of EJBs in the servlet container, including simplified packaging options.
• Singleton beans.
• Support for asynchronous session bean invocation.
• Support for stateful web services via stateful session bean web service endpoints.
• Specification of concurrency options for stateful session beans.
• Application-level callback notifications, including for container initialization and shutdown.
• EJB Timer Service enhancements to support cron-like scheduling, deployment-time timer creation, and stateful session bean timed objects.
• An ejb-jar level component environment to simplify the specification of shared dependencies among components.

The goal of the Expert Group will be to investigate these issues and identify and pursue directions for enhancement to the overall programming model and facilities of the Enterprise JavaBeans API.

Enterprise Information Integration (EII) solutions can provide access to disparate sources of data in real-time while addressing physical and semantic data differences.
This session will let you discover what Enterprise Information Integration is and how it can be used to create data services, a primary building block of SOA-enabled architectures, where data is de-coupled and abstracted between the data source and the consumer, and where semantic mediation and other data processing takes place.

Organizations are adopting service oriented architecture (SOA) in an attempt to reduce cost, mitigate risk, improve efficiency, and increase agility. But many organizations are finding it difficult to realize these benefits and deliver a significant return on investment. This presentation will discuss the challenges that impede SOA adoption and provide suggestions for strategies that can mitigate risks and improve success rates.

Discover the basics of single sign-on and how SAML assertions are finding their way into projects like OpenSSO, NetBeans and Glassfish to secure web services. SAML V2.0, approved by OASIS in March 2005, is an XML-based framework for communicating user authentication, entitlement, and attribute information. Beyond defining the industry-standard protocol for cross domain Web single sign-on (SSO), SAML is a keystone of higher level specifications such as Web Services Interoperability Basic Security Profile (WS-I BSP), the Liberty Alliance's Identity Web Service Framework (ID-WSF) and even Microsoft's Cardspace.

JavaPolis organized a 25 minute Q&A keynote session with James Gosling. A nice opportunity for the European Java developers to ask the father of Java about 'where is Swing going', 'what do you feel about Android', 'what is the future of Java in the RIA space' and lots more. Enjoy!

This JSR will provide a new and improved date and time API for Java. The main goal is to build upon the lessons learned from the first two APIs (Date and Calendar) in Java SE, providing a more advanced and comprehensive model for date and time manipulation.

The new API will be targeted at all applications needing a data model for dates and times. This model will go beyond classes to replace Date and Calendar, to include representations of date without time, time without date, durations and intervals. This will raise the quality of application code. For example, instead of using an int to store a duration, and javadoc to describe it as being a number of days, the date and time model will provide a class defining it unambiguously.

The new API will also tackle related date and time issues. These include formatting and parsing, taking into account the ISO8601 standard and its implementations, such as XML. In addition, the areas of serialization and persistence will be considered.

The final goal of the new API is to be simple to use. The API will need to contain some powerful features, but these must not be allowed to obscure the standard use cases. Part of being easy to use includes interaction with the existing Date and Calendar classes, something that will be a key focus of the Expert Group.

An ESB is part of an SOA infrastructure. However, SOA is not simply a technology or a product: it's a style of design, with many aspects (such as architectural, methodological and organisational) unrelated to the actual technology. But obviously at some point it becomes necessary to map the abstract SOA to a concrete implementation and that's where JBossESB comes in to play!

Red Hat in conjunction with the open source community released JBoss ESB 4.2, a JBoss.org open source project. JBoss ESB intermediates interactions between enterprise applications, business services, business components, and middleware to integrate and enable automation of business processes.

In his presentation Johan will look at the architecture and benefits of the JBoss ESB. The main part of his talk will cover multiple demo's of some basic, as well as some more advanced features of the JBoss ESB.
Johan will conclude his session by presenting the current product roadmap. He will also explain why you should choose for JBoss ESB in future SOA projects.

SpringSource recently announced the release of Spring Web Services 1.0.

Spring Web Services 1.0 provides a flexible, powerful Web services framework by facilitating best practices such as contract-first Web service development, the WS-I basic profile, and loose coupling between contract and implementation, allowing for the creation of flexible Web services using one of the many ways to manipulate XML payloads. By providing developers with a simpler approach to contract-first development, Spring-WS resolves many of the interoperability issues associated with typical Web services approaches.

Join Arjen Poutsma in this session about this interesting new addition to the Spring portfolio!

One of the key outcomes of Java EE 5 / EJB 3.0 was the introduction of the Java Persistence API. JPA is a new standard API for Java persistence and object/relational mapping that supports use in both Java EE and Java SE environments.

The purpose of Java Persistence 2.0 is to augment the Java Persistence API to include further features requested by the community.

This session will give you an up-to-the-minute glimpse into work in progress on Java Persistence 2.0, and will provide you with an opportunity for feedback on new directions.

Aspects to be discussed include the following:

• Expanded modeling capabilities and object/relational mapping functionality, including support for collections of embedded objects, ordered lists, combinations of access types, greater flexibility in combining existing mapping options, etc.

• Expanded query capabilities and additions to the Java Persistence query language

• Standardization of additional contracts for entity detachment and merge, and persistence context management

• Standardization of sets of "hints" for entity manager and query configuration

• Expanded pluggability contracts for Java EE environments

• Support for validation

SpringSource recently announced the release of Spring Web Services 1.0.

Spring Web Services 1.0 provides a flexible, powerful Web services framework by facilitating best practices such as contract-first Web service development, the WS-I basic profile, and loose coupling between contract and implementation, allowing for the creation of flexible Web services using one of the many ways to manipulate XML payloads. By providing developers with a simpler approach to contract-first development, Spring-WS resolves many of the interoperability issues associated with typical Web services approaches.

Join Arjen Poutsma in this session about this interesting new addition to the Spring portfolio!

Learn how your organization can adopt an enterprise service oriented architecture (enterprise SOA) with a business process platform that provides enterprise services to compose and deploy solutions for your specific business processes.