In this case, a global item class can be defined for the connector, to serve as a way to retrieve those properties that can always be accessed.
在这种情况下，可以为连接器定义一个全局项目类，作为对那些一直可以进行访问的属性进行检索的方法。
For each JAR file, it USES the ConnectorConfigBeanInfo class to determine the properties required by the connector.
对于每个JAR文件，它使用connectorconfigbeaninfo类判断连接器需要的属性。
The example OmniFind connector, included in the next article in this series, features a MimeTypeUtil class that determines the mimetype for content created by the connector.
在本系列的下一篇文章中会讲到OmniFind连接器示例，它提供一个MimeTypeUtil类为连接器所创建的内容确定 mimetype。
It is used when the client obtains a connection handle for an Encina Connector instance. With this class, the application specifies connection parameters.
当客户端获得对Encina连接器的连接处理时使用它。
You then need to add an instance of the rest source class for the connector to be fully functioning.
然后，您需要添加restsource类的一个实例，以便连接器可以完全发挥作用。
Thus, the OmniFind connector would only support a single, global item class for content and there could be an unlimited number of other ad-hoc properties per item.
所以，OmniFind连接器只为内容支持一种单一的全局项目类，这样每个项目可能会有无限多的专门的其他属性。
The "MX47 Series" utilizes a 3-row, 39-contact high-density array to achieve a smallest-in-class width and height for an automotive waterproof connector.
在“MX47系列”采用了3排，39接触高密度阵列实现类的宽度和高度为汽车防水连接一个最小合。
The "MX47 Series" utilizes a 3-row, 39-contact high-density array to achieve a smallest-in-class width and height for an automotive waterproof connector.
在“MX47系列”采用了3排，39接触高密度阵列实现类的宽度和高度为汽车防水连接一个最小合。
应用推荐