Hi all,
I just want to point-out that the semantic of what you are proposing here is a little bit more complex. Your code stores as operational data the assigned id-values at the time of the last execution of the service create(). This may not be the same as the current allocation from the resource manager as the service could be "out-of-sync".
If what you need is the current allocation value for that service instance without copying any value, you should be able to use the tailf:link extension as long as you can compose the target path (like if the pool and allocation name is well-know for your service model). Another option would be via a data provider.
Roque
tailf:link target
This statement specifies that the data node should be implemented as a link to another data node, called the target data node. This means that whenever the node is modified, the system modifies the target data node instead, and whenever the data node is read, the system returns the value of target data node.
Note that if the data node is a leaf, the target node MUST also be a leaf, and if the data node is a leaf-list, the target node MUST also be a leaf-list.
Note that the type of the data node MUST be the same as the target data node. Currently the compiler cannot check this.
The argument is an XPath absolute location path. If the target lies within lists, all keys must be specified. A key either has a value, or is a reference to a key in the path of the source node, using the function current() as starting point for an XPath location path. For example:
/a/b[k1='paul'][k2=current()/../k]/c
The link statement can be used in: leaf and leaf-list.
The following substatements can be used:
tailf:inherit-set-hook This statement specifies that a 'tailf:set-hook' statement should survive through symlinks. If set to true a set hook gets called as soon as the value is set via a symlink but also during commit. The normal behaviour is to only call the set hook during commit time.
