AMDS Progress

It's been a very busy day. I have been doing a little re-organization of the AMDS code base to make it more manageable and efficient. The project will be broken into four (4) components:

1. amds-common - contains all the request/response messages and associated data types as an interface
2. amds-rods-client - separate non-web client for the AMDS service
3. amds-web - this was already in work and represents a web-based client interface for the AMDS service
4. amds-rods-service - the actual service implementation

All projects except for the amds-rods-service use the Maven build system. In addition a common package naming scheme was agreed to for services created from this point forward. I also discovered that I can use the Eclipse Modeling Framework to translate the AMDS.xsd into Java classes. The generated class seems compatible with the code that Introduce produces. I will investigate this further after the amds-web project is completed to determine is this is a viable method for generating Introduce compatible code.