/*============================================================================*\
|                                                                              |
|                SOA4D DPWSCore Dynamic Deployment version                     |
|                                                                              |
|           ->>  Copyright 2004-2009 Schneider Electric SA <<-                 |
|                                                                              |
\*============================================================================*/

=============================================
== Dynamic deployment module Release Notes ==
=============================================

*****************
**   VERSION   **
*****************

MODULE VERSION: 1.0.2

This file contains:

1. A brief description for the module changelog,
2. The module changelog,
3. Know issues.

*******************
**  DESCRIPTION  **
*******************

The Dynamic Deployment version of DPWSCore extends the base version, bringing
the following features:

- File configuration (no need to harcode the devices in the code anymore),
- Dynamic deployment through the WS-Management protocol (deployment of service
  classes, devices & services),
- Reference management (ability to define in the configuration logical
  references that will relieve a service code to manage WS-Discovery).


********************************
**  CHANGE LOG & NEW FEATURES **
********************************

2.1.0

- New configuration file schema to allow configuration for most available
  parameters.
- Dynamic deployment attributes with default values not always generated
  anymore.
- SGXP:
  + error code macros renamed from EPX_ERR_ to SGXP_ERR_.
  + attribute can now be ignored (NULL callbacks tolerated).
- Error in wake up datagram reception relayed.
- EPX:
  + epx_get_serializer_error API added.
- Obsolete dyndepl.wsdl removed from sources (since WS-Management and then
  WS-Transfer is used as a protocol).


--------------------------------------------------------------------------------
2.1.M6 (refactoring):

- API header file refactored.

* Fixes:

- Service class properties fixed (SOA4D bug #50).
- The service class attribute "mustSupply" was not saved when false which is
  not the default.

--------------------------------------------------------------------------------
2.1.M5 :

- API added for property value retrieval.
- Service class loader interface changed (a callback was added).
- Service and service class deletion triggered by the 'delete' management
  operation.

* Fixes:

- Bug that appeared only on some platform using the 'DynHome' sample during the
  configuration phase. Bug located in sgxp.c related to choice model group
  parsing (like reference element in dyndepl XML Schema).
- Some "handle reference" counters were not release by the dyndepl service
  preventing the effective destruction of configuration objects.

--------------------------------------------------------------------------------
2.1.M4 :

Publication.


******************
** KNOWN ISSUES **
******************
- When a device is modified using "hot-configuration", for instance by the
  dynamic deployment service, all services handles are changed but event
  subscriptions are not moved to the "new service". Furthermore, the
  application is not warned that handles have changed. A solution may be
  to send events using a stable ID attached to the service instead of the
  handle and let handles for configuration purpose only.
- EPX on gSOAP currently does not support mixed content.
- See SOA4D bug trackers for issues detected by the community.
