Skip to content

JNI Marshal Method Generation, Registration #11939

Closed
Feature
Closed
JNI Marshal Method Generation, Registration#11939
Feature
Labels
Area: BindingsIssues in Java Library Binding projects.java-interopIssues migrated from dotnet/java-interop / relates to the Java.Interop subtreeneeds-triageIssues that need to be assigned.possibly-staleIssues that are potentially no longer relevant.

Description

@jonpryor
jonpryor
opened on Apr 7, 2015

"Big picture" method registration picture

  • Remove marshal methods from binding assemblies
  • Support three method registration approaches:
    • Fully dynamic, via System.Linq.Expresssions/Java.Interop.Export
    • Using the above jnimarshalmethod-gen.exe-generated marshaling assembly; see above.
      • This would be for non-AOT "Release" registration
    • Using generated C code.
      • Possibly most performant; for each method to register, we'd emit a Java_... method as per Java/native convention.
      • Allows using the default Java linker to resolve method symbols!
      • Generated C code would use mono_method_invoke()/etc. to invoke the jnimarshalmethod-gen.exe-generated marshal methods.

Activity

  1. jpobst
    added
    enhancementProposed change to current functionality.
    on Apr 16, 2020
  2. jonpryor
    added 8 commits that reference this issue on May 4, 2022

    [Java.Base-Tests] Test Java-to-Managed invocations for Java.Base

    2947810

    [Java.Base-Tests] Test Java-to-Managed invocations for Java.Base

    bab160e

    [Java.Base-Tests] Test Java-to-Managed invocations for Java.Base

    fc0f953

    [Java.Base-Tests] Test Java-to-Managed invocations for Java.Base

    0399f91

    [Java.Base-Tests] Test Java-to-Managed invocations for Java.Base

    538f429

    [Java.Base-Tests] Test Java-to-Managed invocations for Java.Base

    2b75b66

    [Java.Base-Tests] Test Java-to-Managed invocations for Java.Base

    bd1cce6

    [Java.Base-Tests] Test Java-to-Managed invocations for Java.Base (#975)

    4787e01
  3. jonpryor
    added a commit that references this issue on Feb 1, 2023

    [Java.Interop.Tools.Expressions] Add Java.Interop.Tools.Expressions

    e510fbb
  4. jonpryor
    added 6 commits that reference this issue on Feb 8, 2023

    [Java.Interop.Tools.Expressions] Add Java.Interop.Tools.Expressions

    7ab1209

    [Java.Interop.Tools.Expressions] Add Java.Interop.Tools.Expressions

    132e49c

    [Java.Interop.Tools.Expressions] Add Java.Interop.Tools.Expressions

    eca8388

    [Java.Interop.Tools.Expressions] Add Java.Interop.Tools.Expressions

    20fa0aa

    [Java.Interop.Tools.Expressions] Add Java.Interop.Tools.Expressions

    d176b58

    [Java.Interop.Tools.Expressions] Add Java.Interop.Tools.Expressions

    32e7f55
  5. jonpryor
    added 2 commits that reference this issue on Feb 23, 2023

    [Java.Interop.Tools.Expressions] Add Java.Interop.Tools.Expressions

    6247614

    [Java.Interop.Tools.Expressions] Add Java.Interop.Tools.Expressions (#…

    77800dd
  6. jpobst
    added the
    Feature
    issue type on Apr 29, 2025
  7. jpobst
    removed
    enhancementProposed change to current functionality.
    on Apr 29, 2025
  8. jonathanpeppers
    added
    java-interopIssues migrated from dotnet/java-interop / relates to the Java.Interop subtree
    needs-triageIssues that need to be assigned.
    Area: BindingsIssues in Java Library Binding projects.
    on Jul 1, 2026
  9. jonathanpeppers
    transferred this issue fromdotnet/java-interopon Jul 1, 2026
  10. jonathanpeppers
    added
    possibly-staleIssues that are potentially no longer relevant.
    on Jul 1, 2026

  11. dotnet-policy-service commented on Jul 1, 2026

    @dotnet-policy-service
    dotnet-policy-servicebot
    on Jul 1, 2026 – with Dotnet Policy Service

    We suspect this issue is stale and no longer relevant. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

  12. dotnet-policy-service commented on Jul 15, 2026

    @dotnet-policy-service
    dotnet-policy-servicebot
    on Jul 15, 2026 – with Dotnet Policy Service

    This issue will now be closed since it had been marked "possibly-stale" but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.

  13. dotnet-policy-service
    closed this as completedon Jul 15, 2026
  14. github-actions
    locked and limited conversation to collaborators on Aug 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area: BindingsIssues in Java Library Binding projects.java-interopIssues migrated from dotnet/java-interop / relates to the Java.Interop subtreeneeds-triageIssues that need to be assigned.possibly-staleIssues that are potentially no longer relevant.

    Type

    Feature

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions