如何实例化多个OSGi服务？

发布于 2024-10-31 21:05:59 字数 530 浏览 5 评论 0原文

在 Eclipse RCP 应用程序的上下文中，我决定使用 OSGi 服务从插件（即捆绑包）中提供“接口”。

在我的一个插件中，我有以下解析器接口：

public interface Parser {

    public void start(File file);

    public boolean hasNext();

    public Object next();
}

消费者插件将使用此接口来解析文件。因为可以同时完成多个解析，并且因为该接口的实现将需要多个“状态”私有字段，所以该服务的每个使用者必须使用专用的服务实例。

在这种情况下，manu OSGi 教程提供的默认解决方案（包括在解析器包的启动方法中注册一个服务实例）不起作用。处理这种解决方案的最佳解决方案是什么？我可以使用一种独特的方法创建 ParserFactory 服务：

public Parser create(File file);

有什么意见欢迎留言，

原文

In the context of an Eclipse RCP application I decided to use OSGi services to provide "Interfaces" out of a plugin (i.e a bundle).

In one of my plugin I have the following Parser interface:

public interface Parser {

    public void start(File file);

    public boolean hasNext();

    public Object next();
}

Consumer plugins will use this interface to parse files. Because several parsing can be done in the same time and because an implementation of this interface will need several "state" private field each consumer of this service must use a dedicated service instance.

In this case, the default solution provided by manu OSGi tutorials consisting in registering ONE service instance in the start method of the parser bundle doesn't work. What is the best solution to handle such a solution ?
I can create a ParserFactory service with one unique method:

public Parser create(File file);

Any comment is welcome,

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

海的爱人是光 2024-11-07 21:05:59

正如您所建议的，我会将您的服务接口更改为解析器的提供者。

你的解析器只是一个迭代器，所以也许像

public interface ParserFactory<T> {

  /** Iterating on the returned object
   *  provides Ts parsed from the InputStream.
   *
   *  @param input must be closed by the returned object 
   *   when done iterating. 
   */
  Iterable<T> createParser(InputStream input);
}

使用输入流或读取器这样的东西也使它比需要文件更灵活。

As you're suggesting, I would change your service interface to be a provider of Parsers.

And your Parser is just an Iterator, so maybe something like

public interface ParserFactory<T> {

  /** Iterating on the returned object
   *  provides Ts parsed from the InputStream.
   *
   *  @param input must be closed by the returned object 
   *   when done iterating. 
   */
  Iterable<T> createParser(InputStream input);
}

Using an InputStream or Reader also makes it more flexible that requiring a File.

回复收藏 0 原文