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
There needs to be a Domino Java SDK downloadable from Maven.
Collections are using the Interator interface instead of supporting Java 8 when you need to traverse a Notes collection.
The problem with recycling has been solved for years: https://sourceforge.net/projects/recycler
But the API in my opinion is unfixable broken:
Thread B accesses database X
Thread A terminates
Thread B accesses db X again
-->> Object has been removed or recycled
Terminate initialised thread -->> server panic
This makes it dangerous to use the API in various contexts where thread creation is not within control of the developer, i.e. swing
We've developed an application that mainly consists of about 50,000 lines of Java code (not counting libraries). Dealing with the Domino Java API is a nightmare. My favourite would be a brand new API. Written in 100% pure Java, sitting directly on top of C API and being open source.
1. NotesDocument.getSecNumber().
2. Optional parameter boolean newInstance (take document from disk, not from cache) to getDocumentByUNID, getDocumentByID methods.
It's very necessary!
First and foremost the need to recycle.
Moving idea to product : Domino Designer
the problem with recycle() is being solved with v10: https://pbs.twimg.com/media/Dd5vuTMUwAAI_62.jpg:large
The new API should be available for both XPAGES as Java Agents.
The way you do iterations in the current API is cumbersome, it should be more like standard java iterations work. Also get rid of recycle()...
Both things are already solved in ODA.
Number one issue for me is dealing with Vectors. Java developers working with Domino tend to view this as a major lack of commitment/support to the product. Having new methods that return modern collection classes such as ArrayList would be a much needed improvement.
For other issues please see what OpenNTF Domino API addresses: https://oda.openntf.org/main.nsf/project.xsp?r=project/OpenNTF%20Domino%20API
Can you be more specific on what features you would like to have addressed in the JavaAPI ?