SDK Data Store Exceptions (17001 - 17006)

SDKDataStoreException is a run-time exception that is raised when SDK classes are used to customize TopLink.

Format

EXCEPTION [TOPLINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

Example 13-17 SDK Data Store Exception

EXCEPTION [TOPLINK – 17001]: oracle.toplink.sdk.SDKDataStoreException
EXCEPTION DESCRIPTION: The TopLink SDK does not currently support Cursor.

17001: UNSUPPORTED

Cause: A method call failed because it is not currently supported by the SDK.

Action: Avoid using the unsupported method.

17002: INCORRECT_LOGIN_INSTANCE_PROVIDED

Cause: An instance of oracle.toplink.sdk.SDKAccessor was passed the wrong type of Login (the SDK expects an instance of DatabaseLogin).

Action: Verify that your SDK-based application is being passed the expected type of Login.

17003: INVALID_CALL

Cause: When the QueryManager owned by an SDKDescriptor is initialized, an instance of InvalidSDKCall is set for each type of Call that is not configured. If you invoke an unconfigured Call, this INVALID_CALL error is logged rather than simply throwing a NullPointerException because the INVALID_CALL error contains more information.

Action: Avoid using the unconfigured Call or provide a Call implementation in your SDK-based application.

17004: IE_WHEN_INSTANTIATING_ACCESSOR

Cause: Failed to instantiate the specified class due to a java.lang.InstantiationException.

Action: Ensure that the specified class is not an interface or an abstract class.

17005: IAE_WHEN_INSTANTIATING_ACCESSOR

Cause: Failed to instantiate the specified class due to a java.lang.IllegalAccessException.

Action: Ensure that specified class is public. Ensure permission is set for Java reflection in your VM security settings.

17006: SDK_PLATFORM_DOES_SUPPORT_SEQUENCES

Cause: Unsupported SDKPlatform methods buildSelectSequenceCall or buildUpdateSequenceCall were called.

Action: Avoid using these methods or subclass SDKPlatform and override them with your own implementation.