Feature Requests item #1469828, was opened at 2006-04-13 15:01
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=379537&aid=1469828&group_id=23735
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Interface Improvements (example)
Group: None
Status: Open
Priority: 5
Submitted By: Norman Gray (normang)
Assigned to: Nobody/Anonymous (nobody)
Summary: make sisc.shp available in a .jar file
Initial Comment:
The defaults-for-everything Context.execute() interface makes it
very easy to bridge from Java to Scheme. If, however, the
AppContext.findHeap() method is unable to find the default heap
(perhaps because it is running inside Tomcat), then the caller
must set the default heap via a sequence of calls which is not
particularly complicated, but which is messy if all the potential
errors are to be caught, and which takes away from the
simplicity of the Context.execute() interface.
If the heap were contained inside a .jar file, then there is
code in the findHeap() method to find it (including in the Tomcat
context mentioned), and indeed the sisc-heap.jar build product
provides such a facility. This .jar file is not included in the standard
binary distribution, however, and there is (reasonable) resistance
to including it, since to do so would duplicate the large heap file.
An alternative is to provide a means of creating the heap-in-a-jar
file from the distributed .shp file. I've attached a patch to build.xml
and a MakeSiscHeap program (which I suggest putting in
sisc.util.MakeSiscHeap.java) which can do this. The modified
build.xml builds make-sisc-heap.jar, which is a small jar file which
can be distributed alongside the sisc.shp file, and which can
be used to generate a heap .jar when desired.
Usage:
% java -jar make-sisc-heap.jar [.../sisc.shp]
creates file sisc-heap-bundle.jar containing the heap and the
boot/sisc/HeapAnchor class.
(if the optional argument is omitted, the program defaults to looking
for the sisc.shp file in the same directory as the make-sisc-heap.jar
file).
If the make-sisc-heap.jar file is named make-sisc-heap-jar instead,
then it will still work, but it won't be scooped up in a build step
which copies *.jar elsewhere.
The modified build.xml doesn't address the fine details of how best
to include the make-sisc-heap.jar file in the binary distribution.
Norman
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=379537&aid=1469828&group_id=23735
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
|
