The only problem I see at this stage is that this will require all schema classes to define an attribute that, via an annotation, is specified as the naming attribute.
That doesn't seem like a huge deai but it is a forced constraint on Gldapo users.
Luke Daley added a comment - 16/May/08 08:58 AM The only problem I see at this stage is that this will require all schema classes to define an attribute that, via an annotation, is specified as the naming attribute.
That doesn't seem like a huge deai but it is a forced constraint on Gldapo users.
Improvement
Resolved
Minor
When moving/replacing an object, the in memory value of the naming attribute should be updated to reflect the change
The only problem I see at this stage is that this will require all schema classes to define an attribute that, via an annotation, is specified as the naming attribute.
That doesn't seem like a huge deai but it is a forced constraint on Gldapo users.