[
https://issues.apache.org/jira/browse/DERBY-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537414
]
Daniel John Debrunner commented on DERBY-70:
--------------------------------------------
The section still seems a little unclear to me. Instead of using "application"
it should use server side logic, defining server-side logic as SQL routines
(procedures and functions) implemented in Java.
For example: this section in "Code Your Applications" doesn't make sense for
database class loading:
"An application can safely attempt to boot Derby, even though it is already
running, without any errors. Applications connect to Derby in the usual manner."
> Incorrect documentation about class loading from installed jar files.
> ---------------------------------------------------------------------
>
> Key: DERBY-70
> URL: https://issues.apache.org/jira/browse/DERBY-70
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.0.2.0
> Reporter: Daniel John Debrunner
>
> The section in the developer guide about loading classes from a database,
> incorrectly discusses loading classes stored in a jar file installed in a
> database being loaded from a user application. E.g. 'In an embedded
> environment, when application logic is stored in the database, both the user
> application and Derby can access classes loaded by the Derby class loader
> from stored jar files.'
> Classes stored in such a jar file can only be used by SQL functions and
> procedures.
> Same section also incorrectly mentions server side methods and object
> suppport.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
