Page History
Developers Meeting on Weds, Dec 6, 2017
Info | ||
---|---|---|
| ||
|
...
Friendly reminders of upcoming meetings, discussions etc
- DSpace 7 Working Group (2016-2023): Next meeting is Dec 7 at 15:00 UTC in Google Hangouts. See wiki page for meeting details and past meeting notes.
- DSpace 7 UI Mockups - Watch this page for UI/UX mockups that are currently under discussion, etc.
- DSpace Entities Working Group (2017-18): Next meeting is TBD (January 2018). See wiki page for meeting details and past meeting notes.
...
If you have a topic you'd like to have added to the agenda, please just add it.
(Ongoing Topic) DSpace 7 Status Updates for this week
- Team is currently concentrating on building out search functionality & submission , submission, authentication and MyDSpace functionality
- Refactoring of submission configs notes at Configuration changes in the submission process
(Ongoing Topic) DSpace 6.x Status Updates for this week
DSpace 6.3 Release Planning is ongoing. Looking for more contributors!
Policy on @author tags in code?
- Discussion of rough draft of Proposed DSpace Java Style Guide
Tickets or Pull Requests requiring attention? (Please feel free to add any you wish to discuss under this topic)
...
- Updating code style & validating via CheckStyle : Code Style Guide (WIP)
- Management of database connections for DSpace going forward (7.0 and beyond). What behavior is ideal? Also see notes at DSpace Database Access
- In DSpace 5, each "Context" established a new DB connection. Context then committed or aborted the connection after it was done (based on results of that request). Context could also be shared between methods if a single transaction needed to perform actions across multiple methods.
- In DSpace 6, Hibernate manages the DB connection pool. Each thread grabs a Connection from the pool. This means two Context objects could use the same Connection (if they are in the same thread). In other words, code can no longer assume each
new Context()
is treated as a new database transaction.- Should we be making use of
SessionFactory.openSession()
for READ-ONLY Contexts (or any change of Context state) to ensure we are creating a new Connection (and not simply modifying the state of an existing one)? Currently we always useSessionFactory.getCurrentSession()
in HibernateDBConnection, which doesn't guarantee a new connection: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/core/HibernateDBConnection.java
- Should we be making use of
...
Overview
Content Tools