Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 238 Big Data Appliance
- 1.9K Data Science
- 450.2K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 544 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.8K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.5K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 154 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 436 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Session object in my own set of classes

Good afternoon
I work with the API for the desktop application.
I wrote for myself a small, so to speak, class library at a higher level of abstraction.
In many of my classes, access to the session of this application is required (you need to create a Session object and assign the current session from the application to it, and already work with these objects).
Tell me, please, how should I better organize access to this object?
I used to create a new session object in each class in the specified way, but then I decided that this code repeats, and that this is not very good, and began to pass this object to methods as a parameter. But now I don’t like it either, because this object is passed to many methods and this is also a repetition, and generally not very good when there are a lot of arguments in the methods.
I thought what a parent class could do, which will have this object as a static field, and at the very beginning of my program, assign the current session to this field of this class, and other classes will already have access to it without any additional code. You can make just a separate singleton class with a session. Which option is definitely better, I do not know.
Thanks in advance
Yours faithfully!