[DERBY-3450] Reduce module dependencies in Derby

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Services, SQL, Store
• Labels: derby_triage10_10 derby_triage10_11
• Urgency: Low
• Assignee: Unassigned
• Reporter: Dibyendu Majumdar
• Created: 22/Feb/08 23:12
• Updated: 18/Jul/13 09:46

Description

Derby modules are already well-defined, and have well-defined interfaces. However, there are areas where the module boundaries have not been fully respected, and unwelcome interactions occur. This task aims at fixing such issues to eliminate unwanted dependencies between modules.

Sub-tasks will be created to address specific issues. Changes will be submitted in small increments so that the impact of the changes can be assessed easily. Small changes will also reduce risk and allow the changes to be absorbed quickly.

This task is related to DERBY-3405 and DERBY-3351. However, the changes in this will be generic and independent of the specific objectives of those enhancements.

Issue Links

• relates to: DERBY-4845 Improve the dependency tracking for our build targets
• relates to: DERBY-3351 Implement a Pluggable Storage Engine Architecture in Derby
• relates to: DERBY-3405 Examine the possibility of implementing Derby modules as OSGI bundles

Sub-Tasks

• Remove dependency between StandardException class and org.apache.derby.impl.jdbc classes.: Closed
• ShutdownException and ErrorStringBuilder classes do not belong to the services context module: Closed
• The PublicAPI class should belong to org.apache.derby.iapi.jdbc as it handles creation of SQLException: Open