Has anyone been successful in migrating version 3.1 components to version 5.1?
Thanks.

dhack45,
Depending on which components you are using there may be many fundamental changes made over 2 major and many, many point releases between 3.1 and 5.1.
Without core knowledge of the differences it may be more productive to use your existing 3.1 components as a template and recreate them using the wizards in 5.1. For example, many components now use a BizDriver which may not have in previous versions.
We have had successful migrations which have followed the course of the product from 3.7 to 4.5 and then to 5.x. If you encounter issues due to the significant gap between these versions, our Professional Services Team would be able to assist.

Has anyone published a table of differences between older versions of XAware to the lastest version? It would be quite handy to see this, especially on additional or deprecated features; e.g., xa-script attributes/elements, use of axis, functiods, etc., from 3.7 to 4.5 to 5.3.

I don't think anyone has compiled a "summary table" of changes, which would be a bit of an undertaking. Some of the information is available in various places, and we have been helping some customers with migrations on the forum, through support, and through services for very large migrations. The tasks migrating from 3.x to 4.x are quite different than migrating from 3.x/4.x to 5.x, but at this point any migrations should be to 5.x, since XAware 5 has been available for well over a year.

The underlying architecture for 5.x has changed considerably from 4.x, and is not backward-compatible (which was and is still the goal of point releases). From 3.x to 4.x, the Designer was also changed from a custom GUI to an Eclipse-based IDE, as in 5.x. In 5.x we have added many tutorials, examples, webinars and new wizards to our extensive documentation, as well as wikis and forum support. We recommend using these materials and/or taking our Basic Training course to better understand the XAware 5 features before attempting a migration.

We also have various places where you can find more information about migration, although it is not in a single, comprehensive table or guide. This includes:

- Release notes are included with every point release, which discuss new features

- The XAware5 Designer Help includes several sections which can assist understanding the differences, especially:
-- Basic XAware Know How
-- Using XAWare Designer (for those new to XAware 4 and XAware 5)
-- XAware Script Elements -> Deprecated Elements and Attributes (not comprehensive, but a good start)

- xaware.org -> About the Project lists some general information on the release of 5.0 and some components that were not ported from 4.x

- xaware.org contains this forum, specifically for migration questions and answers (inclunding examples from past customer migrations)

- xaware.org contains helpful wikis for XAware 5, including XAware Upgrade Information, which has some information on upgrading extensions and tips on XAware 5 point release upgrades.

I have also attached a document that compiles notes and some specific changes made, for a couple of customer migrations that XAware assisted. These are not complete, as these projects may have used a limited set of BizComponents. Some of these notes include changes that were made to bring the migrated applications in line with a how a newly developed XAware 5 implementation might be developed and may not be required for a migrated application merely to function in XAware 5 (such as path expressions). (Note that this document was written using 5.3 GA, and some additional enhancements have been made to 5.4 that will make some of the migration items in this doc easier.)

You may want to consult with XAware before starting a migration; we can help to review your application and identify what changes might be required. It is also important to identify whether you want to migrate your apps to take advantage of new features and best practices using XAware 5 to promote easier maintenance, or whether you can make the bare minimal migration leaving some "legacy" approaches that are still supported.