C++ SDO spec compliance/portability: DataObject
-----------------------------------------------

                 Key: TUSCANY-1370
                 URL: https://issues.apache.org/jira/browse/TUSCANY-1370
             Project: Tuscany
          Issue Type: Bug
          Components: C++ SDO
         Environment: API issues -- all platforms
            Reporter: Michael Yoder


The specification interface DataObject.h exposes off-spec member functions, 
these should be made internal to the implementation.

 

-----Original Message-----
From: Michael Yoder 
Sent: Thursday, June 21, 2007 6:34 PM
To: '[email protected]'
Subject: C++ SDO spec compliance/portability: DataObject

Hi,

In the DataObject interface, these member functions are exposed which aren't in 
the C++ 2.1 spec:

    virtual SDO_API bool hasProperty(const char* name) = 0;
    virtual SDO_API bool hasProperty(const SDOString& name) = 0;

    virtual SDO_API DataFactory* getDataFactory() = 0;

    virtual SDO_API void setUserData(const char* path,void* value) = 0;
    virtual SDO_API void setUserData(const SDOString& path, void* value) = 0;
    virtual SDO_API void setUserData(unsigned int propertyIndex, void* value) = 
0;
    virtual SDO_API void setUserData(const Property& property, void* value) = 0;
    virtual SDO_API void setUserData(void* value) = 0;
    virtual SDO_API void* getUserData(const char* path) = 0;
    virtual SDO_API void* getUserData(const SDOString& path) = 0;
    virtual SDO_API void* getUserData(unsigned int propertyIndex) = 0;
    virtual SDO_API void* getUserData(const Property& property) = 0;
    virtual SDO_API void* getUserData() = 0;

    virtual SDO_SPI const char* objectToXPath() = 0;

Would it be appropriate to file a Jira/patch to have these removed from the 
spec interface? Or alternatively a Jira to submit them to the spec committee?

Thanks,

Michael Yoder
Rogue Wave Software - [EMAIL PROTECTED] Software Developer - HydraSDO

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to