Java client: no member enumeration, no GetElementProperties, no instance paths

オープン
  • 何か問題がありますか？
#2,022 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@devin-ai-integration がすでに取り組んでいます。

2026年11月7日 から。

  • #2041 @devin-ai-integration による — オープン

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
42/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
go, java, python
領域
api, backend

調査の方向性

Start in client/java, especially internal/Protos.java and the Java Symbol, Model, and Instance APIs; compare the listed Python and Go methods and the protobuf fields and RPC messages. Implement member decoding, element-properties access, and instance-path access with the suggested fields and options. Done means Java callers can retrieve these data through public APIs, matching the documented behavior of the Python and Go clients.

索引モデルが issue の本文から書いたものです。

説明

enhancement

This issue was written with AI help. The results were produced against the version below.

The Java client (client/java) is the binding for JVM hosts: Eclipse-based tools, Cameo plugins, web services. Three features the service already serves, and the Python and Go clients expose, are missing from it:

feature service Python Go Java
SymbolInfo.members (#1974, capability symbol_members) yes Symbol.members() Symbol.Members dropped: Symbol has no members
GetElementProperties (#2013, capability element_properties) yes Model.element_properties() Client.ElementProperties no method
InstancePaths and Instance.reached_by (#1979) yes Instance.paths(), .path, .owner Client.InstancePaths no method; Instance is id, type and feature values

The data is already there: the generated protobuf classes contain SymbolInfo.members and the GetElementProperties messages, and Capabilities names SYMBOL_MEMBERS and ELEMENT_PROPERTIES. But internal/Protos.java never reads members, and no public method calls either RPC.

What it costs a Java user

We run the same 1630 static reads through every client, with the Pilot as oracle (https://github.com/hideo67/sysmlv2-tests, suite opensysml-java). Over sysml-grpc at 19bc16d1df:

client API pass fail unsupported
Python Symbol API, with members() 652 222 747
Go Symbol API, with Members 642 232 747
TypeScript Symbol API, no members 542 326 753
Java Symbol API, no members 542 326 753
Python, Go element_properties 1236 323 62

The Java client gives the same answer as the TypeScript client on every case. Where it gives the wrong answer, the decoding is not at fault; the information never reaches the caller:

  • Inherited members are invisible. With part def Base { part p; } part def Mid :> Base; and part m : Mid;, m's inherited p is not among childIds() or attributes(). 94 cases that Go passes fail in Java: inherited parts, ports, connections, parameters and annotations read through a usage or a specialization (our matrices A10, A30, A40, B12, B20, C01, C10, C30, D10).
  • No route to most of the metamodel. Through element_properties, Python and Go answer 470 reads that the Symbol API has no field for (connector ends, send action arguments, value expressions, state entry/do/exit actions, documentation, ...). A Java user has no route to any of them.
  • No owner path of an object. Instance does not say how it was reached, and there is no way to ask for its paths, so an object reached through a connector end cannot be traced back to its owner (6 more cases Go passes).
Suggestion
  • Add List<Member> members() to Symbol, read from SymbolInfo.members, with inherited, inheritedFrom and withheldLibraryMembers, and an option for include_library_members, like Python's members(inherited=True, library=True).
  • Add Model.elementProperties(String element, String... properties), returning element references with the id the call accepts back, like Python and Go.
  • Add reachedBy, owner, path to Instance and Model.instancePaths(Instance).

The TypeScript client also lacks members and instance paths (it has element_properties). A shared checklist of service features versus client bindings might help keep the bindings level.

Version
  • OpenSysML develop at 19bc16d1df (nightly-199-g19bc16d1df)
  • Java client 0.12.1 from client/java of the same commit (mvn -f client/java/pom.xml install), JDK 21; bin/sysml-grpc from make build-grpc
  • Suite: https://github.com/hideo67/sysmlv2-tests, test-suite/test-opensysml-java
主要言語
Go
スター
56
フォーク
17
平均マージ
12時間 45分
マージ済み PR（30日）
910

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Open-MBEE/OpenSysML のほかの issue

Open-MBEE/OpenSysML の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。