Community
Participate
Working Groups
There is some interest in adding support for defining additional 3rd party db Vendors. See bug 321401 as one example. We could provide a way to define Vendors via extension, allowing for additional Vendors to be active in the VendorRepository. The primary use for this would be to allow adopters to provide support for DTP database extensions that are not shipped with DTP (namely proprietary DTP extensions). The alternative to this would be for adopters to use the existing JpaPlatform.getConnectionProfileFactory() API to provide an alternate ConnectionProfile implementation. This method allows for much greater flexibility when supporting a DTP extension.
As I already wrote in Dali dev mailing list, we (SAP) would also like to have some extensibility here. We have proprietary DB schema project, to which JPA projects may connect just as to some DB. Impossibility to register our own DB vendor limits us to relying on the UnrecognizedVendor class, which provides default values and objects (like the folding strategy). These default objects (and particularly the folding strategy) don't work properly in our case. I believe the same arguments apply in any case some JPA project tries to connect to some DB, which is not in the list of supported DBs, so, it would be an useful feature for a relatively broad part of the (Dali users) community. I would like to make some contribution here, but I'm not sure how my development capacity will be dsitributed in the nearest fututre, so I can't promise anything for now.
*** Bug 308639 has been marked as a duplicate of this bug. ***
