#dominoforever | Product Ideas Portal


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

Allow JAR files to be used in Java agents

Currently we use JAR files in XPages but cannot use the same JAR in a Java agent without copying it but it won’t work anyways because of a memory leak bug when using JAR in a Java agent. One JAR file should be usable from XPages code and Java agents.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jul 15 2018
  • Likely to implement
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    February 28, 2019 10:15

    Putting Jars into ../ext is a bad option because it

    • reduces security
      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.
    • breaks design update
      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...
    • breaks database coexistence
      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.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    February 18, 2019 12:28

    We put jars in \..jvm\lib\ext

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    February 07, 2019 20:32

    JAR files for LS2J, also!

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 08, 2018 08:04

    Please see and vote for related idea https://domino.ideas.aha.io/ideas/NTS-I-54 

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    July 20, 2018 02:17

    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. 

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    July 18, 2018 09:41

    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.