Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 1 Aug 2011 16:00:10 +0000 (UTC)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1836257429.23068.1312214410388.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1174349043.18204.1311934149737.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (DERBY-5361) Document use of URLs with
 SQLJ.INSTALL_JAR
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073583#comment-13073583 ] 

Dag H. Wanvik commented on DERBY-5361:
--------------------------------------

Yes, I think so, as long as we don't phrase it so it looks like we *require* an absolute path, relative (including just the file name, i.e. no directory) works too.

> Document use of URLs with SQLJ.INSTALL_JAR
> ------------------------------------------
>
>                 Key: DERBY-5361
>                 URL: https://issues.apache.org/jira/browse/DERBY-5361
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.9.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-5361.diff, DERBY-5361.stat, DERBY-5361.zip
>
>
> The reference manual's topic on SQLJ.INSTALL_JAR says the first argument is the path of the jar file to add. That argument doesn't have to be a file path, it can also be a URL.
> Changes needed:
> - rename JAR_FILE_PATH to JAR_FILE_URL (or perhaps JAR_FILE_PATH_OR_URL?)
> - update description of said parameter to reflect that it can also take a URL
> - add a new example in the SQL examples paragraph:
> -- SQL statement
> -- install jar from remote location
> CALL SQLJ.INSTALL_JAR('http://www.example.com/tours.jar', 'APP.Sample3', 0)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira