1.1.1

Table Of Contents
Chapter 20
Storing and Loading JAR Files in SQLFire
Application logic, which can be used by SQL functions and procedures, includes Java class les stored in a JAR le
format. Storing application JAR les in SQLFire simplies application deployment, because it reduces the potential
for problems with a user's classpath.
SQLFire automatically loads installed JAR le classes into the class loader so that you can use them in your SQLFire
applications and procedures. The JAR classes are available to all members of the SQLFire distributed system, including
those that join the system at a later time.
Note: Many of the topics in this section were adapted from the Apache Derby documentation source les, and
are subject to the Apache license:
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
Class Loading Overview
You store application classes, resources, and procedure implementations in SQLFire by installing one or more
JAR les. After installing the JAR le, an application can then access the classes without having to be coded in
a particular way.
These are the basic steps for storing and using JAR les in SQLFire.
Create JAR Files for Your Application
When you create a JAR le for installation, include any Java classes that are intended for SQLFire class loading.
This might include stored procedure or result processor implementations, as well as supporting classes.
When you add classes to the JAR le, do not include:
The standard Java packages (java.*, javax.*)
125