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

Đang mở
  • Có gì không ổn?
#2,022 2 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

@devin-ai-integration đang làm issue này rồi.

Từ ngày 7/11/2026.

  • #2041 của @devin-ai-integration — đang mở

Đánh giá

Độ khó
4/5
Thời gian dự kiến
3-5 ngày
Mức phù hợp với người mới
42/100
Loại issue
Tính năng
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
go, java, python
Lĩnh vực
api, backend

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

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
Ngôn ngữ chính
Go
Star
56
Fork
17
Merge trung bình
12 giờ 45 phút
Pull request đã merge (30 ngày)
910

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của Open-MBEE/OpenSysML

Tất cả issue của Open-MBEE/OpenSysML

Issue tương tự

Thêm issue về Go

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.