[ https://issues.apache.org/jira/browse/DERBY-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17267384#comment-17267384 ]
Richard N. Hillegas commented on DERBY-7097:
Attaching derby-7097-03-aa-embeddedDemo.diff. This patch removes the reference to the embedded driver from the embedded demo. The autoloaded driver is faulted in via DriverManager.getConnection(). Therefore there is no need to mention the embedded driver. After applying this patch, I successfully compiled and ran the embedded demo as described in activity 3 of the Getting Started Guide.
Touches the following file:
Removed references to the embedded driver. The shutdown logic was wrong. I don't think that it has worked as documented since Derby 10.2.1.6 introduced driver autoloading.
> Update documentation to allow users to properly use EmbeddedDriver
> Key: DERBY-7097
> URL: https://issues.apache.org/jira/browse/DERBY-7097
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.15.2.0
> Reporter: Daniel Le Berre
> Priority: Major
> Attachments: derby-7097-01-aa-jpms-related-website-changes.diff, derby-7097-01-ab-jpms-related-website-changes.diff, derby-7097-02-aa-releaseSummary.diff, derby-7097-03-aa-embeddedDemo.diff
> In earlier version of Derby, and as reported in the documentation, the EmbeddedDriver class was in derby.jar.
> As such, it was quite easy to deploy a webapp with an embedded derby database: it was sufficient to just add a derby.jar file to the project library.
> In current releases of derby (10.15.2.0), the EmbeddedDriver class is no longer in the derby.jar file but in the derbytools.jar file.
> $ for i in `ls *.jar`; do echo $i ; jar tf $i | grep Driver ; done
> As such, most of the tutorials found on the internet about "how to use derby in embedded mode" are just wrong because they simply mention derby.jar as a dependency.
> Worst, derby own documentation is not up to date: as such, I had no way to understand why new releases of this tool that I have been using for more than a decade in the classroom suddenly did not work anymore.
> The explanation is finally simple: I just wonder how such impacting decision could be done without proper documentation.
> I am also surprised to be the first one reporting this, since the problem exists since at least a year.
> There are two possible fix to this issue:
> * move back the EmbeddedDriver class to derby.jar (my favorite option I would say), but I guess there is a good reason for moving those classes to derbytools.jar
> * update the documentation on Derby's web site, with a quite visible alert about this change.
> I have been a pretty happy user of derby for years, and will certainly be in the future. Thanks for that great tool. However, that breaking change has been particularly annoying, which is the reason of that bug report.
This message was sent by Atlassian Jira
|Free forum by Nabble||Edit this page|