Hello, my jasper is failing to compile because I have a space in the path of
my tomcat install.

In the error message (below) you will see that I got a javac error:

D:\pw\tip\output\delivery\Program

that should be 

D:\pw\tip\output\delivery\Program Files\...


It is obviously not handling the space correctly.

Is there anyway to tell jasper to handle the space correctly or start up
with 8.3 dir\file names?

I am already supplying:

"-Dcatalina.home=D:\pw\tip\output\delivery\Progra~1\Bentley\ProjectWise\WebS
erver"
"-Duser.dir=D:\pw\tip\output\delivery\Progra~1\Bentley\ProjectWise\WebServer
" 

when I start the jvm.


The error is below:

  [javac] Compiling 1 source file
    [javac] Since fork is true, ignoring compiler setting.
    [javac] javac: invalid flag: D:\pw\tip\output\delivery\Program
    [javac] Usage: javac <options> <source files>
    [javac] where possible options include:
    [javac]   -g                        Generate all debugging info
    [javac]   -g:none                   Generate no debugging info
    [javac]   -g:{lines,vars,source}    Generate only some debugging info
    [javac]   -nowarn                   Generate no warnings
    [javac]   -verbose                  Output messages about what the
compiler is doing
    [javac]   -deprecation              Output source locations where
deprecated APIs are used
    [javac]   -classpath <path>         Specify where to find user class
files
    [javac]   -sourcepath <path>        Specify where to find input source
files
    [javac]   -bootclasspath <path>     Override location of bootstrap class
files
    [javac]   -extdirs <dirs>           Override location of installed
extensions
    [javac]   -d <directory>            Specify where to place generated
class files
    [javac]   -encoding <encoding>      Specify character encoding used by
source files
    [javac]   -source <release>         Provide source compatibility with
specified release
    [javac]   -target <release>         Generate class files for specific VM
version
    [javac]   -help                     Print a synopsis of standard options

-----Original Message-----
From: "G�tz, Bernd" [mailto:[EMAIL PROTECTED]
Sent: Monday, January 26, 2004 11:40 AM
To: 'Tomcat Users List'
Cc: '[EMAIL PROTECTED]'
Subject: RE: TOMCAT and JNI problem... 


Hi Pablo

we also use JNI in our web apps. it works (except the reloading issue, but
that's another story).

we use the ./bin/setenv.sh script for our settings, therefore:

...
# must contain the ACE Agent JNI library "libaceagent.so":
LD_LIBRARY_PATH=/home/bgo/deploy/sr-hls/native
export LD_LIBRARY_PATH
...

I assume, your JNI implementation is somehow broken... and this makes Tomcat
stop... but that's just a wild guess from far away...

regards
-Bernd.

> -----Original Message-----
> From: J.Pablo M [mailto:[EMAIL PROTECTED]
> Sent: Montag, 26. Januar 2004 17:20
> To: [EMAIL PROTECTED]
> Subject: TOMCAT and JNI problem... 
> 
> 
> Hello.
> 
> I'm running a JSP  based Web aplicacion using Tomcat  wich 
> uses a Java Class
> that  loads a
> native library (JNI).
> 
> The files are created as follows:
> 
>   > javac extractor/HTDInterface.java
>   > javah extractor.HTDInterface
> 
> then I compile my c++ source code with the header file
> "extractor_HTDInterface.h" to create
> the shared library  "libhtd.so"
> 
> create a jar file with the Class that implements JNI call
> 
>      static {
>         System.loadLibrary("htd");
> 
> >jar cvf extractor.jar extractor/HTDInterface.class
> 
> For testing  a standalone application I set my CLASSPATH to include
> extractor.jar
> and libhtd.so file is placed inside the JDK at  
> /JAVA_HOME/jre/lib/i386/
> I successfully build and run The standalone application usin 
> the shared
> library.
> 
> For the web application, extractor.jar is placed at  
> /common/lib/   TOMCAT
> directory
> I leave the libhtd.so at the /JAVA_HOME/jre/lib/i386/   JDK directory.
> When my JSP based Web application calls the native library method
> the Tomcat just STOPS.... it doesn't work  STOPS....
> The message is:
>       The connection was refused when attempting to contact 
> localhost:8080
> I have to run startup.sh script again.
> 
> I took off the libhtd.so file from  /JAVA_HOME/jre/lib/i386/ 
> and I placed it
> in a different directory outside the tomcat:
> 
>             /home/myuser/lib/libhtd.so
> 
> Then I made a script to start the tomcat with the LD_LIBRARY_PATH
> environment variable set up:
> -------------------------------------------------------------
> #!/bin/sh
> export JAVA_HOME=/opt/java
> export CATALINA_HOME=/usr/local/jakarta-tomcat
> export PATH=${JAVA_HOME}/bin:${PATH}
> export JAVA_PATH=${JAVA_HOME}
> # path to load the libhtd.so shared library
> export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/home/myuser/lib
> 
> cd /usr/local/jakarta-tomcat/bin
> sh startup.sh
> -------------------------------------------------------------
> 
> BUT the same happens when the Web application calls the native library
> method
> the Tomcat just STOPS.... it doesn't work  ......STOPS....
> 
> The message is:
>       The connection was refused when attempting to contact 
> localhost:8080
> 
> just like when you try to load the web application and the 
> TOMCAT server  is
> not UP.
> 
> Does anyone knows how to solve this ????
> 
> I have read that maybe setting up the CATALINA_OPTS 
> environment variable
> can solve this
> problem.... BUT I dont know how to set that variable. ???????
> 
> I hope this time I've made myself clear
> 
> Another thing: I'm working under Red Hat 9.0  TOMCAT 4.1.27 
> and JDK 1.4.2
> 
> Pablo  Vidal
> 
> _________________________________________________________________
> MSN Amor: busca tu � naranja http://latam.msn.com/amor/
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to