Software versioning is one of the most neglected areas of software development. We're all aware of the need for version control systems in development, but these systems are external to our source code.
How do you write software that withstands the test of time, software that does not have to be rewritten each time you change an interface, software that can still read persisted objects even if they were written by the last version of the application?
This session discusses some fanciful futuristic concepts as well as currently useful approaches to writing software that scales over time.
Alexander Krapf has over 20 years experience in software engineering, product development, and project management in the United States and Europe. He has been extensively involved in a variety of complex product development efforts using his in-depth understanding of .NET, C++, and Java. His successes have ranged from contributing SEC compliance components in the financial sector to managing the development of e-commerce servers for Hitachi Computer Products. In addition to founding and managing Codemesh, Alexander has worked for IBM, Thomson Financial Services, Hitachi, Veeder-Root, and Document Directions Inc., where he has been involved in product rollout, customer training, and customer relations for a diverse set of products and services.
Recognizing the need for easy to use, quality software integration products, Alexander co-founded Codemesh to satisfy a growing market need and his own entrepreneurial instincts. His history, with product successes as well as failures, has taught him what it takes to build a company with strong technology, firm business principles, and excellent customer support: CodeMesh.
Alexander Krapf received a Bachelor of Science degree in Electrical Engineering from the University of Stuttgart, Germany.
OSGi with Spring— Do you seek to to improve the modularity of your enterprise applications? Do you wish you could deploy multiple concurrent versions of services and applications? Do you require operational control over the life cycle of key application components? Interested in building on a proven component technology? If so, Spring on OSGi could be just the thing for you.
OSGi, the good the bad the ugly— The microService Architecture (mSA) Backplane is an OSGi-based infrastructure that will be the basis for many future software products from BEA. This project has been in development for about a year, and currently consists of about 100 different OSGi bundles that encompass functions such as logging, thread management, HTTP servlets, web services, and transaction management.
Stanley Ho JavaPolis 2006 interview— In this JavaPolis 2006 interview Ted Neward talks with Stanley Ho (JSR-277 specification lead) on the up coming Java Module System. In addition they also discuss the current and future state of Java Web Start.
Alexander Krapf 2006 JavaPolis Interview— Software versioning is one of the most neglected areas of software development. We're all aware of the need for version control systems in development, but these systems are external to our source code.
JSR-277 Java Module System— The JSR-277 (Java Module System) specification seeks to address many issues associated with Java Archives (JARs), including the lack of version control, the difficulties in distributing multiple JARs for deployment, the classpath hell, JAR hell, and extension hell, etc. that have been well known to many Java developers for years.
