-
Deprecated InterfacesInterfaceDescriptionThe preferred way is now to deploy the full-text mapping file directly in the Docbase in folder /System/Search/EOS Moreover, the mapping for DQL is deprecated. Only Full-text mapping should be used.
-
Deprecated FieldsFieldDescriptionAs of version 6.5, replaced by
DfContentTransferCapabilities.ASYNCHRONOUS_WRITE
.As of version 6.5, replaced byDfContentTransferCapabilities.PREDICTIVE_CACHING
.As of version 6.5, replaced byDfContentTransferCapabilities.READ
.As of version 6.5, replaced byDfContentTransferCapabilities.WRITE
.The alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers inDfcMessages
should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used insteadThe alphanumeric identifiers should be used instead
-
Deprecated MethodsMethodDescriptionas of DFC 5.2.as of DFC 5.2.As of DFC 5.3, replaced by one of the
get
methodsXxxx Operationas DFC 6.0.As of DFC 6.0, this value may be obtained programmatically by calling DfClient.getLocalClient().getClientConfig().getBoolean("dfc.tracing.enable").as of DFC 5.2.as of DFC 5.2.As of DFC 6.0, tracing is enabled/disabled by setting the configuration option "dfc.tracing.enable" in dfc.properties. This option is dynamic and changes in its value will take affect immediately. Tracing may be programmatically configured by setting the "dfc.tracing.enable" attribute on the typed object returned by IDfClient.getClientConfig().as of DFC 5.2.use isEnabled and isSurrogateGetEnabled methodsas of version D6, useIDfBocsConfig
for cache server config objects.as of version D6, useIDfBocsConfig
for cache server config objects.use setEnabled and setSurrogateGetEnabled methodsPlease useDfClient.getLocalClient()
insteaduse IDfAcsClient.addUnavailableAcsServer()session adoption is no longer useful without a separate DMCLuseIDfSessionManager
instead for session sharinguse IDfAcsClient.getAllNetworkLocations()use IDfAcsClient.getClientNetworkLocations()Please useIDfClient.getModuleRegistry()
insteaduse IDfAcsClient.getNetworkLocation()useIDfSessionManager
instead for session sharingReplaced by newSearchService(IDfSessionManager, String)session adoption is no longer useful without a separate DMCLThis internal attribute is not meaningful hereThe object is immutable. This method had no useful effect in previous versions.The object is immutable. This method had no useful effect in previous versions.The object is immutable. This method had no useful effect in previous versions.The object is immutable. This method had no useful effect in previous versions.DMCL passthrough should not be used anymoreDMCL passthrough should not be used anymoreDMCL passthrough should not be used anymoreuse getValidator and then call getValueAssistance on IDfValidator insteaduse getValidator and then call getValueAssistance on IDfValidator insteaduse getValidator and then call getValueAssistanceDependencies on IDfValidator insteaduse getValidator and then call getWidgetType on IDfValidator insteaduse getValidator and then call validateAll on IDfValidator insteaduse getValidator and then call validateAttrRules on IDfValidator insteaduse getValidator and then call validateAttrRules on IDfValidator insteaduse getValidator and then call validateAttrRules on IDfValidator insteaduse getValidator and then call validateAllObjRules on IDfValidator insteaduse getValidator and then call validateAllObjRules on IDfValidator insteadAs of DFC 5.3, replaced by IDfRelationType.getPermanentLink()As of DFC 5.3, replaced by IDfRelationType.setPermanentLink()useIDfSession.getSessionId()
instead.Please use Aspects instead for interface extension. They provide similar functionality but are safer and more robust.Please use Aspects instead for interface extension. They provide similar functionality but are safer and more robust.Please configure tracing using the ClientConfig objectIDfClient.getClientConfig()
No longer neededNo longer neededAs of DFC 5.2.5, replaced by getUserSourceAsString()As of DFC 5.2.5, replaced by setUserSourceAsString(String)Use getAllSearches(IDfSession) insteadUse getCurrentUserSearches(IDfSession) insteadAlphanumeric identifiers are now used instead of numeric error codesAlphanumeric identifiers are now used instead of numeric error codesUse DfPreferences instead.Alphanumeric identifiers are now used instead of numeric error codesAlphanumeric identifiers are now used instead of numeric error codesa second user argument is no longer supported by the server.a second user argument is no longer supported by the server.DFC 5.2. Use getSchema instead.5.3 SP15.3 SP1DFC 5.2DFC 5.2.DFC 5.2Since 5.1.
This method is deprecated to make usage consistent across the IDfXmlQuery and IDfQuery interfaces.DFC 5.2.5 The default value is 0 (zero), meaning that all rows will be returned.NOTE 1: the result DOM is loaded into memory
NOTE 2: with virtual documents (in nested representation) MaxRows
indicates the number of elements in the nested structure rather than
the number of row elements.
-
Deprecated ConstructorsConstructorDescriptionAlphanumeric identifiers are now used instead of numeric error codesAlphanumeric identifiers are now used instead of numeric error codesAlphanumeric identifiers are now used instead of numeric error codesAlphanumeric identifiers are now used instead of numeric error codesAlphanumeric identifiers are now used instead of numeric error codesAlphanumeric identifiers are now used instead of numeric error codes