Customization of the EyeDB schema driven CORBA binding
the traditional CORBA binding is restrictive
a one-to-one mapping may not be needed:
- for example some attributes do not need exportation
- schema may reflect implementation constraint
- the CORBA view may have a more simple or a more pertinent semantics
- sometimes the starting point is the CORBA IDL
we need to customize! How to make it simply?