Deprecated API

Contents

• Deprecated Classes
• Deprecated Fields
• Deprecated Methods

Deprecated Classes

org.eclipse.core.runtime.PluginVersionIdentifier
clients should use Version instead

Deprecated Fields

org.eclipse.osgi.service.environment.Constants.ARCH_AMD64
use ARCH_X86_64 instead. Note the values has been changed to be the value of the ARCH_X86_64 constant.

org.osgi.service.metatype.AttributeDefinition.BIGDECIMAL
As of 1.1.

org.osgi.service.metatype.AttributeDefinition.BIGINTEGER
As of 1.1.

com.prosyst.util.ref.Log.debug
since osgilib verion 1.3.9 use set/get Debug

org.osgi.service.event.EventConstants.EXECPTION_CLASS
As of 1.1, replaced by EXCEPTION_CLASS

org.eclipse.osgi.service.resolver.BundleDelta.LINKAGE_CHANGED
this type is no longer valid

org.eclipse.osgi.service.resolver.BundleDelta.OPTIONAL_LINKAGE_CHANGED
this type is no longer valid

com.prosyst.util.ref.Log.printOnConsole
since osgilib verion 1.3.9 use set/get PrintOnConsole

Deprecated Methods

org.eclipse.osgi.service.resolver.StateObjectFactory.createBundleDescription(Dictionary, String, long)
use StateObjectFactory.createBundleDescription(State, Dictionary, String, long)

org.eclipse.osgi.service.resolver.StateObjectFactory.createBundleDescription(long, String, Version, String, BundleSpecification[], HostSpecification, ImportPackageSpecification[], ExportPackageDescription[], String[], boolean)
use StateObjectFactory.createBundleDescription(long, String, Version, String, BundleSpecification[], HostSpecification, ImportPackageSpecification[], ExportPackageDescription[], boolean, boolean, boolean, String, String[], GenericSpecification[], GenericDescription[])

org.eclipse.osgi.service.resolver.StateObjectFactory.createBundleDescription(long, String, Version, String, BundleSpecification[], HostSpecification, ImportPackageSpecification[], ExportPackageDescription[], String[], boolean, boolean, boolean, String, String, GenericSpecification[], GenericDescription[])
use StateObjectFactory.createBundleDescription(long, String, Version, String, BundleSpecification[], HostSpecification, ImportPackageSpecification[], ExportPackageDescription[], boolean, boolean, boolean, String, String[], GenericSpecification[], GenericDescription[])

org.eclipse.osgi.service.resolver.StateObjectFactory.createState()
use StateObjectFactory.createState(boolean)

com.prosyst.util.xml.XmlSerializer.endTag()
see XmlSerializer.endTag(String)

org.eclipse.core.runtime.IConfigurationElement.getAttributeAsIs(String)
The method is equivalent to the IConfigurationElement.getAttribute(String). Contrary to its description, this method returns a translated value. Use the IConfigurationElement.getAttribute(String) method instead.

com.prosyst.util.xml.XMLUtil.getAttributeNames(String)
use TagClass.getAttrList() instead

com.prosyst.util.xml.XMLUtil.getAttributeValue(String, String, int)
use TagClass.getAttrList() and TagClass.getAttribute(String attr) instead

com.prosyst.util.xml.XMLUtil.getAttributeValues(String)
use TagClass.getAttrList() instead

com.prosyst.util.xml.XMLUtil.getContent(TagClass, int, String)
use TagClass.getContent(int pos, String name) instead

org.mbs.services.metatype.MetaDataManager.getMetaTypeProviderXML(String)
use getMetaTypeProviderResource instead

org.eclipse.core.runtime.IExtensionPoint.getNamespace()
As namespace is no longer restricted to the contributor name, use IExtensionPoint.getNamespaceIdentifier() to obtain namespace name or IExtensionPoint.getContributor() to get the name of the contributor of this registry element.

In the past namespace was dictated by the name of the bundle. If bundle org.abc contributed registry element with Id of MyId, the namespace of the element was always set to org.abc, producing the qualified name of org.abc.MyId.

The namespace used to be the same as the bundle name. As a result, the IExtensionPoint.getNamespace() method was used both to obtain the name of the bundle and to obtain the namespace of a registry element.

Since 3.2, the extension registry allows elements to specify qualified name. The extension point of the plug-in org.abc could specify org.zzz.MyExtPoint as an Id. In this case, namespace name is org.zzz, but the contributor name is org.abc.

(The use of a simple Id is still a preferred way. Whenever possible, specify only the simple Id and let runtime take care of the rest.)

If your code used the IExtensionPoint.getNamespace() to obtain the name of the contributing bundle, use IExtensionPoint.getContributor(). The typical usage pattern here is to find a bundle name to obtain some information from the corresponding OSGi bundle. For example, deducing the file location specified as a relative path to the bundle install location would fall into this group.

If your code used the IExtensionPoint.getNamespace() to obtain the namespace of the registry element, use IExtensionPoint.getNamespaceIdentifier(). Typically, this is the case when code is trying to process registry elements belonging to some logical group. For example, processing notifications for all elements belonging to the org.abc namespace would fall into this category.

org.eclipse.core.runtime.IExtension.getNamespace()
As namespace is no longer restricted to the contributor name, use IExtension.getNamespaceIdentifier() to obtain namespace name or IExtension.getContributor() to get the name of the contributor of this registry element.

In the past namespace was dictated by the name of the bundle. If bundle org.abc contributed registry element with Id of MyId, the namespace of the element was always set to org.abc, producing the qualified name of org.abc.MyId.

The namespace used to be the same as the bundle name. As a result, the IExtension.getNamespace() method was used both to obtain the name of the bundle and to obtain the namespace of a registry element.

Since 3.2, the extension registry allows elements to specify qualified name. The extension point of the plug-in org.abc could specify org.zzz.MyExtPoint as an Id. In this case, namespace name is org.zzz, but the contributor name is org.abc.

(The use of a simple Id is still a preferred way. Whenever possible, specify only the simple Id and let runtime take care of the rest.)

If your code used the IExtension.getNamespace() to obtain the name of the contributing bundle, use IExtension.getContributor(). The typical usage pattern here is to find a bundle name to obtain some information from the corresponding OSGi bundle. For example, deducing the file location specified as a relative path to the bundle install location would fall into this group.

If your code used the IExtension.getNamespace() to obtain the namespace of the registry element, use IExtension.getNamespaceIdentifier(). Typically, this is the case when code is trying to process registry elements belonging to some logical group. For example, processing notifications for all elements belonging to the org.abc namespace would fall into this category.

org.eclipse.core.runtime.IConfigurationElement.getNamespace()
As namespace is no longer restricted to the contributor name, use IConfigurationElement.getNamespaceIdentifier() to obtain namespace name or IConfigurationElement.getContributor() to get the name of the contributor of this registry element.

In the past namespace was dictated by the name of the bundle. If bundle org.abc contributed registry element with Id of MyId, the namespace of the element was always set to org.abc, producing the qualified name of org.abc.MyId.

The namespace used to be the same as the bundle name. As a result, the IConfigurationElement.getNamespace() method was used both to obtain the name of the bundle and to obtain the namespace of a registry element.

Since 3.2, the extension registry allows elements to specify qualified name. The extension point of the plug-in org.abc could specify org.zzz.MyExtPoint as an Id. In this case, namespace name is org.zzz, but the contributor name is org.abc.

(The use of a simple Id is still a preferred way. Whenever possible, specify only the simple Id and let runtime take care of the rest.)

If your code used the IConfigurationElement.getNamespace() to obtain the name of the contributing bundle, use IConfigurationElement.getContributor(). The typical usage pattern here is to find a bundle name to obtain some information from the corresponding OSGi bundle. For example, deducing the file location specified as a relative path to the bundle install location would fall into this group.

If your code used the IConfigurationElement.getNamespace() to obtain the namespace of the registry element, use IConfigurationElement.getNamespaceIdentifier(). Typically, this is the case when code is trying to process registry elements belonging to some logical group. For example, processing notifications for all elements belonging to the org.abc namespace would fall into this category.

com.prosyst.util.xml.XMLUtil.getTagName(String)
use TagClass.getName() instead

org.eclipse.core.runtime.IConfigurationElement.getValueAsIs()
The method is equivalent to the IConfigurationElement.getValue(). Contrary to its description, this method returns a translated value. Use the IConfigurationElement.getValue() method instead.

com.prosyst.util.timer.Timer.notifyAfter(TimerListener, int, int)

com.prosyst.util.timer.Timer.notifyAfter(TimerListener, int, int, int)

com.prosyst.util.timer.Timer.notifyAfterMillis(TimerListener, int, long, int)

com.prosyst.util.timer.Timer.notifyAfterMillis(TimerListener, long, int)

org.eclipse.osgi.service.resolver.StateObjectFactory.readState(DataInputStream)
use StateObjectFactory.readState(File) instead

org.eclipse.osgi.service.resolver.StateObjectFactory.readState(InputStream)
use StateObjectFactory.readState(File) instead

com.prosyst.mbs.services.db.DBManager.save()

org.eclipse.osgi.service.resolver.StateObjectFactory.writeState(State, DataOutputStream)
use StateObjectFactory.writeState(State, File) instead

org.eclipse.osgi.service.resolver.StateObjectFactory.writeState(State, OutputStream)
use StateObjectFactory.writeState(State, File) instead