Bugzilla – Full Text Bug Listing
| Summary: | Ability to add DB driver library to project build path on project creation | ||
|---|---|---|---|
| Product: | [WebTools] Dali JPA Tools | Reporter: | Neil Hauge <neil.hauge> |
| Component: | General | Assignee: | Tran Le <tranle1> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | karenfbutzke, paul.fullbright, shaun.smith |
| Version: | 2.0 | Keywords: | plan |
| Target Milestone: | 2.1 M2 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | EaseOfUse | ||
Visual for implementation described in initial comments. [x] Add driver library to build path: |Derby Embedded JDBC Driver V| Additionally, the checkbox and the combo will enable only when the project has a connection profile. checked into HEAD |
In JPA project creation, we should add support for a user option to add a "Connectivity Driver Definition" library to the project. This option could be added to the bottom of the existing "Connection" group on the JPA Facet page. This could be a one-line checkbox label("Add driver library to build path") that enables a combo, which is populated by the available driver definitions from DTP. Upon finishing the wizard, the specified library would be added to the project, similar to what currently happens with the JPA implementation User Library. As a reference, take a look at the DTP based Connectivity Driver Definition library option that has been added to the standard "Add Library..." functionality.