Andy, the static code generation was an old experiment and is not used.I have been meaning to remove it for some time as it is confusing being there.
The get/setUserData was actually put in there at the request of the PHP-SDO team. I'm not sure of the details but I think they use this to maintain a correlation between the C++ SDO objects and PHP objects??? This code is not used anywhere within Tuscany SDO (or SCA) code. This may be a case where a real life application has shown up a limitation in the spec and that we should take a proposal to the spec group. I'll try and find out how essential this function is and if there is another way to work around this to enable a spec compliant api in Tuscany Cheers, On 17/07/07, Andy Grove <[EMAIL PROTECTED]> wrote:
I'm currently looking at some of the issues that my collegaue, Michael Yoder, raised regarding the use of propietary methods in the SDO header files. In particular, I'm looking at the setUserData / getUserData methods in DataObject.h [TUSCANY-1370]. These methods could easily be moved to the DataObjectImpl.h header instead. The methods are only referenced in code generated static client code (generated by DataFactoryImpl::generateInterface). However, I'm nervous about making the change because the current sdotest suite does not excercise the static code generated classes enough to call these methods. For instance, if I change the code generator to call a non-existant method "foo" instead of getUserData or setUserData then the current tests still pass. What is the status of the code generator? The Tuscany web site (http://incubator.apache.org/tuscany/sdo-cpp-faq.html) states that there are no plans to support this feature. Is this correct? Thanks, Andy.
-- Pete --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
