Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
And if you need a jar file in multiple databases, how this will work ?
Wow! How long did we have to wait for IBM to react? 15 years, or even 20? Thanks HCL!
Now up to the next one (see anonymous post below dated March 04, 2021)
This feature is now available in Domino Designer 12.0.2
A great option would be to use Java/Сode design elements in Java-agents/services.
Putting Jars into ../ext is a bad option because it
Code in ../ext has AllPermission by default. This is of course a minor issue because any Java code on any Domino server can easily get AllPermission and escalate its Domino permissions to the servers. But moving code to ../ext opens the door for doing harm by mistake.
Putting a database on a new server and version updates will not work with default Domino tooling. And you might even be required to roll out your Jars to any client...
Two applications using different versions of the same library won't be able to live on the same server
Fun fact: The mentioned memory leak in agents occurs whether you attach jars or not. But without attached jars the agent is (in most cases) much smaller causing the leak to be acceptable or even not noticeable.
We've solved this issue by creating our own ClassLoader that makes Java scriptlibs accessible from everywhere.
We put jars in \..jvm\lib\ext
JAR files for LS2J, also!
Please see and vote for related idea https://domino.ideas.aha.io/ideas/NTS-I-54
The jar files stored in the nsf should work with XPages and agents. We shouldn’t have to resort to workarounds like \jvm\lib\ext to make this work and have to deal with that being wiped out when Domino is upgraded.
We put jar files in the \jvm\lib\ext folder on our Domino servers. This makes them available to agents and XPages. (You also need to add them to the \jvm\lib\ext folder on your Notes client for designer to be able to build). Make sure you keep a list of which jar files you've added! You'll need to put them back again when your admins upgrade Domino.