Skip to content

Prep for upcoming changes to the Abstract Beamline Interface#3

Merged
rhfogh merged 2 commits into
rhfogh:rhfogh_developfrom
pkeller:rhfogh_develop
Sep 22, 2025
Merged

Prep for upcoming changes to the Abstract Beamline Interface#3
rhfogh merged 2 commits into
rhfogh:rhfogh_developfrom
pkeller:rhfogh_develop

Conversation

@pkeller

@pkeller pkeller commented Sep 22, 2025

Copy link
Copy Markdown
  • In the very near future, there will be two changes on the Java side:
    • Package names in the ABI will change
    • ABI types and Py4jMessage will be imported into the default JVM view on the Java side instead of the Python side; Python code should use the unqualified class/interface names
  • This commit makes the Python code that interacts with the GPhL workflow insensitive to those changes

 - In the very near future, there will be two changes on the
   Java side:
   - Package names in the ABI will change
   - ABI types and Py4jMessage will be imported into the
     default JVM view on the Java side instead of the
     Python side; Python code should use the unqualified
     class/interface names
 - This commit makes the Python code that interacts with
   the GPhL workflow insensitive to those changes
@pkeller

pkeller commented Sep 22, 2025

Copy link
Copy Markdown
Author

Hopefully this is self-explanatory: I worked out how to get hold of the default Py4J JVM view on the Java side, and I can set up the imports there very easily. I have left the references to the constructors in astra.messagebus.messages.* as they are for the time being. As we discussed, we can look at those in the future, maybe for version 3 of the ABI.

 - Remove cruft that got into the code by accident
@rhfogh rhfogh merged commit f1285d3 into rhfogh:rhfogh_develop Sep 22, 2025
5 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants