-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Domino Visual Editor] Java Agent Support #1018
Comments
I check this into details, I found we must need the Java Agent.ja file in the
|
I created a test database to test plain Java agents. For future updates (i.e. Script Libraries) I can update the database at: The agents are:
Each agent will print a message matching the name to the Java Debug Console. |
I got new some require from Justin on last Friday : I work around this in today , I got some Java agent and Lotus Script agent export.
For Formula Agent: |
Document selection xml:
|
I haven't used the document selection filter for Formula agents, so let's use the default for now and come back to this later. I'd like to get basic examples working for the other agent types before we go too deep into one type. |
LotusScript agent example:
|
I also use the Security tab frequently: In particular, I need to change the Runtime Security Level in order to run some agents. I haven't used the "Default access" section. The user list here will probably need to be populated by the user in the initial version, but we may be able to populate it based on the target server with a solution based on #1240. Java Agents also support Document Selection, but only when the Target is "All selected documents". See the notes above for this feature in Formula agents: |
For the "Run on" property, Designer shows these options:
For our implementation, have "Other" show a new text input where the server can be entered freely. Once we implement #1240, we can use the server list defined in Moonshine, but I think we would still want the text-input option. |
Lotus Script agent example
|
@feather812002 reported two Trigger options that had additional settings. He is already working on these: |
We would like to add support for Java Agents in Domino Visual Editor. The user will need to be able to edit the Java files normally, with language server support. The Java files will need to be compiled into the nsfodp project.
We will want to make it easy to have shared Java code in Script Libraries (#1019). If we don't make this part of the original implementation, we should make sure to add Script Library support soon after agents are available as a feature.
UPDATE: Branch: features/issue_1018_agent_support
The text was updated successfully, but these errors were encountered: