Here’s a final look at the SunNetwork 2000 Conference and Pavillion and its remaining schedule, including keynotes, sessions and BOFs. Also, here are today’s SunNetwork 2002 sessions.
Today’s sessions of interest to me include the following:
The Java CardTM specifications enable JavaTM technology to run on smart cards and similar devices with extremely limited memory. With more than 200 million cards already deployed, the Java Card API allows applications written for one Java Card technology-enabled smart card platform to run on any other Java Card technology-enabled platform. This session details the recent Java Card 2.2 release, which is a technology evolution release following the Java Card 2.1 release in Nov 1999, Java Card 2.1.1 release in May 2000, and Java Card 2.1.2 release in April 2001. The Java Card 2.2 release addresses ease-of-programming issues by providing RMI support and a modular deployment framework, which makes programming the card as well as the terminal easier. It addresses some of the real world deployment issues such as applet and package deletion, and introduces support for logical channel access to smart cards to enable the 3G phone market to use multiple USIM card applications simultaneously. These features bring value to 3G, IT infrastructure and financial markets, yet the release remains completely backward compatible with previous specifications.
Implementing Web Services with JavaTM API for XML Messaging (JAXM) and the Java Web Services Developer Pack (Java WSDP) — This developer-oriented session presents the JavaTM API for XML Messaging (JAXM) programming model for Web Services. After an architectural overview of JAXM, this session will take the audience through the steps required to develop two types of JAXM client applications (with or without a provider), the details of the JAXM programming model through code/demo walkthroughs, and configuration and deployment on the Java Web Services Developer Pack (Java WSDP), which is an integrated and production-quality tool set that will help Java developers to build, test, and deploy Web Services. The difference between the two JAXM clients, the relationship with JAX-RPC and JMS, the SOAP 1.1 with attachments API for Java (SAAJ), and message profiling will be discussed in the context of the Java 2 Platform, Enterprise Edition (J2EETM) component models. This session is intended for developers planning to either implement JAXM, build/extend JAXM profiles, or develop SOAP 1.1-based messaging applications by using Java WSDP. After the session, developers are expected to be able to start JAXM Web Services development.
JXTA in the Enterprise — The open source Project JXTA (www.jxta.org) defines a set of network protocols to establish a virtual ad hoc, peer-to-peer network overlay on top of existing physical networks. The JXTA virtual network standardizes the manner in which peers discover each other, self-organize into peergroups, advertise and discover published network resources (cpu, disk, contents), communicate, and monitor one another. The JXTA network is built out of five abstractions that hide the underlying network complexity and topology: homogeneous peer ID addressing, peergroups that define spontaneous secure virtual domains, a uniform resource advertisement description, a resolver to bind a resource to a physical peer, and pipes as virtual communication channels between peers. This session will discuss security and network infrastructure issues faced when deploying JXTA in a corporate network. We will describe how a JXTA corporate network (Relay and Rendezvous peers) can be configured to address various enterprise security requirements, and how the JXTA network can be integrated with existing enterprise services (directory, monitoring and authentication services). We will cover a number of JXTA enterprise services that recently have been contributed by the JXTA community to help the integration of JXTA into an enterprise network such as an LDAP-based naming service, a JavaTM Authentication and Authorization Service-based peergroup authentication service and a SOAP/Web bridge service.
Of course, there are others today like Java and SAP, Web Services Development using Sun ONE, Liberty, Jini and much more. How does one choose? Anyway, I have to say that this conference is a success. I only wish I could come on Friday when Bill Joy and James Gosling keynote, in addition to another day of choice SunNetwork 2002 Friday sessions. Enjoy!